MCP.so
Sign In

Firecrawl MCP ServerFeatured

@mendableai

Basic information

Category

Browser Automation

License

MIT

Transports

stdio

Author

mendableai

Submitted by

Victor Bruno Castro

About Firecrawl MCP Server

🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.

Firecrawl MCP Server config

Add this server to your MCP-compatible client using the configuration below.

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

Firecrawl MCP Server tools

27

Retrieve and extract content from one supplied URL through Firecrawl. Use this when the request identifies a page and needs its content or defined fields. It can return markdown, HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema; JSON is useful when the requested result has defined fields, while markdown preserves readable page content. This tool operates on a known page. For a set of pages use `firecrawl_crawl`, and to discover page URLs use `firecrawl_map` or `firecrawl_search`. Options include JavaScript render delay, cache age, main-content filtering, PII redaction, and lockdown cache-only retrieval. Browser actions may change the live page when interactive actions are enabled. Firecrawl may reuse recently indexed content instead of refetching the page, and the reuse window varies by domain. Set `maxAge: 0` to force a live fetch, or a smaller `maxAge` to bound how stale reused content may be. A successful response does not by itself confirm that the state it describes is still current. Returns the selected content formats and page metadata.

Enumerate URLs indexed under one website through Firecrawl without fetching each page's content. Use this when the request asks for a site's URL inventory, when several relevant pages must be located, or when the desired page URL is unknown. An optional `search` term narrows the URL list, while sitemap, subdomain, query-parameter, and result-limit options control coverage. Returns matching URLs rather than page bodies. Retrieve one page with `firecrawl_scrape`; collect content across multiple pages with `firecrawl_crawl`.

Search web, news, or image sources and return ranked results. Operators include quoted phrases, `-term`, `site:host`, `inurl:term`, `intitle:term`, and `related:host`; the set is non-exhaustive. `includeDomains` and `excludeDomains` are mutually exclusive hostname filters; categories limit results to GitHub, research, PDF, or developer sources. For a programming question, add `categories: ["developer"]`. It searches an index of GitHub issues, merged pull requests, repository READMEs, and curated documentation sites, and returns the hits in `data.developer` beside the web results. `categories: ["research"]` restricts these web results to research-affiliated websites and returns page snippets. The `firecrawl_research_*` tools are a separate surface that searches paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature. `scrapeOptions` can attach extracted page content; pages fetched this way use a fixed reuse window and ignore `maxAge`, so use `firecrawl_scrape` when a live fetch is required. Returns source-type result groups and usage metadata. Authenticated responses can include an `id` for optional search feedback.

Records schema-validated quality feedback for a prior `firecrawl_search` UUID `searchId`. A `good` rating requires a valuable source, `partial` a valuable source or at least one `missingContent` entry, and `bad` at least one `missingContent` entry or a query suggestion; caps are 50 `valuableSources` and 20 `missingContent` entries. Eligibility is limited to successful searches within the feedback age window. The record is idempotent per search ID. Eligible first feedback for a search can refund 1 credit; refunds are subject to the team's daily cap. The response reports whether a refund was applied, along with submission and daily-cap status.

Submit concise quality feedback for a completed search, scrape, parse, or map job. Provide the endpoint, job ID, rating, and relevant issue codes or small contextual fields; omit large page contents and raw outputs. Returns submission status, feedback ID, and accounting fields.

Start a multi-page crawl at a website URL, poll it to a terminal state, and return the final status and collected data. Scope can be bounded with include/exclude paths, depth, page limit, subdomain/external-link controls, sitemap handling, delay, and scrape options. Crawl results can be large; use conservative limits when full-site coverage is unnecessary. Webhooks and interactive scrape actions are unavailable in safe mode. Returns the crawl ID, status, and page data.

Retrieve the current status, progress, and available results for an existing crawl ID. This only reads Firecrawl job state and does not start or modify the crawl.

Deprecated compatibility entry point. Use firecrawl_scrape once per known URL with formats: ["json"] and jsonOptions containing the prompt and schema. Use firecrawl_search or firecrawl_agent before Scrape when URLs are not known.

