Run Firecrawl MCP locally

​

Run locally

env FIRECRAWL_API_KEY=fc-YOUR_API_KEY npx -y firecrawl-mcp@3.22.4

​

Install globally

npm install -g firecrawl-mcp

​

Configuration

​

Environment Variables

​

Cloud and self-hosted API

• FIRECRAWL_API_KEY: Your Firecrawl API key
  • Required when using cloud API (default)
  • Optional when using self-hosted instance with FIRECRAWL_API_URL
• FIRECRAWL_API_URL (Optional): Custom API endpoint for self-hosted instances
  • Example: https://firecrawl.your-domain.com
  • If not provided, the cloud API will be used (requires API key)

​

Configuration Examples

export FIRECRAWL_API_KEY=your-api-key

export FIRECRAWL_API_URL=https://firecrawl.your-domain.com
export FIRECRAWL_API_KEY=your-api-key  # If your instance requires auth

​

Custom configuration with Claude Desktop

{
  "mcpServers": {
    "mcp-server-firecrawl": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": {
        "FIRECRAWL_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

​

Hosted MCP vs local MCP

• Hosted keyless mode exposes only the keyless-supported tools and is rate-limited per IP.
• Local-only file reads are available only when you run the MCP server locally.
• Webhooks and local file paths should be configured from a local or self-hosted MCP server when the agent needs access to local resources.

​

Rate Limiting