WEB RESEARCH / Exa
Exa MCP
Connects an assistant to Exa web search, content retrieval and optional multi-step research tools.
“Connect to Exa's hosted MCP server:”
01 / THE REASONING
Why this made the selection.
- Supports a hosted endpoint and a separately inspectable local stdio path.
- Documents tool selection and the authentication difference between anonymous search and Exa Agent.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md (installation, capability and permission sections)
- package.json
- src/stdio.ts
- src/tools/webSearch.ts
- LICENSE
Our findings
- The web-search tool declares readOnlyHint and openWorldHint; returned web content is external data.
- The local implementation supports tool-list configuration; the hosted service is subject to its own account terms.
- The README lists two default tools, web_search_exa and web_fetch_exa, and two optional tools, agent_run and web_search_advanced_exa, enabled through the tools URL parameter.
- The README prefers OAuth (forced with ?login or /mcp/oauth). An API key can instead go in the URL as exaApiKey, an Authorization: Bearer header or an x-api-key header.
- The README’s mcpServers block for other clients has a trailing comma after the url value, so it is not valid JSON as printed. It is reproduced as text. Until 2026-10-13 this record showed it re-serialised without the comma.
- At this commit package.json declares license MIT and mcpName ai.exa/exa (io.github.exa-labs/exa-mcp-server at the previous pin). The package name is still exa-mcp-server.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add https://mcp.exa.ai/mcp using the official client configuration.
- Authenticate when using Exa Agent or higher account limits; specify all required tools if overriding the defaults.
Before you start
- A remote-capable MCP client; Exa authentication for restricted capabilities.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"exa": {
"type": "streamable-http",
"url": "https://mcp.exa.ai/mcp",
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official documentation ↗Checked
https://github.com/exa-labs/exa-mcp-server/blob/e9c3b0126a3373eb1aeaca162e84d0791ff4c7f7/README.md
Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, review, configExample
- Applicable source licence ↗Checked
https://github.com/exa-labs/exa-mcp-server/blob/e9c3b0126a3373eb1aeaca162e84d0791ff4c7f7/LICENSE
Supports: license
https://github.com/exa-labs/exa-mcp-server/blob/e9c3b0126a3373eb1aeaca162e84d0791ff4c7f7/package.json
Supports: language, review, license field MIT, package name exa-mcp-server
https://github.com/exa-labs/exa-mcp-server/blob/e9c3b0126a3373eb1aeaca162e84d0791ff4c7f7/src/stdio.ts
Supports: language, review
https://github.com/exa-labs/exa-mcp-server/blob/e9c3b0126a3373eb1aeaca162e84d0791ff4c7f7/src/tools/webSearch.ts
Supports: language, review