Start an asynchronous web research job from a prompt, optional seed URLs, and an optional JSON schema. Use this for a requested synthesis across multiple sources when the task can wait for asynchronous completion. The agent can search, navigate, read pages, and assemble a structured result. This call returns only a job ID, not the research result. Read the job with `firecrawl_agent_status` until it reaches `completed` or `failed`; research commonly takes several minutes. If the job cannot finish within the task's available time, `firecrawl_search` and `firecrawl_scrape` can gather evidence synchronously.

Retrieve progress or final results for a `firecrawl_agent` job ID. A `processing` response is non-terminal and does not contain the final research result. Check again after 15–30 seconds until the status is `completed` or `failed`; complex jobs can take several minutes. If the job cannot finish within the task's available time, use `firecrawl_search` and `firecrawl_scrape` to complete the requested output. Returns job status, progress information, and result data when completed.

Open or reuse a live browser session to navigate a page, click controls, fill fields, or run browser code. Provide either `url` or `scrapeId`, and either a natural-language `prompt` or executable `code`; code can run as Bash, Python, or Node with a bounded timeout. This acts on the live site, so actions such as form submission can create persistent external side effects. Returns execution output, stdout/stderr, exit status, and session viewing URLs.

Stop the live interact session associated with a `scrapeId` and release its resources. Returns a success confirmation.

Parse one supported document into markdown, HTML, links, summary, targeted answers, or JSON matching a schema. Supported inputs include common HTML, PDF, Word, RTF, OpenDocument, and spreadsheet files; PDF parsing can be bounded with `pdfOptions.maxPages`. Local MCP reads `filePath` from the server filesystem. Hosted MCP uses two calls: first provide `filePath` to receive upload instructions, upload locally, then call again with the returned `uploadRef`; do not send both fields together. Remote web URLs belong in `firecrawl_scrape`. Set `redactPII` to request redaction of personally identifiable information in the returned content. `zeroDataRetention` requires an eligible authenticated account; omit it for anonymous keyless use. Returns upload instructions for hosted phase one or parsed document content for the final call.

Create a recurring scrape, crawl, or search monitor that compares each check with its retained predecessor. The simple form accepts `page`/`pages` or `queries` plus a plain-language `goal`; the advanced `body` form controls targets, schedule, change-tracking formats, judging, retention, webhook, and notifications. In the simple form, a `goal` is required. If `queries` contains one or more non-empty values and is supplied with `page`/`pages`, `queries` create the search target and page targets are ignored. A monitor schedules future network checks and can send configured email or webhook notifications. Returns the created monitor.

List monitors for the authenticated account with optional pagination controls. Returns one page of monitor records and pagination metadata.

Retrieve one monitor by ID, including its configuration and current state. This does not run or modify the monitor.

Patch an existing monitor by ID. The body can change its name, active/paused status, schedule, targets, goal, judging, webhook, notifications, or retention; these changes affect future scheduled checks. Returns the updated monitor.

Permanently delete a monitor by ID and stop its future schedule. This operation cannot be undone and returns deletion status.

Queue an immediate check for a monitor outside its normal schedule. This starts network work for the monitor's configured targets and returns the queued check.

List historical checks for a monitor, optionally filtered by status and bounded by a result limit. Returns one page of check summaries and pagination metadata.

Retrieve one monitor check and its page-level results, optionally filtered by page status. Pages report `same`, `new`, `changed`, `removed`, or `error`; configured goal judging can add a meaningful-change decision. Markdown tracking returns a unified text diff, JSON tracking returns field paths with previous/current values and a current snapshot, and mixed tracking returns both. Returns one page of results plus a `next` URL when more pages exist.

Search paper metadata and abstracts with a natural-language query across the indexed corpus, which spans biomedical, life-science, and clinical literature (PubMed, bioRxiv, medRxiv) alongside arXiv and other scientific sources. Optional author, category, and date filters constrain results. Several distinct framings of the same question surface different papers than a single query does. Returns ranked papers with canonical IDs, titles, authors, and abstracts.

Retrieve canonical metadata for one paper ID, such as an arXiv, PMC, PMID, or DOI identifier. Returns the title, abstract, authors, categories, source IDs, and dates as markdown.

