Exa MCP Server: Tools, Setup and Security

The Exa MCP server lets an AI app search the web, read pages as clean markdown and run multi-step research jobs. Exa publishes it as a hosted server at https://mcp.exa.ai/mcp, with open-source code on GitHub. It is one of the few search servers you can try without any key.

Checked against: Exa MCP docs on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

Exa's MCP docs list which tools are on by default. The GitHub README still lists agent_run as optional. This profile follows the docs page.

Default tools:

• web_search_exa: searches the web and returns "clean, ready-to-use content."
• web_fetch_exa: reads one or more URLs as clean markdown.
• agent_run: runs an Exa Agent for multi-step research, list-building, enrichment and structured output. The docs mark it "Enabled by default with OAuth or API key." It only appears once you connect with ?login or configure an API key.

Opt-in tool:

• web_search_advanced_exa: search with filters for domains, dates, highlights, summaries and subpage crawling.

You pick tools with the tools parameter. The docs warn that an explicit list "replaces the defaults, so include every tool you want enabled." For example:

https://mcp.exa.ai/mcp?tools=web_search_exa,web_fetch_exa,agent_run

The repository also ships agent skills for research and Exa Agent runs, which load with plugin installs.

How to connect it

Most clients take the standard shape from the README:

{
  "mcpServers": {
    "exa": {
      "type": "streamable-http",
      "url": "https://mcp.exa.ai/mcp"
    }
  }
}

For Codex, the README gives:

codex mcp add exa --url https://mcp.exa.ai/mcp

For Claude, it points to the Claude plugin directory or this command:

claude plugin install exa@claude-plugins-official

The README lists more clients, including Cursor, VS Code, Gemini CLI, Windsurf (now Devin Desktop), Zed and Warp.

To sign in, use https://mcp.exa.ai/mcp?login, which the docs say starts the browser flow and bills usage to your Exa team. Clients without OAuth can send an x-api-key header. The README also mentions an exaApiKey URL parameter. A header is the safer choice, since keys in URLs can end up in logs.

Security notes

No write tools. The documented tools search, fetch and research. None of them change data in your accounts.

Keys. Prefer OAuth or a header over a key in the URL. See MCP secret leakage.

Data handling. Exa's MCP docs do not describe retention or logging. Review Exa's own policies before sending sensitive queries. Remember that your query text leaves your network.

Untrusted content. web_fetch_exa returns whatever a page says. A page can hide instructions aimed at your AI app. Read prompt injection through MCP tool results and the MCP security center.

Cost. agent_run jobs can make many searches. Keep approvals on for it if you are on a paid balance.

Pricing

Exa's pricing page says agents can call Exa "through the hosted MCP server" and lists usage prices. As of October 2026: search starts at $4 per 1,000 requests for Lite and Instant types, $7 for Auto and Fast, and $12 to $15 for Deep Search. Contents cost $1 per 1,000 pages per content type. New accounts get $10 in credits, and "your free balance resets to $10 on the first of every month."

Alternatives

• Perplexity MCP server: search plus answer, reasoning and research tools.
• Tavily MCP server: search, extract, crawl and map with a free monthly credit.
• Firecrawl MCP server: stronger on scraping and crawling whole sites.

Browse more on our MCP server profiles hub.

Next step

Search servers decide which pages AI agents read. If you want your site to be one of them, our MCP marketing and GEO work can help.

Frequently asked questions