How to Add a Remote MCP Server to Cline
Where Cline keeps its Remote Servers tab and cline_mcp_settings.json, the required "type": "streamableHttp" key, and the silent fallback to legacy SSE when that key is missing.
Last verified October 15, 2026
How do I add a remote MCP server to Cline?
Click the MCP Servers icon in Cline's top toolbar, open the Configure tab, and use the Remote Servers tab: enter a server name, the full server URL, set Transport Type to Streamable HTTP, and click Add Server. If you'd rather edit the config directly, the same tab has a Configure MCP Servers button that opens the underlying JSON file, where a remote entry needs "type": "streamableHttp" set explicitly — Cline's docs say omitting it falls back to the legacy SSE transport.
Where the setting actually lives
Cline's MCP settings are reached the same way whether you're adding a local (STDIO) tool or a hosted remote server: MCP Servers icon → Configure tab. From there, the Remote Servers tab is the form-based path for a hosted endpoint, and the Configure MCP Servers button opens the raw JSON for anyone who wants to paste a config block instead.
If you're on the Cline CLI rather than the VS Code extension, cline mcp opens an interactive wizard that can list, add, edit, enable/disable, and delete servers — including prompting for a URL and headers when you choose a remote transport, and an Authorize OAuth action that runs or reruns browser authorization for a remote server. cline config mcp (or cline config mcp --json) lists servers non-interactively, and cline mcp add <name> <url> --transport http --yes adds a remote server in one scripted step (cline mcp remove deletes one). The CLI and the IDE extension share one settings file, so a server you add in one shows up in the other.
That file is ~/.cline/data/settings/cline_mcp_settings.json, and Cline's docs say all Cline apps (the IDE extension, the CLI, and the SDK) read MCP settings from it. The CLI can be pointed at a different file with the CLINE_MCP_SETTINGS_PATH environment variable. The Configure MCP Servers button opens the same file, so use whichever is handier; the path is useful for scripting or version control.
The config
Cline reads remote servers from an mcpServers object, keyed by the name you give the server, with a type, a url, and — only if the server requires a static token — a headers object:
{
"mcpServers": {
"my-server": {
"type": "streamableHttp",
"url": "https://mcp.example.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}
The type field is required for Streamable HTTP. Cline's docs are explicit: "The type field selects the transport. Omitting it defaults to the legacy sse transport for backward compatibility, so set type: streamableHttp explicitly for the recommended transport." Leaving it out is the single most common reason a remote server connects to nothing.
If the server issues you a static token rather than running an OAuth flow, add it under headers:
"headers": {
"Authorization": "Bearer your-token"
}
disabled toggles the server off without deleting it. You may still see an autoApprove list in examples, but per-tool approval no longer applies in current builds: since Cline 4.1.15 and 4.1.16 (August 2026), MCP auto-approval is governed solely by the global Use MCP servers toggle.
Worth knowing if you're moving a config between editors: type: streamableHttp is Cline's own spelling. VS Code and Visual Studio use "type": "http"; Continue and Zoo Code use "streamable-http" with a hyphen; OpenCode uses "type": "remote"; Qwen Code uses httpUrl instead of a type field, treating plain url as legacy SSE, while current Gemini CLI uses url with "type": "http"; and Cursor, Zed, JetBrains, and Claude Desktop take a plain url with no type key at all. Copying a working block from one of those editors into Cline's config will save without error and then silently fall back to SSE — check that type reads exactly streamableHttp before assuming the config is wrong.
Authorization
What happens after you click Add Server depends on how the server itself is built, and Cline's documentation and its GitHub changelog describe two different mechanisms rather than one:
- Static token servers use the
headersfield above — you paste aBearertoken you already have, and there's no browser step. - OAuth-capable servers open a browser tab for you to sign in and approve, without any
headersentry. Cline's GitHub changelog records version 4.1.7 adding "support for pre-registered OAuth clients for remote MCP servers, for setups where dynamic client registration isn't available," and a fix in the same release to "surface OAuth authorization for SSE MCP servers on a 401 instead of failing outright." Cline's CLI docs list an Authorize OAuth action in thecline mcpwizard to run or rerun browser authorization for a remote server; the docs don't describe the IDE extension's own OAuth screens.
If a server that previously worked starts failing with an authorization error, that's usually an expired token rather than a broken config — delete the server and re-add it to force a fresh OAuth exchange, rather than editing the JSON.
What usually goes wrong
| Symptom | Cause and fix |
|---|---|
| Connects, then fails immediately | Missing or misspelled type. Without "type": "streamableHttp" (exact camelCase), Cline falls back to the legacy sse transport and a Streamable HTTP server won't answer it. |
| "Unauthorized" or 401 after it worked before | The OAuth token expired. Delete the server and re-add it to run a fresh authorization (on the CLI, the cline mcp wizard's Authorize OAuth action reruns it); Cline's 4.1.7 release improved how 401s surface for SSE servers instead of failing outright. |
| Server added but no tools appear | Confirm the server started — Cline's docs point to checking that it's enabled (disabled: false) and that the process or endpoint is actually reachable, then restart the session, since tool lists commonly refresh only at session start. |
| Tool calls sit there doing nothing | Check for Cline's approval prompt and approve the call. In current builds, MCP auto-approval is the single global Use MCP servers toggle, not a per-tool autoApprove list. |
| Unresponsive server | Use the restart control in MCP settings rather than deleting and re-adding, unless you also need a fresh OAuth exchange. |
A worked example
To make the above concrete, here's what it looks like with a real server. Tempreon is a hosted MCP server that gives whichever AI tool you're working in a persistent memory of how you work, and its server supports OAuth, so the example needs no headers entry:
{
"mcpServers": {
"tempreon": {
"type": "streamableHttp",
"url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp",
"disabled": false,
"autoApprove": []
}
}
}
Add that through the Remote Servers tab (or paste it into the JSON via Configure MCP Servers), and Cline opens a browser tab to approve the connection the first time it connects — there's no token to find or paste. A full walkthrough, including what to do if re-authorization ever gets stuck, is in the Cline setup doc.
Any other MCP server that supports Streamable HTTP follows the same shape — swap the name, the URL, and add headers only if that server hands you a static token instead of running OAuth.
Sources
The dated claims on this page were checked against these vendor documents. Client UIs move constantly, so if one of these has changed since the date shown, trust the vendor over this page — and tell us.
- MCP — Cline Docs — read 2026-10-15
- Configuration — Cline Docs — read 2026-10-15
- CHANGELOG.md — cline/cline (GitHub) — read 2026-10-15
Frequently asked questions
- Where is the MCP setting in Cline?
- Click the MCP Servers icon in Cline's top toolbar, open the Configure tab, and either use the Remote Servers tab for a hosted endpoint or click Configure MCP Servers to edit the JSON file directly. Both paths write to the same config, so use whichever is faster for the change you're making.
- Does a remote MCP server need the type field set in Cline?
- Yes, if you want Streamable HTTP. Cline's docs state that omitting "type" defaults the connection to the legacy sse transport for backward compatibility, so a server built for Streamable HTTP needs "type": "streamableHttp" written explicitly, in that exact camelCase. Without it, Cline falls back to legacy SSE, and a Streamable HTTP server won't connect.
- Does Cline support OAuth for remote MCP servers, or only static headers?
- Both. Cline's MCP docs describe the headers object for a static Authorization: Bearer token, and the CLI docs list an Authorize OAuth action in the cline mcp wizard that runs or reruns browser authorization for a remote server. Cline's GitHub changelog adds detail: version 4.1.7 added support for pre-registered OAuth clients on remote servers and, for SSE servers, started surfacing OAuth authorization on a 401 instead of failing outright, and earlier GitHub issues describe Cline opening a browser tab for servers that support dynamic client registration. In practice, a server with OAuth support gets a browser consent screen on first connect and needs no headers entry at all — add the headers field only for a server that issues you a static token instead.