Best for
- Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
F
Firecrawl MCP Server
Official
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
GitHub source repository ↗
75FMRS · B
Source and config reviewed
Officially maintained by Firecrawl; tools cover the full range from single-page scraping to site-wide crawling, structured extraction, and an interactive agent, with usage guidance and common pitfalls documented per tool in the README. This review is a static check of source and docs, not an actual call test.
Read the scoring and verification method →The official Firecrawl-maintained MCP server, exposing the Firecrawl platform's page scraping, site-map discovery, deep crawling, structured data extraction, and an interactive browser agent to MCP-compatible AI assistants — for getting clean, ready-to-use web context.
Tools
firecrawl_scrape
Scrape a single URL's content with advanced format options
firecrawl_map
Discover all crawlable URLs under a website
firecrawl_search
Search the web and return relevant page content
firecrawl_crawl
Deep-crawl multiple pages across an entire website
firecrawl_check_crawl_status
Check the progress and status of a crawl job
firecrawl_parse
Parse already-fetched content into a structured form
firecrawl_extract
Extract structured data from a page against a given schema
firecrawl_agent
Run a browser agent to complete complex, interactive web tasks
firecrawl_agent_status
Check the execution status of an agent task
firecrawl_interact
Interact with a webpage (click, type, etc.)
firecrawl_interact_stop
Stop an in-progress web interaction session
Setup
Start via `npx -y firecrawl-mcp`, after signing up at https://www.firecrawl.dev and setting a FIRECRAWL_API_KEY env var. A self-hosted Firecrawl instance can also be pointed to via the corresponding env var.
claude_desktop_config.json
{
"mcpServers": {
"firecrawl": {
"command": "npx",
"args": ["-y", "firecrawl-mcp"],
"env": {
"FIRECRAWL_API_KEY": "<YOUR_FIRECRAWL_API_KEY>"
}
}
}
}
Fit and risk
Not for
- Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
Required permissions
- Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
Risks and side effects
- Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
Troubleshooting
- Calls return an auth error: check that FIRECRAWL_API_KEY is correct and the account has remaining quota
- A crawl job appears stuck: use firecrawl_check_crawl_status to check progress — very large sites can take a while
- Extraction returns empty: confirm the schema passed to firecrawl_extract matches the page's actual structure
Use cases
Scrape a single page's content for summarization or Q&A
Map and deep-crawl an entire site to gather content in bulk
Extract structured data (e.g. product info, pricing) from a page against a schema
Use the browser agent to complete complex scraping tasks requiring clicks or logins
Supported clients
Claude DesktopFull support
VS CodeFull support
CursorFull support
WindsurfFull support
ZedFull support
AmpFull support