Continue MCP Setup: Connect MCP Servers to Continue
What it is
An open-source AI code assistant for VS Code and JetBrains that lets you build and share custom autocomplete and chat models.
How MCP works in Continue
Continue is an MCP client for its Agent mode. Servers are declared in a top-level mcpServers block (or standalone files under .continue/mcpServers/) over stdio, SSE, or streamable-http.
Config file location
config.yaml (in ~/.continue/) or a YAML file under .continue/mcpServers/ holds a top-level mcpServers list.
Add your first server
A good first server is Playwright MCP — Microsoft's browser automation server. It runs locally over stdio via npx, needs no API key, and gives the agent a real browser to drive. Here is the verified Continue config:
mcpServers:
- name: Playwright
command: npx
args:
- "@playwright/mcp@latest"Restart or reload Continue after saving, then confirm the server's tools show up. Swap in any other server from the directory using the same structure.
Transports & platforms
| Transports | stdio, SSE, Streamable HTTP |
|---|---|
| Platforms | macOS, Windows, Linux |
| License | Open source |
| Vendor | Continue |
FAQ
Does Continue support MCP?
Yes. Continue works as an MCP client over stdio, SSE, Streamable HTTP. Continue is an MCP client for its Agent mode. Servers are declared in a top-level mcpServers block (or standalone files under .continue/mcpServers/) over stdio, SSE, or streamable-http.
Where is the Continue MCP config?
config.yaml (in ~/.continue/) or a YAML file under .continue/mcpServers/ holds a top-level mcpServers list. The verified example above shows the exact structure it expects.
Which MCP servers work with Continue?
Any server that speaks a transport Continue supports (stdio, SSE, Streamable HTTP). Browse the MCP server directory on this site to find databases, browser automation, API integrations, and dev tools, then add them using the config format above.