How to add an MCP server to Cline
Cline reads its MCP servers from cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers) and connects to them over stdio (a local process), Streamable HTTP and HTTP+SSE.
123,011 of the 123,011 servers we can write a config for work in it.
A local server
A local server runs on your machine, started by Cline from its package. It needs Node.js installed first. For example, Azure MCP Server goes in cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"azure": {
"command": "npx",
"args": ["-y", "@azure/[email protected]", "server", "start"]
}
}
}A remote server
A remote server runs on its publisher's machines, and Cline connects to its address. Nothing needs installing. For example, Context7 goes in cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"context7": {
"type": "streamableHttp",
"url": "https://mcp.context7.com/mcp"
}
}
}Which servers work in Cline
Cline can send a key in a header, so the 3,250 servers that need one work in it.
| Runs | Servers | In Cline? |
|---|---|---|
| Local (stdio) | 85,194 | Works |
| Remote, Streamable HTTP | 30,856 | Works |
| Remote, Streamable HTTP, key in a header | 3,203 | Works |
| Remote, HTTP+SSE | 3,711 | Works |
| Remote, HTTP+SSE, key in a header | 47 | Works |
If the server does not show up
- A remote server that does not connect
- The environment variables servers ask for
- Cline's own MCP documentation
Matches the official docs The configs follow Cline's MCP docs, read on 2026-10-31.