Skip to main content
hc
Submit
mcpSource-backed
Firecrawl logo

Firecrawl MCP Server

Official Firecrawl MCP server for scraping, crawling, mapping, searching, and extracting web content through Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, and other MCP clients.

by Firecrawl · submitted by JSONbored·added 2026-06-05·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/firecrawl-mcp-server
Source URLs
https://github.com/firecrawl/firecrawl-docs/blob/main/mcp-server.mdx, https://github.com/firecrawl/firecrawl-mcp-server
Brand
Firecrawl
Brand domain
firecrawl.dev
Brand asset source
brandfetch
Safety notes
Crawling and scraping can trigger rate limits, terms-of-service issues, or accidental collection of sensitive pages., Use selected tools and narrow prompts instead of exposing broad scrape/crawl behavior to every agent task.
Privacy notes
Scraped pages, extraction outputs, and search results can include personal data, tokens in URLs, or private content if the agent is pointed at authenticated pages., Keep the Firecrawl API key out of repository config and shared screenshots.
Author
Firecrawl
Submitted by
JSONbored
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

5 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Network & hosting1General15 minutes

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 2 risk areas. Review closely: credentials & tokens.

2 areas
  • SafetyGeneralCrawling and scraping can trigger rate limits, terms-of-service issues, or accidental collection of sensitive pages.
  • SafetyGeneralUse selected tools and narrow prompts instead of exposing broad scrape/crawl behavior to every agent task.
  • PrivacyCredentials & tokensScraped pages, extraction outputs, and search results can include personal data, tokens in URLs, or private content if the agent is pointed at authenticated pages.
  • PrivacyCredentials & tokensKeep the Firecrawl API key out of repository config and shared screenshots.

Safety notes

  • Crawling and scraping can trigger rate limits, terms-of-service issues, or accidental collection of sensitive pages.
  • Use selected tools and narrow prompts instead of exposing broad scrape/crawl behavior to every agent task.

Privacy notes

  • Scraped pages, extraction outputs, and search results can include personal data, tokens in URLs, or private content if the agent is pointed at authenticated pages.
  • Keep the Firecrawl API key out of repository config and shared screenshots.

Prerequisites

  • A Firecrawl API key.
  • Node.js and npx for local stdio use, or a client that supports hosted HTTP MCP endpoints.
  • Clear rules for what sites the agent is allowed to crawl or scrape.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": {
        "FIRECRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

About this resource

Content

Firecrawl MCP exposes Firecrawl web data tools through Model Context Protocol. The official documentation covers a hosted endpoint and local npx setup for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Google Antigravity, and n8n. Typical tools include scraping, crawling, mapping, searching, and structured extraction.

Installation

For Claude Code local stdio setup:

claude mcp add firecrawl -e FIRECRAWL_API_KEY=your-api-key -- npx -y firecrawl-mcp

For hosted HTTP setup, use Firecrawl's documented endpoint pattern and pass the API key through the client-supported auth mechanism. For local JSON config:

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

Use Cases

  • Scrape a public documentation page and summarize key implementation details.
  • Crawl a small website section before drafting migration notes.
  • Map available URLs before deciding what to fetch.
  • Extract structured fields from pages where a normal browser search is too shallow.
  • Give an agent web research tools while keeping API credentials in local config.

Safety and Privacy

Firecrawl is powerful enough to collect more data than intended. Use it with explicit domains, bounded page counts, and prompts that forbid authenticated or private pages unless that access is intentional. Keep API keys in environment variables or client secret storage.

Duplicate Check

content/tools/firecrawl.mdx lists Firecrawl as a tool. This MCP entry is a separate installable integration for MCP clients and belongs in content/mcp.

References

#firecrawl#scraping#crawling#extraction#web-search

Source citations

Add this badge to your README

