aicoolies logo

Firecrawl MCP Server

Web scraping and crawling via MCP for AI agents

Share
freemiumOpen Source
Visit Website →

Firecrawl MCP Server is the official MCP integration for Firecrawl, giving Cursor, Claude, Windsurf, and other MCP clients scrape, crawl, map, search, extract, and agent-style web research tools. It now supports a hosted remote endpoint, keyless rate-limited scrape/search/interact use, API-key/OAuth access for the full tool set, and self-hosted Firecrawl deployments.

We have a review for this tool

A detailed review by the aicoolies team — click to read

Firecrawl MCP Server is the official Model Context Protocol server for bringing Firecrawl web data tools into AI coding agents and desktop clients. The current README positions it around live-web search, scraping, crawling, mapping, extraction, browser interaction, and agent-style research, rather than as a generic browser automation server. It can be used through the hosted remote endpoint at mcp.firecrawl.dev, through an API-key endpoint for higher limits and the full tool set, or by running the npm package locally inside Claude Desktop, Cursor, Windsurf, VS Code-style MCP clients, and other compatible hosts.

The most important 2026 change is the hosted MCP path. Firecrawl now documents a keyless free tier where scrape, search, and interact work without an API key but are rate-limited; crawl, map, agent, extract, and higher-limit usage still require an API key or OAuth. That makes the server easier to trial, while production teams still need to model Firecrawl API credits, concurrency limits, retries, and credit monitoring. The upstream repo also documents cloud and self-hosted support, including a custom FIRECRAWL_API_URL for teams that run Firecrawl inside their own environment.

Pricing should be read as Firecrawl platform pricing, not as a separate MCP-server subscription. The public pricing page lists a Free plan with 1,000 credits per month, Hobby at $16/month billed yearly, Standard at $83/month billed yearly, Growth at $333/month billed yearly, Scale at $599/month billed yearly for 1,000,000 credits, and Enterprise custom pricing. The GitHub repository is MIT-licensed, active, and had about 6.7K stars at verification time, but reliability, anti-bot handling, and credit burn still need workload-specific testing before a review page should make hands-on claims.

Pricing

Hosted keyless tier supports rate-limited scrape/search/interact; Firecrawl pricing lists Free 1,000 credits/mo, Hobby $16/mo, Standard $83/mo, Growth $333/mo, Scale $599/mo, and Enterprise custom.

Platforms

Hosted MCP, API key/OAuth, npm, Claude Desktop, Cursor, Windsurf, Docker, self-hosted Firecrawl

Categories

Tags

Use Cases

Alternatives

Related Tools

Hermes Agent logo

Hermes Agent

Top Pick

Open-source AI agent framework with persistent memory, reusable skills, tools, and messaging gateways

Hermes Agent is an open-source AI agent framework with persistent memory, reusable skills, 40+ tools, cron jobs, and messaging gateways.

open-sourceOpen Source

Safari MCP Server

Apple's Safari-native MCP server for web debugging agents

Safari MCP Server is Apple's safaridriver-based MCP server in Safari Technology Preview, giving compatible coding agents local access to Safari page content, console logs, network requests, screenshots, JavaScript evaluation, interactions, viewport controls, and accessibility/performance checks.

freeTelemetry

Headroom

Context compression for LLM apps and coding agents

Headroom is an Apache-2.0 context compression layer for LLM apps and coding agents. It compresses tool output, logs, files, RAG chunks, and agent history through a local library, proxy, wrapper, or MCP server, with retrieval hooks for bringing originals back when needed. Treat its savings numbers as Headroom-reported benchmarks, not independent aicoolies measurements.

open-sourceOpen SourceTelemetry

Codebase Memory MCP

Codebase knowledge graph MCP server for AI coding agents

Codebase Memory MCP is an MIT-licensed MCP server that turns a repository into a persistent code knowledge graph for AI coding agents. It gives Claude Code, Cursor, Codex-style agents, and other MCP clients structural queries for functions, classes, call chains, routes, and architecture, helping them explore large projects without repeatedly rereading files or relying only on broad search.

open-sourceOpen SourceTelemetry
BeeAI Framework logo

BeeAI Framework

Python and TypeScript framework for production multi-agent systems

BeeAI Framework is an Apache-2.0 toolkit for building production-ready AI agents and multi-agent systems in Python and TypeScript. Its docs cover agents, tools, RAG, memory, workflows, backend providers, serving, and A2A/MCP integration surfaces, making it a vendor-neutral option for teams comparing LangGraph, CrewAI, Mastra, and related agent runtimes.

open-sourceOpen SourceTelemetry

Supabase MCP

MCP server for connecting AI assistants to Supabase projects

Supabase MCP is Supabase's Apache-2.0 server for connecting AI assistants to Supabase projects. It can expose database, configuration, and project-management workflows to MCP clients such as Cursor, Claude, and Windsurf, while the official docs emphasize permission and security review before production use, SQL changes, or high-privilege database access.

open-sourceOpen SourceTelemetry

Used in Stacks

Comparisons

Context7 vs Firecrawl MCP Server: Docs Context or Live Web Extraction?

Context7 and Firecrawl MCP Server solve different freshness problems for AI coding agents. Context7 injects version-specific library documentation into prompts, while Firecrawl brings live web search, scraping, crawling, and extraction into MCP clients. Choose Context7 first when the task is reliable API usage inside code; choose Firecrawl when the agent needs current public-web data or structured page extraction.

Context7Firecrawl MCP Server

Firecrawl MCP Server vs Playwright MCP — Crawl Stack vs Browser Automation

Firecrawl MCP Server and Playwright MCP both expose web capabilities to AI agents through MCP, but they optimize for different work. Firecrawl MCP Server is the better fit when the agent needs repeatable search, scraping, crawling, and extraction pipelines. Playwright MCP is stronger when the agent must drive a real browser, inspect UI state, click controls, and validate web flows.

Firecrawl MCP ServerPlaywright MCP

Firecrawl MCP Server vs Exa MCP Server — Crawl Stack vs Neural Search

Firecrawl MCP Server and Exa MCP Server both give agents web-data access through MCP, but they answer different questions. Exa is strongest when an agent needs neural web search and relevant sources. Firecrawl is strongest when the workflow needs search plus scraping, crawling, extraction, and clean content transformation. This comparison separates discovery, crawling depth, output quality, and agent workflow fit.

Firecrawl MCP ServerExa MCP Server