Search. MCP servers, the command line and skills for connecting an agent to Exa.
Official server
1 server
Sourced servers by others
4
Command line
none curated
Vendor skills
none
Official server
Published by Exa's owner: we named it as the system's official server after reading its registry record, or it is published under Exa's own domain. See what first-party means.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Remote, Streamable HTTP:https://mcp.exa.ai/mcpIts record declares no header. A server may still ask you to sign in (OAuth) when a client connects.
Version 3.4.1. Registry record last changed .
Not checked. OSV is asked about npm and PyPI packages that name a version; this server lists none, or its record changed after the last read.
Servers by other publishers
4 servers for Exa that name a public repository or a package. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.
In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score. Downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.
A server is listed for Exa when we have named it as the system's official server, when its registry title or the last part of its registry name names Exa as whole words, or when it is published under Exa's own domain. See how this directory is made.
Built from agent catalog version 2026-11-13.3 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.