Serverdex comparison
Firecrawl MCP vs Tavily MCP
Fetch and extract web content for an AI client: crawl or scrape pages and return clean text or structured data.
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.
Firecrawl MCP Server
io.github.firecrawl/firecrawl-mcp-server
Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.
Firecrawl MCP
Side by side
| Firecrawl MCP Server | Tavily MCP | |
|---|---|---|
| Publisher | firecrawl | tavily-ai |
| Category | Search & Web | Search & Web |
| GitHub stars | 7,819 | 2,495 |
| Forks | 932 | 310 |
| Open issues | 192 | 64 |
| Last push | Nov 14, 2026 | Nov 13, 2026 |
| Maintenance | Active | Active |
| Licence | MIT | MIT |
| Language | JavaScript | TypeScript |
| How it runs | Hosted (streamable-http) + Local package (npm) | Local package (npm) |
| Credentials | Answered with no credentials | Local: needs an environment variable (TAVILY_API_KEY) |
| Live check | Working · 195 ms | Local only — nothing to call |
| Tools listed | 3 | — |
| Context cost (estimate) | ≈6.6k tokens | — |
| Registry version | 3.41.0 | 0.2.15 |
| First published | Nov 19, 2026 | Jan 26, 2026 |
What the data says
- Firecrawl MCP Server has more GitHub stars: 7,819 against 2,495 for Tavily MCP.
- Both repositories were pushed to within the last 90 days (Firecrawl MCP Server: Nov 14, 2026; Tavily MCP: Nov 13, 2026).
- Firecrawl MCP Server publishes a hosted endpoint; Tavily MCP is installed locally as a package.
- Firecrawl MCP Server'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 Firecrawl MCP Server and Tavily MCP have in common?
- Fetch and extract web content for an AI client: crawl or scrape pages and return clean text or structured data.
- Firecrawl MCP Server or Tavily MCP: which one should I install?
- Firecrawl MCP Server has more GitHub stars: 7,819 against 2,495 for Tavily MCP. Both repositories were pushed to within the last 90 days (Firecrawl MCP Server: Nov 14, 2026; Tavily MCP: Nov 13, 2026). Firecrawl MCP Server publishes a hosted endpoint; Tavily MCP is installed locally as a package. Firecrawl MCP Server'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: Exa MCP vs Tavily MCP, Brave Search MCP vs Tavily MCP. All comparisons.