Firecrawl MCP server
Firecrawl publishes its own remote MCP server. Govern it with Anlyon: adopt only the tools you choose, and have a person approve the ones that delete data or can't be undone. Your agent never holds your Firecrawl credentials.
- endpoint
- https://mcp.firecrawl.dev/v2/mcp
- registry name
- io.github.firecrawl/firecrawl-mcp-server
- published by
- github.com/firecrawl
- verified
- GitHub organisation, by the MCP Registry
- transport
- Streamable HTTP
- 0 delete or cancel
- 0 can't be undone
- 2 change things
- 1 only read
- 1.Add the serverPress Govern it. The console opens with mcp.firecrawl.dev filled in and reads what sign-in it needs. Nothing is saved yet.
- 2.Connect FirecrawlConnect the way the server asks: sign in, or add a key. The credential stays in Anlyon's vault, and your agent never holds it.
- 3.Adopt what you chooseEach tool you adopt becomes an action with the approval you set. A tool you skip can't be called.
Which tools need a person? Approve the ones you can't take back.
anlyon.dev's scan of Firecrawl's server lists 3 tools: 2 change things and 1 only read. Scanned 2026-11-03. A class is a suggestion from what the server says about its tools.
- Put the 2 tools that change things under a limit, or approval where a mistake is costly.
- Let the 1 tool that only reads through.
Questions. Firecrawl's official MCP server.
It is Firecrawl's own server: the MCP Registry verified its publisher as the GitHub organisation github.com/firecrawl, and its endpoint, mcp.firecrawl.dev, is on Firecrawl's domain. What your agent can do with it depends on which tools it may call. With Anlyon it reaches only the tools you adopt, and the ones that delete data or can't be undone can wait for a person's approval.
anlyon.dev's scan classes none of Firecrawl's tools as deleting or cancelling things. Tools that change things can still be held for approval in Anlyon.
https://mcp.firecrawl.dev/v2/mcp. Its name in the MCP Registry is io.github.firecrawl/firecrawl-mcp-server.