Exa MCP server in Cline web search for an autonomous coder.
Connect Exa's hosted search endpoint to the Cline VS Code extension through cline_mcp_settings.json — reachable in two clicks from the Cline panel.
Cline plans and executes multi-step coding tasks, and tasks routinely hit walls that training data can't climb: an undocumented breaking change, an obscure error string, a brand-new SDK. Exa — an AI-native search engine with crawling and code-context retrieval, open source at github.com/exa-labs/exa-mcp-server (4.6k stars) — gives Cline a way through.
Exa runs as a hosted remote server, so the Cline setup is a proxy entry in one JSON file. You don't need to hunt for that file on disk; Cline opens it for you.
Where Exa helps a Cline task
Mid-task, Cline can search the web for the exact error it just hit, crawl a library's migration guide, or pull code-context examples showing how production codebases use an API. Because Cline asks for approval before tool calls (unless you auto-approve), you see each search before it runs. As of mid-2026 the hosted endpoint exposes search, crawl, and code-context tools — Exa's live listing on the Loomal marketplace at https://loomal.ai/marketplace/exa shows the current set.
Open the config from the Cline panel
In VS Code, open the Cline panel, click the MCP Servers icon, then Configure — this opens cline_mcp_settings.json, which physically lives deep in VS Code's globalStorage under saoudrizwan.claude-dev/settings/, a path nobody should type by hand. Add an entry that bridges to Exa's remote endpoint via mcp-remote, with your API key from Exa's dashboard:
{
"mcpServers": {
"exa": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.exa.ai/mcp?exaApiKey=YOUR_EXA_API_KEY"
]
}
}
}Verify in the MCP Servers panel
Save the file and watch the MCP Servers panel: Exa should appear with a green status and an expandable tool list. Each tool has a toggle and an auto-approve option — leave auto-approve off until you've seen a few calls and trust the pattern. Then start a task that needs current information and confirm Cline proposes an Exa search.
Troubleshooting in Cline
A red status in the panel means the local proxy process failed: most often Node isn't visible to VS Code, or the JSON has a syntax slip — the panel shows the error inline, which beats digging through logs. Use the panel's Restart action on the server after fixing; a full VS Code window reload (Developer: Reload Window) clears stubborn cases.
If the server is green but searches error out, the problem is on the Exa side of the bridge: an invalid exaApiKey in the URL or exhausted API credits. Cline surfaces the tool error text in the task transcript, and Exa's dashboard confirms key status and remaining usage.
FAQ
How do I install Exa in Cline?
Open the Cline panel > MCP Servers > Configure, which opens cline_mcp_settings.json. Add an exa entry under mcpServers running npx -y mcp-remote with Exa's endpoint URL and your API key, save, and check the panel for a green status.
Where is cline_mcp_settings.json on disk?
Inside VS Code's globalStorage at saoudrizwan.claude-dev/settings/cline_mcp_settings.json — but you shouldn't navigate there. The Configure button in Cline's MCP Servers panel opens the exact file.
Should I auto-approve Exa's tools?
Search and crawl are read-only, so auto-approving them is lower-risk than file or shell tools. Still, run a few tasks with manual approval first so you understand when and how often Cline reaches for search — each call spends Exa API usage.
Exa shows connected but every search fails. Why?
The bridge is up but Exa is rejecting the calls — check that the exaApiKey parameter in the URL is correct and that your Exa account has remaining credits. The error text in Cline's task transcript usually says which.
More MCP servers for Cline.
Browse the index — every listing shows its live tool list.