How to connect the Exa MCP server
To connect the official Exa MCP server, add https://mcp.exa.ai/mcp to your MCP client as a Streamable HTTP server, then no sign-in is needed to connect. For clients without MCP OAuth, use an API key. Exa documents setup for ChatGPT, Codex, Claude Code, Claude, Cursor, VS Code and Windsurf.
Docs reviewed 5 Nov 2026Connection tested.
Try in the browser, no sign-in →
Endpoint https://mcp.exa.ai/mcp · Registry ai.exa/exa 3.4.1
Add Exa MCP to your client
Add https://mcp.exa.ai/mcp as a custom connector in ChatGPT, then sign in when prompted.
Connect Exa MCP step by step
Before you start
- Without sign-in or an API key, search and fetch work at a free rate limit and agent_run is unavailable. Agent runs are usage-based and need OAuth or an API key; usage belongs to your Exa team. docs.exa.ai/reference
Authentication
- Your client → Exa MCP
- No authentication. docs.exa.ai/referenceregistry.modelcontextprotocol.io/v0.1
- Exa MCP → Exa API
- Not established by this guide.
Steps
- Open Exa's MCP setup instructions for your client
- Add the Exa MCP server to your client
Add https://mcp.exa.ai/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Exa also publishes a ChatGPT and Codex plugin, a Claude Code plugin, a Claude connector and a Cursor Marketplace listing, which sign you in with OAuth.
- Recommended for interactive clients: sign in with OAuth
Exa recommends OAuth for interactive clients and production use. In a client that supports MCP OAuth, connect to https://mcp.exa.ai/mcp?login instead; the client discovers Exa's authorization server and opens the browser sign-in.
- For clients without MCP OAuth, use an API key
Create an API key in the Exa dashboard and send it in the x-api-key header. Keep the key in a secret store, not in shared configuration.
- Optional: choose which tools the client sees
Exa's tools URL parameter selects the tools. An explicit list replaces the defaults, so include every tool you want, including web_search_exa and web_fetch_exa.
- List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
What we observed
- 5 Nov 2026: HTTP 200; the server returned an initialize result (exa-search-server 3.5.0) without credentials and no WWW-Authenticate challenge.
- 5 Nov 2026: initialize and tools/list succeeded without credentials from the API Tracker browser explorer: 2 tools (web_search_exa, web_fetch_exa). A web_search_exa call also returned results.
Exa MCP questions
What is the Exa MCP server URL?
The official Exa MCP server is at https://mcp.exa.ai/mcp and uses the Streamable HTTP transport.
How do I authenticate with the Exa MCP server?
No sign-in is needed to connect. Recommended for interactive clients: sign in with OAuth: Exa recommends OAuth for interactive clients and production use. In a client that supports MCP OAuth, connect to https://mcp.exa.ai/mcp?login instead; the client discovers Exa's authorization server and opens the browser sign-in. For clients without MCP OAuth, use an API key: Create an API key in the Exa dashboard and send it in the x-api-key header. Keep the key in a secret store, not in shared configuration.
Which AI clients can use the Exa MCP server?
Exa's documentation covers ChatGPT, Codex, Claude Code, Claude, Cursor, VS Code and Windsurf. Other clients that support remote Streamable HTTP MCP servers may also work.
What do I need before connecting Exa MCP?
Without sign-in or an API key, search and fetch work at a free rate limit and agent_run is unavailable. Agent runs are usage-based and need OAuth or an API key; usage belongs to your Exa team.
Has this Exa MCP guide been tested?
Exa's documentation was reviewed on 2026-11-05. The connection was tested.
Sources and review
Exa's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.
Guide source and binding
MCP connection guide (draft 0.1) for ai.exa/exa 3.4.1, bound to /remotes/0 of the Registry record by SHA-256 171a39a8e135….
- docs.exa.ai/reference/exa-mcp · checked 5 Nov 2026
- registry.modelcontextprotocol.io/v0.1/servers/ai.exa%2Fexa/versions/3.4.1 · checked 5 Nov 2026