Show that Firecrawl MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/firecrawl-mcp-server.svg)](https://heyclau.de/entry/mcp/firecrawl-mcp-server)

How it compares

Firecrawl MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Firecrawl logoFirecrawl MCP Server

Official Firecrawl MCP server for scraping, crawling, mapping, searching, and extracting web content through Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, and other MCP clients.

Open dossier
WebClaw logoWebClaw MCP Server

Local-first MCP server for web scraping, crawling, URL mapping, batch extraction, structured extraction, summarization, diffing, brand extraction, and optional hosted API fallback for bot-protected pages.

Open dossier
AgentQL logoAgentQL MCP Server

AgentQL MCP server for extracting structured JSON from public webpages using a URL and natural-language extraction prompt.

Open dossier
Bright Data logoBright Data Web MCP Server

MCP server that connects Claude to Bright Data web search, scraping, browser automation, public web datasets, and package metadata tools.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersJSONboredoktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandFirecrawl logoFirecrawlWebClaw logoWebClawAgentQL logoAgentQLBright Data logoBright Data
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorFirecrawlWebClawAgentQLBright Data
Added2026-06-052026-06-062026-06-062026-06-05
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Crawling and scraping can trigger rate limits, terms-of-service issues, or accidental collection of sensitive pages. Use selected tools and narrow prompts instead of exposing broad scrape/crawl behavior to every agent task.✓WebClaw MCP Server can scrape one URL, crawl same-origin links, map URLs, batch multiple URLs, extract structured data, summarize pages, compare snapshots, and extract brand metadata. Scraping, crawling, search, research, and hosted fallback can trigger target-site rate limits, bot protections, legal restrictions, or terms-of-service limits. The server validates public HTTP URLs and rejects private or internal destinations, but operators should still avoid fetching internal, secret, customer-specific, or credential-bearing URLs. Cookie-bearing requests, proxies, and browser profiles can expose authenticated sessions or route traffic through external infrastructure. Setting `WEBCLAW_API_KEY` enables hosted API fallback, which can send target URLs and page context to the WebClaw service. Structured extraction and summarization may use configured LLM providers; review provider data handling before enabling those tools with sensitive pages.✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API. The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited. Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns. The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies. Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.✓This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs. Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection. `PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact. The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens. Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
Privacy notes✓Scraped pages, extraction outputs, and search results can include personal data, tokens in URLs, or private content if the agent is pointed at authenticated pages. Keep the Firecrawl API key out of repository config and shared screenshots.✓URLs, fetched page content, crawl results, extracted structured data, snapshots, brand metadata, cookies, proxy settings, API keys, and LLM prompts can be exposed to the MCP client. Crawled pages may include personal data, customer content, non-public links, access tokens embedded in URLs, or site-specific identifiers. Diff snapshots and exported JSON can preserve page content longer than expected; store and delete them according to the workflow's retention needs. Hosted fallback, proxy providers, search/research APIs, and LLM providers may observe target URLs, headers, cookies, prompts, and extracted content when enabled. Redact sensitive URLs and extracted data before sharing MCP transcripts, crawl results, logs, or generated RAG context.✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API. Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material. AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files. Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.✓Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files. Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider. Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions. Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Prerequisites
  • A Firecrawl API key.
  • Node.js and npx for local stdio use, or a client that supports hosted HTTP MCP endpoints.
  • Clear rules for what sites the agent is allowed to crawl or scrape.
  • Node.js for the `create-webclaw` installer, or Rust/Cargo when building the MCP binary from source.
  • Review of AGPL-3.0 obligations before redistributing or operating modified server versions.
  • Review of target-site terms, robots expectations, rate limits, and scraping permissions.
  • Optional `WEBCLAW_API_KEY` only when hosted API fallback is acceptable for bot-protected or JavaScript-heavy pages.
  • Node.js and npx available to the MCP client runtime.
  • AgentQL API key from the AgentQL developer portal.
  • Approved list of public webpages or domains Claude may query.
  • Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
  • Node.js and npx available to the MCP client runtime.
  • Bright Data account and API token stored as `API_TOKEN`.
  • Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms.
  • A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Install
claude mcp add firecrawl -e FIRECRAWL_API_KEY=your-api-key -- npx -y firecrawl-mcp
npx create-webclaw
npx -y agentql-mcp
npx @brightdata/mcp
Config
{
  "mcpServers": {
    "firecrawl": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": {
        "FIRECRAWL_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Manual-only setup:
npx create-webclaw
{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "<your-agentql-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "bright-data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "YOUR_BRIGHT_DATA_API_TOKEN",
        "GROUPS": "code,research",
        "RATE_LIMIT": "100/1h"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.