Field note
Exa documents a single hosted MCP endpoint, https://mcp.exa.ai/mcp, that exposes web search, code search, an Exa Agent and Exa Connect to any MCP client, and the install list now covers Cursor, VS Code, ChatGPT and Codex, Claude Code, Claude Web, Desktop and Cowork, Grok Build, OpenCode, Kiro, Gemini CLI, Warp and v0. The server is open source.
The mechanism is distribution rather than capability: one URL, added with a one-line command such as codex mcp add exa or claude mcp add --transport http exa, and in several clients the same thing arrives as a plugin that bundles the server together with Exa's skills. A retrieval vendor that ships a hosted endpoint no longer needs an integration per client, because the client already speaks the protocol.
That is the practical payoff of the work tracked in the MCP topic hub, and it puts Exa in the same position as Mintlify's retrieval surface for developer documentation: the index competes on recall and freshness while the transport stops being a differentiator.
This is vendor documentation describing setup, not a measurement of search quality or of how the client passes results into a model's context. The condition to watch is whether hosted MCP endpoints start publishing per-client behaviour, because a shared protocol hides real differences in how each client truncates, caches and attributes what it retrieves.