Exa MCP server in VS Code (GitHub Copilot) live web results in agent mode.
Wire Exa's hosted MCP endpoint into VS Code's mcp.json and Copilot's agent mode gets web search, crawling, and code-context lookup — no local process required.
Copilot's agent mode is strong inside your repository but blind to the live web. Exa (github.com/exa-labs/exa-mcp-server, 4.6k stars) fixes that with fast, intelligent web search and crawling over MCP — including a code-context tool that pulls relevant, current library and API documentation, which is exactly what an agent writing code against fast-moving dependencies needs.
Exa ships as a hosted remote server, so the VS Code setup is one of the simplest in the catalog: a URL entry in mcp.json, no npx command, no stdio process for VS Code to babysit.
Two ways in: Command Palette or mcp.json
VS Code reads MCP servers from mcp.json, which exists at two scopes: your user settings (created via Command Palette: MCP: Add Server) for servers you want everywhere, and .vscode/mcp.json in a project for servers checked in alongside the code. For a general-purpose search server like Exa, user scope usually makes more sense — but project scope is the right call if your whole team should get it on clone.
Running MCP: Add Server walks you through it interactively; pick the HTTP server type and paste the endpoint. Or write the file directly.
The config
Note that VS Code's mcp.json uses a servers key — not the mcpServers key most other clients use. Copying a Claude Desktop snippet verbatim is the single most common mistake here. Grab an API key from your Exa dashboard first:
{
"servers": {
"exa": {
"type": "http",
"url": "https://mcp.exa.ai/mcp?exaApiKey=YOUR_EXA_API_KEY"
}
}
}Start the server and confirm tools
Saving the file isn't enough — open the file in the editor and click the Start action VS Code renders above the server entry (or use MCP: List Servers from the Command Palette and start it there). Then open Copilot Chat in agent mode, click the tools icon, and check that Exa's search and crawling tools are listed and enabled.
Ask something that forces a lookup — "search for the current Bun release notes" — and you should see a tool-call confirmation before Copilot runs the Exa search.
Troubleshooting in VS Code
If the server shows an error state, run MCP: List Servers and pick Show Output to get the server's log — that's where auth failures appear, and an invalid or missing exaApiKey in the URL is the most frequent one. A 401-style failure in the log means the key, not your config syntax.
If tools are connected but Copilot never calls them, check that agent mode (not plain chat) is active and that the tools are toggled on in the tools picker. After editing mcp.json, restart the server from the MCP view; a full Reload Window clears stubborn cached state. Also confirm MCP support is enabled in your settings (chat.mcp.enabled) if your organization manages VS Code policy centrally.
See what you're connecting to
Exa's live listing on the Loomal marketplace at https://loomal.ai/marketplace/exa shows the server's probed tool list, so you can confirm what Copilot will see before you touch mcp.json. It sits in the search category alongside other web-retrieval servers worth comparing.
FAQ
How do I install Exa in VS Code with Copilot?
There's no package to install. Run MCP: Add Server from the Command Palette and choose HTTP, or add an entry under the servers key in .vscode/mcp.json pointing at https://mcp.exa.ai/mcp with your API key, then click Start in the MCP view.
Where does VS Code keep MCP configuration?
In mcp.json at two scopes: user-level (created through Command Palette: MCP: Add Server) and project-level at .vscode/mcp.json. Project-scoped entries can be committed so teammates get the server automatically.
Why doesn't Exa show up in Copilot after I save mcp.json?
Usually one of three things: you used mcpServers instead of VS Code's servers key, you never started the server from the MCP view, or the exaApiKey in the URL is wrong. MCP: List Servers > Show Output gives you the exact error.
Do I need Node.js or npx for this?
No. Exa is a hosted remote server, so VS Code talks to it over HTTP directly. That sidesteps the PATH and runtime-version problems that stdio-based MCP servers commonly cause.
Browse more MCP servers for VS Code.
Find every Copilot-compatible server with live tool lists.