Skip to main content
Developers use Firecrawl’s MCP server to add web scraping to Claude Desktop, Cursor, and other AI coding assistants.

​
Start with a Template

MCP Server Firecrawl

Official MCP server - Add web scraping to Claude Desktop and Cursor

Open Lovable

Build complete applications from any website instantly
Get started with MCP in minutes. Follow our setup guide to integrate Firecrawl into Claude Desktop or Cursor.

​
How It Works

Integrate Firecrawl directly into your AI coding workflow through Model Context Protocol. Once configured, your AI assistant gains access to a set of web scraping tools it can call on your behalf:
ToolWhat it does
ScrapeExtract content or structured data from a single URL
Batch ScrapeExtract content from multiple known URLs in parallel
MapDiscover all indexed URLs on a website
CrawlWalk a site section and extract content from every page
SearchSearch the web and optionally extract content from results
Your assistant picks the right tool automatically — ask it to “read the Next.js docs” and it will scrape; ask it to “find all blog posts on example.com” and it will map then batch scrape.

​
Why Developers Choose Firecrawl MCP

​
Build Smarter AI Assistants

Give your AI real-time access to documentation, APIs, and web resources. Reduce outdated information and hallucinations by providing your assistant with the latest data.

​
Zero Infrastructure Required

No servers to manage, no crawlers to maintain. Just configure once and your AI assistant can access websites instantly through the Model Context Protocol.

​
Customer Stories

BotpressDiscover how Botpress uses Firecrawl to streamline knowledge base population and improve developer experience.

Answer HQLearn how Answer HQ uses Firecrawl to help businesses import website data and build intelligent support assistants.

​
FAQs

Currently, Claude Desktop and Cursor have native MCP support. More AI assistants are adding support regularly. You can also use the MCP SDK to build custom integrations.
VS Code and other IDEs can use MCP through community extensions or terminal integrations. Native support varies by IDE. Check our GitHub repository for IDE-specific setup guides.
The MCP server automatically caches responses for 15 minutes. You can configure cache duration in your MCP server settings or implement custom caching logic.
MCP requests use your standard Firecrawl API rate limits. We recommend batching related requests and using caching for frequently accessed documentation.
Follow our setup guide to configure MCP. You’ll need to add your Firecrawl API key to your MCP configuration file. The process takes just a few minutes.