Exa MCP Server: AI-Native Search for Claude and Cursor

The official Exa listing points to exa-labs/exa-mcp-server. It offers a hosted remote endpoint and a local stdio package. Choose the route and tool selection for the research task before giving the agent a broad question.

Docs-derived; sources checked October 17, 2026. MCPFind did not authenticate, search, fetch content, or measure usage. Configuration and access notes follow the official repository.

Choose hosted or local access

The hosted Streamable HTTP endpoint is https://mcp.exa.ai/mcp. Anonymous access is supported with rate limits. OAuth or an API key enables higher limits and Agent access; use the current documented authentication flow and account terms. Hosted access does not always require OAuth.

The local stdio route uses the exa-mcp-server package and an EXA_API_KEY:

{
  "mcpServers": {
    "exa": {
      "command": "npx",
      "args": ["-y", "exa-mcp-server"],
      "env": {
        "EXA_API_KEY": "YOUR_EXA_API_KEY"
      }
    }
  }
}

Adapt this to your client's documented configuration format and credential storage. Check current limits and billing before using the key. A client connection is not evidence that every tool is enabled or that Agent access is available.

Retain the tools your workflow needs

The documented defaults include web_search_exa and web_fetch_exa. For domain and date filters, enable web_search_advanced_exa. On the hosted endpoint, the tools= parameter replaces the defaults; it does not append to them. To retain search and fetch while adding advanced search, use:

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

Inspect the tools advertised by the connected server after changing this URL. Keep Agent access separate from this search-and-fetch workflow: it has its own authentication and usage requirements. Follow the repository's current instructions for local tool selection instead of assuming a hosted URL parameter configures a local process.

Verify a bounded research question

Choose a publisher domain, a date range, and one question with a checkable answer. For example, find a named product's release notes from a specified month on its official documentation domain.

1. Ask web_search_advanced_exa to search only that domain and date range with a small result count. Inspect its current schema for the supported filter names and values before calling it.
2. Expect titles and source URLs relevant to the question. Select one publisher URL, then ask web_fetch_exa to retrieve the content required for the answer.
3. Open the publisher page and compare the release date, version, and quoted or summarized change with the fetched output. If the date is absent or the content differs, record the limitation rather than treating the search filter as proof.
4. Distinguish an empty successful search from an authentication, rate-limit, or fetch failure. Check usage and resolve that failure before broadening the query or starting Agent research.

This test checks a specific source and answer. It does not demonstrate that Exa ranks all topics better than another provider. Compare another search integration on the same bounded question, publisher checks, and account limits. If you need a server that synthesizes an answer as part of its documented workflow, review the Perplexity guide and verify its current behavior independently.