Find citation-graph candidates from one to ten `seed_ids`; the first ID is the primary seed and later IDs are anchors. `mode` defaults to `similar` (co-citation/bibliographic coupling); `citers` returns papers citing a seed and `references` papers cited by a seed. `intent` ranks candidates. Returns ranked candidates and the evaluated pool size.

Retrieve in-body passages from one paper that are relevant to a specific question. Full text is available only for indexed papers; `k` controls the number of passages. Returns matching passages or a notice when full text is unavailable.

Search indexed public GitHub issue, pull-request, and README content. Returns ranked matches with repository, URL, snippet, and full matched markdown when available.

For a developer question — code behaviour, a library or framework, an API contract, an error message, or a known bug — search an index built for coding agents. The index covers GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Set skills to "only" to limit the search to agent-skill files. Returns ranked results with an ID, source type, URL, title, and the matched passages in markdown.

Overview

What is Firecrawl MCP Server?

Firecrawl MCP is the official Model Context Protocol server from Firecrawl that lets AI agents search the web, scrape pages into clean Markdown or JSON, crawl and map sites, and interact with live pages from Claude, Cursor, VS Code and other clients.

You can use the hosted endpoint at https://mcp.firecrawl.dev/v2/mcp with no install, or run the open-source firecrawl-mcp package locally with npx or Docker. The local server also works with a self-hosted Firecrawl instance.

How to use Firecrawl MCP Server?

Prerequisites: a Firecrawl API key from https://www.firecrawl.dev/app/api-keys for the full tool set. Node.js is only needed for the local npx install.

Hosted, keyless: point your client at https://mcp.firecrawl.dev/v2/mcp. Without a key, firecrawl_scrape, firecrawl_search and firecrawl_parse work with rate limits; crawl, map and agent tools need a key.

Hosted, signed in: use https://mcp.firecrawl.dev/v2/mcp-oauth and complete the OAuth flow in your client. This URL is an MCP endpoint, not a page to open in a browser.

Hosted, API key: keep the URL https://mcp.firecrawl.dev/v2/mcp and send the header Authorization: Bearer <FIRECRAWL_API_KEY>. The README says never to put the key in the URL or in an agent chat.

Local:

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

Claude Code

# Hosted with OAuth sign-in
claude mcp add --transport http firecrawl https://mcp.firecrawl.dev/v2/mcp-oauth

# Local server
claude mcp add firecrawl -e FIRECRAWL_API_KEY=fc-YOUR_API_KEY -- npx -y firecrawl-mcp

Claude Desktop

Add to claude_desktop_config.json:

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

Cursor

Open Cursor Settings > Features > MCP Servers, click + Add new global MCP server, and enter:

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

VS Code

In .vscode/mcp.json, prompting for the key instead of storing it:

{
  "inputs": [
    { "type": "promptString", "id": "apiKey", "description": "Firecrawl API Key", "password": true }
  ],
  "servers": {
    "firecrawl": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": { "FIRECRAWL_API_KEY": "${input:apiKey}" }
    }
  }
}

Windsurf

Add the same mcpServers block (server name mcp-server-firecrawl) to ./codeium/windsurf/model_config.json.

For self-hosting, set FIRECRAWL_API_URL to your instance. Set HTTP_STREAMABLE_SERVER=true to serve the local server over Streamable HTTP at http://localhost:3000/mcp. A Docker image is published as ghcr.io/firecrawl/firecrawl-mcp-server.

Key features of Firecrawl MCP Server

  • Web search that can return full page content, plus a search index for coding agents covering GitHub issues, merged pull requests, READMEs and docs
  • Scrape any URL to Markdown, HTML, links, screenshots or JSON that matches a schema you supply
  • Crawl and map whole sites with path filters, depth and page limits
  • Live browser interaction: click, type and navigate before reading a page
  • Asynchronous research agent, document parsing (PDF, Word, spreadsheets), and recurring page monitors with diffs
  • Credit usage checks, automatic retries and rate-limit handling
  • Hosted (keyless, OAuth or API key) or local via npx/Docker, including self-hosted Firecrawl

Firecrawl MCP Server tools

