Cline MCP Setup: cline_mcp_settings.json, Remote Servers and autoApprove (2026)

In the Cline extension, click the MCP Servers icon at the top of the Cline panel, open the Configure tab and click Configure MCP Servers. That opens Cline's MCP settings JSON, where you add servers under mcpServers. For a hosted server, the Remote Servers tab lets you paste a URL instead.

In the Cline CLI, the file is ~/.cline/data/settings/cline_mcp_settings.json, and cline mcp opens a setup wizard. One detail trips people up: for remote servers, set "type": "streamableHttp" yourself, because Cline defaults to the older SSE transport when type is missing.

Checked against: Cline's MCP documentation on 2 November 2026. eSEOspace did not test Cline.

Add a server in the IDE extension

Edit the JSON

1. In the Cline panel, click the MCP Servers icon (the stacked-server icon in the top toolbar).
2. Open the Configure tab.
3. Click Configure MCP Servers near the bottom.
4. Add or update entries under mcpServers and save.

Or paste a remote URL

1. Open the Remote Servers tab.
2. Enter a Server Name and the full Server URL.
3. Choose Streamable HTTP (Cline marks it recommended) or SSE (Legacy).
4. Click Add Server.

Example configs

A local stdio server, from Cline's docs:

{
  "mcpServers": {
    "local-server": {
      "command": "node",
      "args": ["/path/to/server.js"],
      "env": {
        "API_KEY": "your_api_key"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

A remote Streamable HTTP server:

{
  "mcpServers": {
    "remote-server": {
      "type": "streamableHttp",
      "url": "https://example.com/mcp",
      "headers": {
        "Authorization": "Bearer your-token"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Both were checked against Cline's docs on 2 November 2026. Cline's docs explain: "Omitting it defaults to the legacy sse transport for backward compatibility, so set "type": "streamableHttp" explicitly." Our SSE vs Streamable HTTP comparison covers why SSE is being phased out.

Add a server in the Cline CLI

The CLI reads ~/.cline/data/settings/cline_mcp_settings.json. Set the CLINE_MCP_SETTINGS_PATH environment variable to use another file.

Run the wizard:

cline mcp

It can list, add, edit, enable or disable, authorize OAuth for, and delete servers. To skip the menu in scripts, Cline's docs show:

cline mcp add files --yes -- npx -y @modelcontextprotocol/server-filesystem .
cline mcp add docs https://example.com/mcp --transport http --header "Authorization: Bearer TOKEN" --yes
cline mcp remove docs

Without --yes, cline mcp add opens the wizard with those fields pre-filled. To list servers without the wizard, run cline config mcp or cline config mcp --json.

autoApprove: use it carefully

Each server entry can carry an autoApprove list. Tools named there run without asking you. Cline's security advice is short: "Limit autoApprove to safe tools" and "review tool calls before approval."

A practical rule: only add tools that read data, never tools that create, update, delete or send. Our MCP tool permission planner helps sort a server's tools into those groups, and our excessive permissions guide explains the risk.

Local or remote: which to choose

Cline's docs sum up the trade-off. STDIO servers mean a "local process, lower latency, simpler local setup." Remote HTTP or SSE servers mean a "hosted endpoint, centralized deployment, supports multi-client usage." Their advice: "Use STDIO for local tools and remote transport for shared hosted services."

For a business team, that usually means remote servers for SaaS apps such as a CRM or issue tracker, where the vendor hosts the server and you sign in with OAuth. Keep stdio for tools that must touch files on the developer's machine. Our remote vs local lesson goes deeper.

Check that it works

Cline's quick start ends with: "Verify tools appear and test one tool call." In the MCP Servers panel, a connected server lists its tools. Ask Cline to run one low-risk tool and check the result.

In the same panel you can enable or disable servers, restart one that stops responding, set request timeouts and remove servers.

Troubleshooting

Cline's docs give this table, summarized:

For a deeper look at a stubborn server, test it outside Cline with the MCP Inspector, which runs with npx @modelcontextprotocol/inspector and needs Node 22.19.0 or newer. Our MCP Inspector lesson walks through it. For the Filesystem server used in the CLI example above, the MCP project's local server guide explains the folder arguments.

Common mistakes

• Leaving out type on a remote server. Cline falls back to SSE, which many modern servers do not offer.
• Real tokens in a shared settings file. Cline advises storing secrets in environment variables.
• A long autoApprove list. It removes your chance to catch a bad tool call.
• Editing the IDE file and expecting the CLI to see it. The CLI uses its own settings path unless you point CLINE_MCP_SETTINGS_PATH at the same file.

Next step

Pick a first server from our best MCP servers for VS Code list, since Cline runs inside VS Code. If you also use Copilot, our VS Code mcp.json guide explains how its separate config works. The config generator can draft entries for you.

Frequently asked questions