Exa MCP Server
MCP server that connects AI agents to Exa for web search, webpage content fetching and multi-step research.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 5 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.
npm:@modelcontextprotocol/sdk 1.26.0MCP TypeScript SDK: Experimental tasks were not tied to the session that created them (GHSA-22jm-h49p-29qw, high, fixed in 1.32.0)npm:zod 3.25.76Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)
See 3 more
npm:@modelcontextprotocol/sdk 1.26.0— GHSA-46jr-4wx8-v453 (high), fixed in 1.32.0npm:@modelcontextprotocol/sdk 1.26.0— GHSA-6qxp-vccf-f47h (high), fixed in 1.31.0npm:@modelcontextprotocol/sdk 1.26.0— GHSA-f897-62hf-6gxq (high), fixed in 1.30.1
Linux x86_64
You need first
- Needs the network
- Keys or accounts: Exa API key or OAuth sign-in (optional; needed for higher limits and Exa Agent)
npm install -g exa-mcp-server (stdio server on PATH)
npm install -g exa-mcp-server && npm ls -g exa-mcp-server
Add it to your agent
claude mcp add exa-mcp-server -- exa-mcp-serverJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"exa-mcp-server": {
"command": "exa-mcp-server",
"args": []
}
}
}Add exa-mcp-server to your MCP client's server list, and the client will show its tools, such as web_search_exa and web_fetch_exa.
What it does
- Search the web and get clean content resultsNot tested
- Fetch webpages as markdownNot tested
- Run multi-step research agentsNot tested
- Search with domain and date filtersNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- 0 of 4 features work
- Works offline
Good for
- search the web from an AI agent
- read a webpage as clean markdown
- run multi-step research with an Exa Agent
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client connects and lists its tools
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version 3.4.3
An MCP client handshake over stdio listed 2 tools.
Differences the test machine hit
- README: Install with `claude plugin install exa@claude-plugins-official` or `codex mcp add exa --url https://mcp.exa.ai/mcp`
In the test: Neither client CLI is installed here, and both commands only connect to Exa's hosted server. The npm package linked from the README (`npm install -g exa-mcp-server`) gives a local stdio server called `exa-mcp-server`. - README: The hosted MCP server works anonymously with rate limits
In the test: The local npm stdio server needs EXA_API_KEY for tool calls. Without it, web_search_exa and web_fetch_exa return tool errors, and the bundled code says 'API key must be provided as an argument or as an environment variable (EXA_API_KEY)'. - README: Enable optional tools by appending ?tools=... to the MCP URL
In the test: For the local server, optional tools are enabled with the ENABLED_TOOLS or TOOLS environment variable (seen in the bundled source).