Connect Cline to local and remote MCP servers

Cline can connect to local stdio processes and hosted remote MCP servers, allowing developers to add external APIs and services beyond the agent’s built-in tools. The meaningful setup choice is whether the workflow belongs in a local process or shared hosted endpoint, followed by credential handling, explicit approval boundaries, and direct tool testing.

Setup path

How to approach this capability

1
Choose a local stdio or remote streamable HTTP setup based on whether the integration is personal or shared.
2
Configure credentials securely, confirm the exposed tools, and test one constrained tool call before enabling broader automation.

Distribution decision

Cline documents UI, JSON, and CLI paths for adding and managing MCP servers.

Governance and safety

Install only trusted servers, limit auto-approval to safe tools, and review the permission and timeout model.

First-party documentation

MCP overview
Source checked Aug 16, 2026