Firecrawl MCP 是官方的吗?
是的。该服务器由 Firecrawl 在 `firecrawl/firecrawl-mcp-server` 仓库(原 `mendableai`)中维护,并感谢 @vrknetha 最初的社区实现。
@mendableai
基本信息
🔥 官方 Firecrawl MCP 服务器 - 为 Cursor、Claude 及其他任何 LLM 客户端添加强大的网页抓取和搜索能力。
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"firecrawl-mcp": {
"command": "npx",
"args": [
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY"
}
}
}
}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.
Firecrawl MCP 是 Firecrawl 官方推出的 Model Context Protocol 服务器,让 AI 智能体可以在 Claude、Cursor、VS Code 等客户端中搜索网页、把页面抓取为干净的 Markdown 或 JSON、爬取和映射站点,并与实时页面交互。
你可以直接使用托管端点 https://mcp.firecrawl.dev/v2/mcp,无需安装;也可以通过 npx 或 Docker 在本地运行开源的 firecrawl-mcp 包。本地服务器同样支持自托管的 Firecrawl 实例。
前提条件: 要使用完整工具集,需要从 https://www.firecrawl.dev/app/api-keys 获取 Firecrawl API 密钥。只有本地 npx 安装才需要 Node.js。
托管、免密钥: 将客户端指向 https://mcp.firecrawl.dev/v2/mcp。没有密钥时,firecrawl_scrape、firecrawl_search 和 firecrawl_parse 可在限流条件下使用;爬取、映射和 agent 类工具需要密钥。
托管、登录: 使用 https://mcp.firecrawl.dev/v2/mcp-oauth,并在客户端中完成 OAuth 流程。这个 URL 是 MCP 端点,不是要在浏览器中打开的网页。
托管、API 密钥: URL 保持为 https://mcp.firecrawl.dev/v2/mcp,并发送请求头 Authorization: Bearer <FIRECRAWL_API_KEY>。README 明确提醒:不要把密钥放进 URL,也不要在与智能体的对话中粘贴密钥。
本地:
env FIRECRAWL_API_KEY=fc-YOUR_API_KEY npx -y firecrawl-mcp
# 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_config.json 中添加:
{
"mcpServers": {
"mcp-server-firecrawl": {
"command": "npx",
"args": ["-y", "firecrawl-mcp"],
"env": {
"FIRECRAWL_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
打开 Cursor Settings > Features > MCP Servers,点击 + Add new global MCP server,然后输入:
{
"mcpServers": {
"firecrawl-mcp": {
"command": "npx",
"args": ["-y", "firecrawl-mcp"],
"env": {
"FIRECRAWL_API_KEY": "YOUR-API-KEY"
}
}
}
}
在 .vscode/mcp.json 中配置,运行时提示输入密钥而不是明文保存:
{
"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}" }
}
}
}
将同样的 mcpServers 配置块(服务器名为 mcp-server-firecrawl)添加到 ./codeium/windsurf/model_config.json。
如需自托管,把 FIRECRAWL_API_URL 设置为你的实例地址。设置 HTTP_STREAMABLE_SERVER=true 可让本地服务器通过 Streamable HTTP 在 http://localhost:3000/mcp 提供服务。Docker 镜像发布为 ghcr.io/firecrawl/firecrawl-mcp-server。
在完整配置和默认设置下,服务器会列出 27 个工具;免密钥的托管端点只提供 firecrawl_scrape、firecrawl_search 和 firecrawl_parse。
firecrawl_scrape 读取一个已知 URL;firecrawl_parse 转换 PDF 等文档。结构化提取通过 firecrawl_scrape 加 formats: ["json"] 完成(firecrawl_extract 已弃用)。firecrawl_search 从查询词出发;firecrawl_map 列出站点 URL 但不抓取内容。firecrawl_crawl 收集多个页面;firecrawl_check_crawl_status 查看任务进度。firecrawl_interact 打开实时浏览器会话;firecrawl_interact_stop 关闭会话。firecrawl_agent 和 firecrawl_agent_status 运行多来源研究任务;firecrawl_research_* 工具可检索 PubMed、bioRxiv、medRxiv 和 arXiv 中的论文。firecrawl_monitor_* 工具安排定期检查并报告变化。firecrawl_credit_usage、firecrawl_search_feedback 和 firecrawl_feedback。Exa MCP Server 和 Tavily MCP 专注于面向智能体的搜索,从自有索引返回内容;Firecrawl MCP 则以抓取、爬取和与你指定的页面交互为核心。Apify Actors MCP 提供针对特定网站的现成爬虫。如果只需要简单的浏览器自动化而不依赖抓取 API,Playwright MCP 会在本地运行浏览器。
/v2/mcp-oauth 登录或添加 API 密钥,即可解锁 crawl、map、agent 等其余工具。limit。cmd /c "set FIRECRAWL_API_KEY=your-api-key && npx -y firecrawl-mcp"。FIRECRAWL_NO_SEARCH_FEEDBACK=1 和/或 FIRECRAWL_NO_ENDPOINT_FEEDBACK=1,或使用仅搜索端点 https://mcp.firecrawl.dev/v2/mcp-search。是的。该服务器由 Firecrawl 在 `firecrawl/firecrawl-mcp-server` 仓库(原 `mendableai`)中维护,并感谢 @vrknetha 最初的社区实现。
代码采用 MIT 许可证,托管的免密钥档位无需账号即可在限流条件下使用 scrape、search 和 parse。其他工具会消耗你 Firecrawl 套餐的额度;当前价格请查看 firecrawl.dev。
需要从 `https://www.firecrawl.dev/app/api-keys` 获取的 Firecrawl API 密钥(以 `fc-` 开头)。本地使用时设置为 `FIRECRAWL_API_KEY`,托管使用时作为 Bearer token 发送。托管模式也可以改用 OAuth 登录。
支持。README 提供了 Cursor、VS Code、Windsurf 和 Claude Desktop 的配置,Claude Code 可以添加托管 URL 或本地 npx 命令。
托管服务器无需安装并支持 OAuth。如果你想通过 `FIRECRAWL_API_URL` 对接自托管 Firecrawl、解析本地磁盘上的文件,或用 Docker 控制运行环境,就选择本地运行。
`firecrawl_interact` 会作用于真实网站,提交表单等操作可能产生实际影响。批准这类工具调用前请先检查。
可以。将 `FIRECRAWL_API_URL` 设置为自托管的 Firecrawl 实例;只有当你的实例要求认证时才需要 API 密钥。
Official Chrome DevTools MCP server from Google that lets coding agents control, debug and profile a live Chrome browser.

Parse allows your agent to access thousands of APIs instantly. You can use Parse to build an API for any action on any website and edit any previously existing API in our catalogue.
🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
Capture screenshots of webpages as images or PDFs with Screenshot Scout.
评论