With the full profile and default settings, the server lists 27 tools; the keyless hosted endpoint exposes only firecrawl_scrape, firecrawl_search and firecrawl_parse.

  • Fetch and parse: firecrawl_scrape reads one known URL; firecrawl_parse converts a document such as a PDF. Structured extraction is done with firecrawl_scrape and formats: ["json"] (firecrawl_extract is deprecated).
  • Discover: firecrawl_search starts from a query; firecrawl_map lists a site's URLs without fetching them.
  • Crawl: firecrawl_crawl collects many pages; firecrawl_check_crawl_status reads a job's progress.
  • Interact: firecrawl_interact opens a live browser session; firecrawl_interact_stop closes it.
  • Research: firecrawl_agent and firecrawl_agent_status run multi-source research jobs; the firecrawl_research_* tools search papers in PubMed, bioRxiv, medRxiv and arXiv.
  • Monitor: firecrawl_monitor_* tools schedule repeat checks and report changes.
  • Account and feedback: firecrawl_credit_usage, firecrawl_search_feedback and firecrawl_feedback.

Use cases of Firecrawl MCP Server

  • Pulling current docs into a coding session: "Scrape the Next.js caching docs and summarize what changed."
  • Research with sources: "Search for recent benchmarks of vector databases and give me the top five with links."
  • Structured extraction: "Get the plan names and prices from this pricing page as JSON."
  • Site audits: "Map example.com and list every page under /blog."
  • Pages behind interactions: "Open this page, click Load more, then read the results."
  • Change tracking: set a monitor on a competitor's pricing page and get alerted when it changes.

Firecrawl MCP Server vs alternatives

Exa MCP Server and Tavily MCP focus on search for agents and return content from their own indexes, while Firecrawl MCP centers on scraping, crawling and interacting with pages you choose. Apify Actors MCP gives access to prebuilt scrapers for specific sites. For simple browser automation without a scraping API, Playwright MCP runs a local browser.

Troubleshooting Firecrawl MCP Server

  • Only three tools appear: you are on the keyless hosted endpoint. Sign in through /v2/mcp-oauth or add an API key to unlock crawl, map, agent and the rest.
  • Rate limit errors: the server surfaces Firecrawl rate-limit errors to the client. Signing in or using an API key gives higher limits; for crawls, also lower the limit.
  • Windows issues with the Cursor command: try cmd /c "set FIRECRAWL_API_KEY=your-api-key && npx -y firecrawl-mcp".
  • Opening the OAuth URL in a browser does nothing useful: it is a server URL; add it in your MCP client and use the client's account-connection flow.
  • Too many tools for your client's tool limit: set FIRECRAWL_NO_SEARCH_FEEDBACK=1 and/or FIRECRAWL_NO_ENDPOINT_FEEDBACK=1, or use the search-only endpoint https://mcp.firecrawl.dev/v2/mcp-search.

Frequently asked questions

1

Is Firecrawl MCP official?

Yes. The server is maintained by Firecrawl in the `firecrawl/firecrawl-mcp-server` repository (formerly `mendableai`), with credit to the original community implementation by @vrknetha.

2

Is the Firecrawl MCP server free?

The code is MIT-licensed, and the hosted keyless tier allows rate-limited scrape, search and parse without an account. Other tools use your Firecrawl plan's credits; check firecrawl.dev for current pricing.

3

Which API key do I need?

A Firecrawl API key (it starts with `fc-`) from `https://www.firecrawl.dev/app/api-keys`, set as `FIRECRAWL_API_KEY` locally or sent as a Bearer token to the hosted server. OAuth sign-in is an alternative for hosted use.

4

Does Firecrawl MCP work with Claude Code, Cursor and VS Code?

Yes. The README documents Cursor, VS Code, Windsurf and Claude Desktop, and Claude Code can add either the hosted URL or the local npx command.

5

Should I use the remote or local server?

The hosted server needs no install and supports OAuth. Run locally when you want to point at a self-hosted Firecrawl via `FIRECRAWL_API_URL`, parse files from your own disk, or control the runtime with Docker.

6

Is it safe to let an agent use firecrawl_interact?

`firecrawl_interact` acts on live sites, so actions such as submitting forms can have real side effects. Review those tool calls before approving them.

7

Can I run Firecrawl MCP without Firecrawl's cloud?

Yes. Set `FIRECRAWL_API_URL` to your self-hosted Firecrawl instance; an API key is then only needed if your instance requires one.

Comments

More Browser Automation MCP servers