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