Firecrawl MCP Server
Firecrawl MCP Server is an MCP server published by Firecrawl, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Firecrawl. Last verified 2026-08-25.
Does Firecrawl MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Firecrawl MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is Firecrawl MCP Server a first-party (official) MCP server?
Yes. Firecrawl MCP Server is the first-party MCP server published by Firecrawl (last verified 2026-08-25).
How do I connect to Firecrawl MCP Server?
Firecrawl MCP Server is available via a hosted remote endpoint at https://mcp.firecrawl.dev/v2/mcp, the package npm:firecrawl-mcp, the official MCP Registry under io.github.firecrawl/firecrawl-mcp-server, the source repository at https://github.com/firecrawl/firecrawl-mcp-server. Authentication: api_key. Transports: sse-legacy, stdio.
What tools does Firecrawl MCP Server expose?
Firecrawl MCP Server exposes 3 tools, including firecrawl_scrape, firecrawl_search, firecrawl_parse (last verified 2026-08-25).
Does Firecrawl MCP Server support MCP revision 2025-11-25?
Yes. Firecrawl MCP Server supports MCP revision 2025-11-25 (checked 2026-08-25).
Does Firecrawl MCP Server support MCP revision 2026-07-28?
No. Firecrawl MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-07).
When were Firecrawl MCP Server's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does Firecrawl MCP Server expose?
3 tools verified.
firecrawl_scrapefirecrawl_searchfirecrawl_parse
Which MCP concepts apply to Firecrawl MCP Server?
- Streamable HTTP - MCP's HTTP transport, introduced in the 2025-03-26 revision as the replacement for the original HTTP+SSE transport. A single endpoint accepts JSON-RPC POST requests; since 2026-07-28, requests must carry the Mcp-Method and Mcp-Name headers for header-based routing, and the legacy HTTP+SSE transport is formally deprecated.
The Firecrawl MCP Server fronts Firecrawl's web data API: search with
full page content, URL scraping into structured data, site mapping,
crawling, extraction, page interaction, and asynchronous research
agents. Firecrawl operates three hosted endpoints: the main server at
https://mcp.firecrawl.dev/v2/mcp, which serves scrape, search, and
interact on a keyless free tier and unlocks account tools with a
bearer API key; an interactive OAuth variant at /v2/mcp-oauth; and a
read-only search-only surface at /v2/mcp-search exposing six tools. A
local stdio install runs via npx -y firecrawl-mcp with
FIRECRAWL_API_KEY, or against a self-hosted Firecrawl instance via
FIRECRAWL_API_URL.
Spec support is legacy, established first-hand. A 2026-08-07 probe of
the hosted endpoint rejected a server/discover call at 2026-07-28 with
the error "Unsupported protocol version: 2026-07-28 (supported versions:
2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)", and a
legacy initialize then negotiated 2025-11-25, identifying itself as
firecrawl-fastmcp 3.23.5. The server is built on the third-party
fastmcp framework rather than the official TypeScript SDK, with no
direct @modelcontextprotocol/sdk dependency.
The publisher was formerly Mendable AI: the old mendableai GitHub organization now exists only as a pointer named "Mendable AI is now Firecrawl", and the README still labels a Smithery install path under the old scope as legacy. One bookkeeping quirk: recent versions publish to npm and the MCP Registry without matching git tags; the repository's GitHub releases stop at v3.2.1 (September 2025) while npm carries 3.23.5.
Which MCP spec revisions does Firecrawl MCP Server support?
Firecrawl MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Firecrawl MCP Server?
Ranked #16 in The MCP 500 with Adoption Index 68.97 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 27,437 | API · |
| GitHub stars | 7,458 | API · |
| GitHub forks | 884 | API · |
| Last push | 2026-09-14T03:01:19Z | API · |
| Repository archived | no | API · |
Repository and package signals for Firecrawl MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 157
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: batch-processing, claude, content-extraction, data-collection, firecrawl, firecrawl-ai, javascript-rendering, llm-tools, mcp, mcp-server, model-context-protocol, search-api, web-crawler, web-scraping — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
3.24.0- Last published
- First published
- Releases
- 107
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 4
- Unpacked size
- 164 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.95 (High).
- Official MCP Registry record io.github.firecrawl/firecrawl-mcp-server version 3.23.4 (published 2026-08-06) - npm package firecrawl-mcp, stdio transport, repository firecrawl/firecrawl-mcp-server - accessed
- firecrawl/firecrawl-mcp-server README - "Official Firecrawl MCP Server"; stdio run via npx -y firecrawl-mcp with FIRECRAWL_API_KEY; hosted endpoints documented as https://mcp.firecrawl.dev/v2/mcp (keyless free tier for scrape, search, interact; other tools need a key), https://mcp.firecrawl.dev/v2/mcp-oauth (interactive OAuth), and https://mcp.firecrawl.dev/v2/mcp-search (read-only six-tool search surface); tools include firecrawl_scrape, firecrawl_map, firecrawl_crawl, firecrawl_extract, firecrawl_search, firecrawl_agent - accessed
- Endpoint probe of https://mcp.firecrawl.dev/v2/mcp - a server/discover call at 2026-07-28 returned JSON-RPC error -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; a follow-up legacy initialize at 2025-11-25 negotiated protocolVersion 2025-11-25 with serverInfo firecrawl-fastmcp 3.23.5, returned over an SSE-framed streamable-http response - accessed
- Firecrawl docs "MCP setup guides - OAuth" - documents connecting clients to https://mcp.firecrawl.dev/v2/mcp-oauth via OAuth 2.0 Authorization Code with PKCE, and https://mcp.firecrawl.dev/v2/mcp with an Authorization Bearer FIRECRAWL_API_KEY header - accessed
- Staleness re-verification via the GitHub API - repository firecrawl/firecrawl-mcp-server active (pushed 2026-08-14, not archived), latest release v3.2.1 (2025-09-26); entity facts unchanged - accessed
- Endpoint re-probe - server/discover at 2026-07-28 again rejected with error -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; legacy status unchanged - accessed
- Endpoint probe of https://mcp.firecrawl.dev/v2/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 3 tools - accessed