Skip to main content
The Firecrawl MCP server enables AI assistants like Claude Desktop to scrape, crawl, and extract web data using the Model Context Protocol (MCP). It provides seamless integration with any MCP-compatible client.

What is MCP?

The Model Context Protocol (MCP) is an open protocol that standardizes how AI applications connect to data sources. The Firecrawl MCP server implements this protocol, allowing AI assistants to access web scraping capabilities.

Installation

For Claude Desktop

Add the Firecrawl MCP server to your Claude Desktop configuration:
  1. Install the MCP server:
  1. Configure Claude Desktop:
Edit your Claude Desktop config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the Firecrawl server:
  1. Restart Claude Desktop
The Firecrawl tools will now be available in Claude Desktop.

For Other MCP Clients

The server works with any MCP-compatible client. Install and configure according to your client’s documentation:
Then add it to your client’s MCP configuration.

Authentication

Get your API key from firecrawl.dev and set it in your MCP configuration:

Available Tools

The MCP server provides the following tools:

1. Scrape

Scrape a single URL and get clean, LLM-ready content. Parameters:
  • url (required) - The URL to scrape
  • formats - Output formats: markdown, html, screenshot, links
  • onlyMainContent - Extract only main content (default: true)
  • includeTags - HTML tags to include
  • excludeTags - HTML tags to exclude
Example Usage in Claude:

2. Crawl

Crawl an entire website and get content from all pages. Parameters:
  • url (required) - Starting URL
  • limit - Maximum pages to crawl (default: 100)
  • maxDepth - Maximum discovery depth
  • excludePaths - Paths to exclude (e.g., ["blog/*", "admin/*"])
  • includePaths - Paths to include
  • formats - Output formats for scraped pages
Example Usage in Claude:

3. Map

Discover all URLs on a website. Parameters:
  • url (required) - Website URL
  • search - Search query to filter URLs
  • limit - Maximum URLs to return
  • includeSubdomains - Include subdomains
Example Usage in Claude:
Search the web and optionally scrape results. Parameters:
  • query (required) - Search query
  • limit - Number of results (default: 10)
  • scrapeResults - Also scrape the search results
  • formats - Output formats for scraped content
Example Usage in Claude:

5. Agent

Autonomous AI agent for web research and data extraction. Parameters:
  • prompt (required) - What you want the agent to find
  • urls - Optional URLs to focus on
  • model - Model to use: spark-1-mini (default), spark-1-pro
  • schema - JSON schema for structured output
Example Usage in Claude:

6. Batch Scrape

Scrape multiple URLs in parallel. Parameters:
  • urls (required) - Array of URLs to scrape
  • formats - Output formats
Example Usage in Claude:

Usage Examples

With Claude Desktop

Once configured, you can ask Claude naturally: Scraping:
Crawling:
Agent Research:
Search:
Batch Processing:

Programmatic Usage

You can also run the MCP server programmatically:

Configuration

Environment Variables

Advanced Configuration

For custom configurations, you can extend the server:

Tool Response Format

All tools return structured data that Claude can easily parse:

Scrape Response

Crawl Response

Agent Response

Error Handling

The MCP server provides clear error messages:
Common error codes:
  • AUTHENTICATION_ERROR - Invalid or missing API key
  • RATE_LIMIT_ERROR - Rate limit exceeded
  • INVALID_URL - Invalid URL format
  • SCRAPE_FAILED - Failed to scrape the URL
  • CRAWL_TIMEOUT - Crawl operation timed out

Debugging

Enable debug logging:
Logs will be written to:
  • macOS/Linux: ~/.config/firecrawl-mcp/logs/
  • Windows: %APPDATA%\firecrawl-mcp\logs\

Updating

Update to the latest version:
Then restart your MCP client (e.g., Claude Desktop).

Uninstalling

  1. Remove the server configuration from your MCP client config
  2. Uninstall the package:

Supported Clients

The Firecrawl MCP server works with:
  • Claude Desktop (Anthropic)
  • Continue (VS Code extension)
  • Cody (Sourcegraph)
  • Any MCP-compatible client

Security

  • API keys are stored in your local MCP configuration
  • All requests are made directly from your machine to the Firecrawl API
  • No data is sent to third parties except Firecrawl
  • Use environment variables or secure configuration files for API keys

Performance

  • Scraping is near-instant for most pages
  • Crawling time depends on the number of pages (typically 1-5 minutes for 50-100 pages)
  • Agent tasks vary based on complexity (30 seconds to 2 minutes)
  • Batch scraping processes URLs in parallel for optimal speed

Limitations

  • Maximum crawl limit: 1000 pages per request
  • Maximum batch scrape: 100 URLs per request
  • Rate limits apply based on your Firecrawl plan
  • Timeout limits: 5 minutes for crawls, 2 minutes for agent tasks

Resources

Support

For help: