Serverdex comparison
Exa MCP vs Tavily MCP
Web search built for AI agents: search the live web and return results an LLM can use, from the search provider's own MCP server.
Every figure below is read from the Serverdex index of the official MCP registry on November 19, 2026: repository data from GitHub, transport and credentials from each server's registry entry, and the live check from a credential-free MCP handshake. Nothing here is an opinion.
Exa
ai.exa/exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Exa MCP
Side by side
| Exa | Tavily MCP | |
|---|---|---|
| Publisher | exa-labs | tavily-ai |
| Category | Search & Web | Search & Web |
| GitHub stars | 5,241 | 2,495 |
| Forks | 412 | 310 |
| Open issues | 7 | 64 |
| Last push | Nov 17, 2026 | Nov 13, 2026 |
| Maintenance | Active | Active |
| Licence | MIT | MIT |
| Language | TypeScript | TypeScript |
| How it runs | Hosted (streamable-http) | Local package (npm) |
| Credentials | Answered with no credentials | Local: needs an environment variable (TAVILY_API_KEY) |
| Live check | Working · 63 ms | Local only — nothing to call |
| Tools listed | 2 | — |
| Context cost (estimate) | ≈604 tokens | — |
| Registry version | 3.4.1 | 0.2.15 |
| First published | Sep 23, 2026 | Jan 26, 2026 |
What the data says
- Exa has more GitHub stars: 5,241 against 2,495 for Tavily MCP.
- Both repositories were pushed to within the last 90 days (Exa: Nov 17, 2026; Tavily MCP: Nov 13, 2026).
- Exa publishes a hosted endpoint; Tavily MCP is installed locally as a package.
- Exa's hosted endpoint answered the live check with no credentials; Tavily MCP has no hosted endpoint to call.
- Both ship under the MIT licence.
Install either one
Both server pages carry the config from the registry, one-click install for Cursor and VS Code, and the one-line command for Claude Code and Codex:
Questions people ask
- What do Exa and Tavily MCP have in common?
- Web search built for AI agents: search the live web and return results an LLM can use, from the search provider's own MCP server.
- Exa or Tavily MCP: which one should I install?
- Exa has more GitHub stars: 5,241 against 2,495 for Tavily MCP. Both repositories were pushed to within the last 90 days (Exa: Nov 17, 2026; Tavily MCP: Nov 13, 2026). Exa publishes a hosted endpoint; Tavily MCP is installed locally as a package. Exa's hosted endpoint answered the live check with no credentials; Tavily MCP has no hosted endpoint to call. Both ship under the MIT licence. Pick the one whose transport fits your client (hosted endpoints need a client that speaks Streamable HTTP; local packages need the runtime installed) and whose credentials you can provide; stars are a popularity signal, not a verdict on code quality.
- Where do these numbers come from?
- From the Serverdex index of the official MCP registry as of November 19, 2026: stars, forks, issues, last push, licence and language from each GitHub repository; transport and environment variables from the registry's server.json; the live check from a credential-free initialize + tools/list call to the hosted endpoint, about once a day. This page is rebuilt daily.
Related comparisons: Brave Search MCP vs Exa MCP, Firecrawl MCP vs Tavily MCP, Brave Search MCP vs Tavily MCP. All comparisons.