Exa MCP server in Continue.dev search the live web from YAML.
Bridge Exa's hosted search endpoint into Continue.dev's config.yaml so chat and agent sessions can search, crawl, and pull real code examples.
Continue.dev sessions are bounded by your codebase plus the model's memory — and the web is where the answers to "why is this failing" and "what changed in the new release" actually live. Exa is a search engine built for AI callers: web search, page crawling, and a code-context tool that retrieves real usage examples. The server is open source (github.com/exa-labs/exa-mcp-server, 4.6k stars) and offered hosted by Exa.
Continue declares MCP servers in YAML, and since Exa is remote you bridge it with mcp-remote — a local proxy spawned by the same block.
What an Exa-equipped session looks like
Hit a cryptic stack trace and the agent searches for it. Upgrading a dependency? It crawls the release notes. Integrating an API with sparse docs? The code-context tool returns how real repositories call it. As of mid-2026 those three capabilities — search, crawl, code-context — are the hosted server's tool set; Exa's live Loomal marketplace listing at https://loomal.ai/marketplace/exa shows what's currently exposed.
You'll need an Exa API key from their dashboard; usage is metered on Exa's side.
The config.yaml block
Add the entry to ~/.continue/config.yaml for global availability, or as a standalone YAML file in .continue/mcpServers/ inside a single project. The command spawns mcp-remote locally, which proxies stdio to Exa's HTTP endpoint — your key rides along as a URL parameter:
mcpServers:
- name: exa
command: npx
args:
- "-y"
- "mcp-remote"
- "https://mcp.exa.ai/mcp?exaApiKey=YOUR_EXA_API_KEY"Reload the extension and test
Reload Continue (Reload Window in VS Code does it) so the new block is read. In an agent-mode chat, ask for something undeniably current — a release that shipped this week — and watch the tool calls panel for an Exa search. If the model answers from memory instead, ask it explicitly to search; once it has used the tool successfully it tends to keep reaching for it.
Troubleshooting in Continue.dev
YAML quoting bites here specifically: the Exa URL contains ? and =, so keep it quoted as shown — an unquoted URL can parse but mangle the key, producing auth failures that look like server bugs. Indentation errors under args are the other frequent break; each item gets its own dash at the same depth.
If the block parses but the server never connects, test npx -y mcp-remote <url> in a terminal: an immediate exit usually means the URL or key is bad, while a hang followed by connection in Continue means it was working all along and the extension just needed its reload. Continue re-reads MCP config only on reload — every edit needs one.
FAQ
How do I add Exa to Continue.dev?
Add an mcpServers list entry to ~/.continue/config.yaml that runs npx -y mcp-remote with Exa's endpoint URL (including your exaApiKey), then reload the Continue extension. Project-scoped setups use a YAML file in .continue/mcpServers/ instead.
Why does the config run mcp-remote instead of an Exa package?
Exa ships its MCP server as a hosted remote endpoint, and Continue's stdio-style YAML blocks launch local commands. mcp-remote is the standard local proxy that connects the two; recent Continue versions also support remote transports directly, so check their docs if you'd rather skip the proxy.
My searches return auth errors. What happened?
Either the exaApiKey URL parameter is wrong or your Exa credits ran out. Verify the key in Exa's dashboard and make sure the URL stayed quoted in YAML — unquoted special characters can corrupt the parameter without an obvious error.
Does using Exa through Continue cost money?
The MCP server is open source, but each search consumes metered Exa API usage under their pricing; trial credits usually cover initial use. There's no charge from Continue's side for connecting it.
More MCP servers for Continue.dev.
Live tool lists on every listing in the index.