Firecrawl MCP Server review
TestedMCP server for Firecrawl — search, scrape, and interact with the web. · Firecrawl MCP Server directory profile
The only server to pass the entire suite
Firecrawl passed all 8 of 8 tasks in our benchmark run — the only service to clear the two tasks that separated the field: scraping a page whose content only exists after client-side JavaScript rendering, and returning schema-shaped JSON from a structured-extraction prompt. It did so at a 320 ms median tool-call latency.
Measured strengths
- Passed the JavaScript-rendered scrape (294 ms) that three of five competitors failed in the same run
- Only benchmarked service supporting all three canonical task types, including structured JSON extraction
- Every search task completed in under 310 ms
- 95th-percentile latency of 1.9 s — second-tightest in the run
Measured caveats
- Structured extraction was its slowest single task at 2.6 s
- No pay-as-you-go pricing exists — usage is bought through monthly plan credits (verified 2026-07-17)
- Our per-task cost figure (~4 credits) is a conservative estimate, not metered usage
Pricing
Plan-based credits, no pay-as-you-go (firecrawl.dev/pricing, checked 2026-07-17): Free 1,000 credits/mo; Hobby $18/mo for 5,000 credits ($0.0036/credit); Standard $49/mo for 100,000 credits ($0.00049/credit). Operations: scrape 1 credit/page, search 2 credits per 10 results.
Benchmark results
Run 20260717T113200Z-7113 · promoted 2026-07-17 · harness 88581d0 · how these numbers are produced
- Success rate
- 100% (8 applicable tasks)
- Latency p50 / p95
- 320 ms / 1938 ms
- Cost per task (estimated)
- ~$0.014 (4 credits)
Capability coverage
-
scrape_markdown: supported -
web_search: supported -
structured_extract: supported
Task-by-task outcomes
| Task | Outcome | Latency |
|---|---|---|
| Scrape a minimal static page | passed | 547 ms |
| Scrape a long-form encyclopedia article | passed | 716 ms |
| Scrape a technical documentation page | passed | 338 ms |
| Scrape a JavaScript-rendered page | passed | 294 ms |
| Known-answer search (historically stable fact) | passed | 243 ms |
| Known-answer search (protocol constant) | passed | 245 ms |
| Navigational search for a canonical domain | passed | 302 ms |
| Extract a titled summary as structured JSON | passed | 2596 ms |