topmcps
Browse MCPs
Firecrawl

Firecrawl

Official

Scrape, crawl, extract structured data, and search the web from an AI agent.

Score 90(?)FirecrawlMIT6.4kVerified Top MCPs for Web Scraping →
InstallView on GitHub

Quick answer

What it does

Exposes Firecrawl operations as MCP tools: single-page scrape, depth-limited crawl, schema-driven extract, and web search with content fetching.

Best for

  • JS-rendered page scraping
  • Multi-page crawls (docs sites)
  • Schema-driven structured extraction
  • Web search with content body

Not for

  • Sites with an existing API
  • Volumes that exceed Firecrawl's rate limits

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export FIRECRAWL_API_KEY=fc-your_key
# export FIRECRAWL_API_URL=https://api.firecrawl.dev
claude mcp add firecrawl -- npx -y firecrawl-mcp

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "firecrawl-mcp"
          ],
          "env": {
            "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
            "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
          }
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.firecrawl]
command = "npx"
args = [
  "-y",
  "firecrawl-mcp",
]
env = { FIRECRAWL_API_KEY = "${FIRECRAWL_API_KEY}", FIRECRAWL_API_URL = "${FIRECRAWL_API_URL}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "firecrawl": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "firecrawl-mcp"
        ]
      },
      "env": {
        "FIRECRAWL_API_KEY": "${FIRECRAWL_API_KEY}",
        "FIRECRAWL_API_URL": "${FIRECRAWL_API_URL}"
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Firecrawl doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set FIRECRAWL_API_KEY, FIRECRAWL_API_URL in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. web scraping work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-scraping
Compare Firecrawl against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Firecrawl MCP vs [Fetch MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/firecrawl
- top-mcps.com listing for Fetch
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Firecrawl MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/firecrawl (fetch https://top-mcps.com/mcp/firecrawl.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (FIRECRAWL_API_KEY, FIRECRAWL_API_URL) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Web Scraping MCPs

Other tools in the same category worth evaluating.

Fetch

Retrieve web pages and convert them to clean markdown.

web, fetch, markdown, scraping
1 minLow
Puppeteer

Full browser automation: navigate, click, screenshot, and scrape.

browser, automation, scraping, puppeteer
5 minMedium
Playwright
Official

Official Microsoft browser automation across Chromium, Firefox, and WebKit.

browser, automation, playwright, testing
5 minMedium

Compared with Firecrawl

Side-by-side breakdowns for the choices people most often weigh against this MCP.

FirecrawlvsAgentQLFirecrawlvsFetchFirecrawlvsPlaywrightFirecrawlvsBrowserbase

Exploring Top MCPs for Web Scraping? See all Web Scraping MCPs →