MCP client - Continue - verified
How to add an MCP server to Continue
Where to add MCP servers in Continue: mcpServers in ~/.continue/config.yaml (%USERPROFILE%\.continue\config.yaml on Windows), or block files (YAML or JSON MCP configs) in .continue/mcpServers/ at the workspace root. Its docs list support for stdio, Streamable HTTP and SSE. Its docs do not say whether it handles OAuth for remote servers.
Continue homepage - Continue.dev in our tools directory - Compare all MCP clients
- Kind
- Editor
- stdio
- Yes
- Streamable HTTP
- Yes
- SSE
- Yes
Add a server
- Where the config lives
- mcpServers in ~/.continue/config.yaml (%USERPROFILE%\.continue\config.yaml on Windows), or block files (YAML or JSON MCP configs) in .continue/mcpServers/ at the workspace root
The example from the Continue docs, copied verbatim. Swap in your server's name, command or URL.
Excerpt from the docs - merge into your existing config
# ...
mcpServers:
- name: Name
type: streamable-http
url: https://....
# ...Which server?
Pick a server from the verified directory of official MCP servers. Each one lists its transport, auth and the setup snippets its vendor publishes, so you can match it to what Continue supports.
MCP support
What the Continue docs say it supports. Not stated means the docs do not say either way.
| Feature | Value | Source |
|---|---|---|
| ToolsCalls the functions a server exposes. | Yes | docs.continue.dev/customize/deep-dives/mcp |
| ResourcesReads data and files a server exposes as resources. | Not stated | Docs do not say |
| PromptsOffers a server's prompt templates to the user. | Not stated | Docs do not say |
| SamplingLets a server ask the client's model for a completion. | Not stated | Docs do not say |
| RootsTells a server which directories it may work in. | Not stated | Docs do not say |
| ElicitationLets a server ask the user for input mid-task. | Not stated | Docs do not say |
| DiscoveryPicks up tools, prompts or resources a server adds or removes while connected. | Not stated | Docs do not say |
| InstructionsUses the instructions a server sends when it connects. | Not stated | Docs do not say |
| stdioStarts a local server as a subprocess. | Yes | docs.continue.dev/customize/deep-dives/mcp |
| Streamable HTTPConnects to a remote server over the current HTTP transport. | Yes | docs.continue.dev/customize/deep-dives/mcp |
| SSEConnects over the older HTTP+SSE transport. | Yes | docs.continue.dev/customize/deep-dives/mcp |
| OAuthSigns in to remote servers with OAuth. | Not stated | Docs do not say |
Worth knowing
Continue's docs state that MCP can only be used in agent mode.
Other editors
FAQ
Where is the Continue MCP config?
mcpServers in ~/.continue/config.yaml (%USERPROFILE%\.continue\config.yaml on Windows), or block files (YAML or JSON MCP configs) in .continue/mcpServers/ at the workspace root. The example on this page is copied from https://docs.continue.dev/customize/deep-dives/mcp
Does Continue support remote MCP servers over Streamable HTTP?
Yes, per https://docs.continue.dev/customize/deep-dives/mcp. Its docs list support for stdio, Streamable HTTP and SSE.
Does Continue support OAuth for MCP servers?
Its docs do not say whether it handles OAuth for remote servers.
Which MCP features does Continue support?
Its docs list Tools. They do not state Resources, Prompts, Sampling, Roots, Elicitation, Discovery and Instructions.
Sources
Last verified from the pages below.
- Continue docs: How to Set Up Model Context Protocol (MCP) in Continue - docs.continue.dev
- Continue docs: How to Configure Continue - docs.continue.dev
- Continue docs: config.yaml Reference - docs.continue.dev
Newsletter
New MCP servers, the week they ship
One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.