Firecrawl MCP Server

Name: Firecrawl MCP Server
Author: firecrawl

Server Details

Official Firecrawl MCP server: search, scrape, and interact with the web, plus paper search.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 21 days
Last Tested: 2026-10-19 09:18
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: firecrawl/firecrawl-mcp-server
GitHub Stars: 7,617
Server Listing: Firecrawl MCP Server

TDQS

A4.2/5.0

Scored 2026-10-17 22:10 across 3 tools

Disambiguation4/5

The three tools have mostly distinct primary targets: parse handles local documents, scrape extracts one URL, and search queries the web. However, scrape and search both mention Alexandria/provider capabilities and cross-reference several absent tools, which adds some boundary confusion.

Naming Consistency5/5

All tool names follow the same predictable firecrawl_verb pattern in snake_case. There is no mixing of naming conventions.

Tool Count3/5

Three tools is compact and each is broad, but for a server branded as Firecrawl it feels under-scoped because the descriptions repeatedly reference separate map, crawl, find_tools, gov_search, and research tools. The count is not excessive, but it is borderline for the apparent service surface.

Completeness2/5

Core parse, scrape, and search operations are present, but major referenced capabilities such as firecrawl_map, firecrawl_crawl, firecrawl_find_tools, firecrawl_gov_search, and firecrawl_research_* are missing. This creates significant gaps that will cause agent failures when following the tool descriptions.

Available Tools

3 tools

firecrawl_parseFirecrawl file parsingA

Read-only

Inspect

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. Authenticated final responses can include a data.metadata.scrapeId for optional parse feedback.

ParametersJSON Schema

Name	Required	Description
`proxy`	No
`maxAge`	No	Ignored: parse never reuses or stores indexed content.
`formats`	No
`parsers`	No
`filePath`	No	Phase 1 only: path to the local file on the caller/harness machine. Hosted MCP will not read or stat this path; it is used only to produce upload instructions.
`redactPII`	No
`uploadRef`	No	Phase 2 only: short-lived upload reference returned by phase 1 after the local PUT upload completes.
`pdfOptions`	No
`contentType`	No	Phase 1 MIME type override. If omitted, the server infers it from the file extension without reading the file.
`excludeTags`	No
`includeTags`	No
`jsonOptions`	No
`queryOptions`	No
`storeInCache`	No
`onlyMainContent`	No
`declaredSizeBytes`	No	Optional phase 1 size declaration. Hosted MCP does not stat the file; provide this only if the caller already knows it.
`zeroDataRetention`	No
`removeBase64Images`	No
`skipTlsVerification`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`raw`	No	Response body when it was not JSON.
`data`	No	Parsed document content; can include `data.metadata.scrapeId` for parse feedback.
`mode`	No	Which phase of the hosted flow produced this response.
`error`	No	Error message or error object when the call did not succeed.
`notes`	No	Hosted phase one: constraints on completing the upload flow.
`upload`	No	Hosted phase one: how to upload the local file.
`message`	No	Guidance for the next call.
`success`	No	Whether the API call succeeded.
`warning`	No	Non-fatal warning about the result.
`agent_hints`	No	Optional response guidance from the Firecrawl API.
`nextToolCall`	No	Hosted phase one: the second `firecrawl_parse` call to make once the upload succeeds, as `{name, arguments}`.

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only cover the safety profile (readOnly, non-destructive, closed-world); the description adds substantial behavior beyond them — the two-call hosted upload handshake, PII redaction semantics, the authentication prerequisite for zeroDataRetention, and the optional scrapeId feedback hook. No contradiction with the read-only annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and supported inputs, then the two-phase flow, then behavioral notes. Every sentence carries information, though the paragraph is dense and slightly long given how many schema-level details remain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be detailed, and annotations cover safety. The description handles the two-phase upload model and auth requirements well, but with 19 parameters and low schema coverage it still leaves many optional parameters unexplained, which an agent working from this tool alone would need.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 26%, so the description must carry the load. It explains the critical flow parameters (filePath phase 1, uploadRef phase 2, pdfOptions.maxPages, redactPII, zeroDataRetention, formats) but leaves roughly a dozen parameters (proxy, parsers, excludeTags/includeTags, jsonOptions, queryOptions, storeInCache, onlyMainContent, declaredSizeBytes, removeBase64Images, skipTlsVerification) undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (parse) and resource (one supported document), enumerates the output formats (markdown, HTML, links, summary, answers, JSON), and names supported input types. It explicitly carves out the sibling boundary by saying remote web URLs belong in firecrawl_scrape, so the agent can distinguish it from firecrawl_scrape without reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: local MCP reads filePath, hosted MCP requires a two-phase filePath-then-uploadRef flow with an explicit 'do not send both together' warning, and remote URLs go to firecrawl_scrape. It also conditions zeroDataRetention on an eligible authenticated account and tells the agent to omit it for keyless use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

firecrawl_scrapeFirecrawl scrapeA

Read-only

Inspect

Scrape one URL and return its content: markdown by default, or HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema. Use it when the request identifies a page and needs its content or defined fields. Use firecrawl_search when additional web sources are needed; on an authenticated session, firecrawl_map lists a site's URLs and firecrawl_crawl collects a set of pages.

Firecrawl may serve recently indexed content; set maxAge: 0 for a live fetch or a smaller maxAge to bound staleness. A successful response does not by itself confirm the page is still current. A named browser profile loads saved session data without saving changes to it. Authenticated responses can include a metadata.scrapeId for optional scrape feedback.

On an authenticated session with Alexandria access, firecrawl_search and firecrawl_find_tools can discover providers for the same fields across several pages; a matching provider returns typed records in one call. Keyless sessions have no provider matches.

Alexandria mode, on an authenticated session with Alexandria access: alexandria selects catalogued capability execution and is mutually exclusive with url.

ParametersJSON Schema

Name	Required	Description
`url`	No
`proxy`	No
`maxAge`	No
`mobile`	No
`formats`	No
`parsers`	No
`profile`	No	Loads a saved browser profile without saving changes to it.
`timeout`	No	Execution timeout in milliseconds.
`waitFor`	No
`location`	No
`lockdown`	No
`objective`	Yes	The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information.
`redactPII`	No
`requestId`	No	Idempotency key bound to one Alexandria execution payload. Generated when omitted and returned with the result.
`alexandria`	No	Catalogued Alexandria capability invocation, mutually exclusive with url. One {provider, capability, options} object or an array of 1-10, with contracts available through firecrawl_search or firecrawl_find_tools. Each call may include version to pin a published workflow; omitting it uses latest. Only requestId and timeout are supported alongside alexandria. The selected contract marks required inputs and any requiresOneOf groups (at least one member per group); it may include example.request/example.response and response.key (which may differ from records). Where pagination is declared, its fields govern paging with the same filters; catalogue next is separate from provider pagination. Returns per-capability results in data.alexandria with data, records, or an error with a code; individual capabilities can fail even when the outer response succeeds. Requires an API key on a team with Alexandria enabled. Some providers require accepted terms; blocked requests return the applicable requirements.
`pdfOptions`	No
`toolDetail`	No	URL mode only: domain discovery detail, summary by default; compact returns provider/capability/description, full includes contracts. Ignored with alexandria.
`domainTools`	No	URL mode only: include domain-matched Alexandria tools for the page in tools on the returned document. Ignored with alexandria.
`excludeTags`	No
`includeTags`	No
`jsonOptions`	No
`queryOptions`	No
`storeInCache`	No
`onlyMainContent`	No
`screenshotOptions`	No
`zeroDataRetention`	No
`removeBase64Images`	No
`skipTlsVerification`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`data`	No	Alexandria mode: per-capability results in `data.alexandria`, each with `data`, `records`, or an `error`.
`html`	No	Processed HTML of the page.
`json`	No	Structured data matching the requested JSON schema or prompt.
`menu`	No	Menu data extracted from the page.
`audio`	No	Audio extracted from the page.
`error`	No	Error message or error object when the call did not succeed.
`links`	No	Links found on the page.
`pages`	No	Physical PDF pages, when `parsers[].pages` is set.
`tools`	No	Domain-matched Alexandria tools for the page, when `domainTools` is set.
`video`	No	Video extracted from the page.
`answer`	No	Targeted answer to the question that was asked of the page.
`blocks`	No	Typed PDF layout blocks, when `parsers[].blocks` is set.
`images`	No	Images found on the page.
`actions`	No	Results of the browser actions that ran during the scrape.
`message`	No	Guidance that accompanies the result.
`product`	No	Product data extracted from the page.
`rawHtml`	No	Unprocessed HTML of the page.
`receipt`	No	Billing receipt for the execution.
`success`	No	Whether the API call succeeded.
`summary`	No	Summary of the page content.
`warning`	No	Non-fatal warning about the result.
`branding`	No	Branding data extracted from the page.
`delivery`	No	`retained` when the full result stayed server-side instead of being inlined.
`markdown`	No	Page content as markdown.
`metadata`	No	Page metadata; authenticated responses can include `metadata.scrapeId` for scrape feedback.
`nextTool`	No	A follow-up tool call (`{name, arguments}`) that continues or inspects this result.
`requestId`	No	Identifier of this Alexandria execution.
`scrape_id`	No	Identifier of the underlying scrape.
`attributes`	No	Values collected by the requested attribute selectors.
`highlights`	No	Highlighted passages from the page.
`screenshot`	No	Screenshot of the page.
`agent_hints`	No	Optional response guidance from the Firecrawl API.
`creditsCost`	No	Credits this call consumed.
`workspaceId`	No	Workspace holding a retained result, for inspection through virtual Bash.
`feedbackTool`	No	Pointer to the feedback tool for reporting how this result served the task.
`responseBytes`	No	Size of the full result in bytes.
`changeTracking`	No	Change-tracking comparison against the previous scrape.
`idleTtlSeconds`	No	Seconds a retained workspace stays available while idle.
`estimatedTokens`	No	Estimated token cost of the full result.
`inlineTokenBudget`	No	Token budget above which a result is retained rather than inlined.
`tokenEstimateMethod`	No	How `estimatedTokens` was derived.

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnly/openWorld/non-destructive, so the description adds real behavioral context: recently indexed content may be served, maxAge=0 forces a live fetch, success does not prove the page is current, profiles load but never persist changes, authenticated responses carry metadata.scrapeId, and Alexandria requires an API team key with per-capability failures inside a successful envelope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and output options before any conditional guidance, and every paragraph does distinct work (routing, freshness, profiles, Alexandria). It runs long and the final Alexandria paragraph is dense, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-shape explanation is rightly omitted, and the description is careful to note the alexandria return path and failure mode. For a 28-parameter tool with one required field, the description orients the agent to the main modes, though the long tail of tuning parameters remains undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 28 parameters at 25% schema description coverage, the description must carry weight, and it does explain maxAge, the formats family, profile persistence, URL-vs-Alexandria exclusivity, and the per-capability option/version semantics. However, most parameters (proxy, parsers, lockdown, waitFor, location, redactPII, storeInCache, zeroDataRetention, include/excludeTags, etc.) get no mention anywhere, so the compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Scrape one URL and return its content') and enumerates the concrete output shapes (markdown default, HTML, links, screenshots, branding, query answer, schema-bound JSON). It also distinguishes itself from named siblings (search, map, crawl) and from the Alexandria invocation mode, so an agent can pick it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule ('Use it when the request identifies a page and needs its content or defined fields') plus conditional alternatives: search when more web sources are needed, map for URL listing, crawl for page sets, and the alexandria/url mutual exclusion. The only unaddressed sibling is firecrawl_parse, a minor omission against otherwise complete routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

firecrawl_searchFirecrawl web searchA

Read-only

Inspect

Search web, news, or image sources and return ranked results with query-relevant highlights. Each web result is a title, URL, and description; use firecrawl_scrape on a result URL when the excerpt is not enough.

Authenticated search also returns matching Alexandria data providers in data.tools (companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more). Prefer a provider over scraping pages when the task needs the same fields across several entities, exact figures or timestamps, provenance, or many records; use web results when they already answer the question. Authenticated searches always add alexandria to the sources, so sources: ["web"] also returns providers; domainTools: false turns off website-matched tools only.

On an authenticated session, tool matches describe available capabilities; firecrawl_find_tools returns their contracts and firecrawl_scrape with an alexandria body executes a selected capability. Keyless sessions get no Alexandria matches in data.tools.

For a programming question, add categories: ["developer"]; its hits return in data.web with category: "developer". For a legal or regulatory question, categories: ["gov"] returns hits in data.web with category: "gov" and cannot be combined with other categories; authenticated sessions also have firecrawl_gov_search as the dedicated tool. Verify gov results' issuer, jurisdiction, status, and version before citing current law. categories: ["research"] restricts web results to research-affiliated websites; the firecrawl_research_* tools are a separate surface over paper abstracts and full text (PubMed, bioRxiv, medRxiv, arXiv). Query operators, domain filters, categories, toolDetail and scrapeOptions are described on their parameters. Returns source-type result groups and usage metadata. Authenticated responses can include an id for optional search feedback.

ParametersJSON Schema

Name	Required	Description
`tbs`	No
`limit`	No
`query`	Yes	Query for web and semantic tool discovery. Operators include quoted phrases, `-term`, `site:host`, `inurl:term`, `intitle:term`, and `related:host`; the set is non-exhaustive. Catalogue browsing is available through firecrawl_find_tools.
`filter`	No
`sources`	No	Search sources; authenticated sessions default to web + alexandria, keyless sessions to web only. Authenticated searches always add alexandria to the sources, so sources: ["web"] also returns providers; domainTools: false turns off website-matched tools only. enterprise zdr or anon searches do not add it. Use ["alexandria"] alone for provider discovery without web results.
`location`	No
`objective`	Yes	The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information.
`categories`	No	Limit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation; `gov` searches the Government Index of US federal, state, and local legal and regulatory sources, the index behind firecrawl_gov_search, and cannot be combined with other categories; gov hits can include historical versions, bill text, agency guidance, and third-party reproductions, so verify the issuer, jurisdiction, enacted/effective status, and version before citing current governing law, clarify a missing jurisdiction or ambiguous as-of date, and use general search for non-US questions or missing coverage (no hits does not establish that no applicable law exists). `developer` and `gov` return hits in `data.web` with `category` set to their name; the other categories also filter `data.web`.
`enterprise`	No
`highlights`	No	Return query-relevant page excerpts for web and news results when available (default). Highlights appear in web `description` and news `snippet`; otherwise, original snippets are returned. Set to false to keep the original search snippets.
`toolDetail`	No	Compact by default. Compact returns only provider, capability and description; full includes contracts. Inspect selected compact tools with firecrawl_find_tools providers and capabilities.
`domainTools`	No	Include domain-matched tools for result URLs. Defaults to true when Alexandria is combined with web, news or images; semantic-only search leaves domain matching off.
`scrapeOptions`	No	Attach page content for web results in the same call. These fetches ignore maxAge, so use firecrawl_scrape when you need a live fetch. scrapeOptions fetches web pages, never Alexandria provider tools.
`excludeDomains`	No	Hostnames to leave out of results. Mutually exclusive with includeDomains.
`includeDomains`	No	Hostnames to restrict results to. Mutually exclusive with excludeDomains.

Output Schema

ParametersJSON Schema

Name	Required	Description
`id`	No	Search identifier, for optional `firecrawl_search_feedback`.
`data`	No	Ranked results grouped by source, such as `web`, `news`, `images`, and `alexandria`.
`error`	No	Error message or error object when the call did not succeed.
`tools`	No	Domain-matched Alexandria tools for the results.
`success`	No	Whether the API call succeeded.
`warning`	No	Non-fatal warning about the result.
`nextTool`	No	A follow-up tool call that continues this search.
`agent_hints`	No	Optional response guidance from the Firecrawl API.
`creditsUsed`	No	Credits this search consumed.
`feedbackTool`	No	Pointer to the feedback tool for this search.

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorld=true, so safety is covered. The description then adds genuinely non-obvious behavior: how keyless vs authenticated sessions differ in sources, that authenticated searches always inject alexandria, that scrapeOptions fetches ignore maxAge, and that responses may carry a feedback id. Docked one because it never states rate limits or the concrete shape of data.tools beyond a prose list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then routing, then per-category rules in a logical order; almost every sentence carries actionable information. It loses a point for redundancy with the schema – the alexandria/domainTools and gov-verification caveats are restated nearly verbatim from the sources and categories parameter descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter tool with nested objects and an output schema, this covers the decision surface: what sources exist, session-dependent defaults, provider vs web tradeoffs, category-specific caveats, and the fact that usage metadata and source-type groups are returned. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is a moderate 67%, and the description compensates well for the undocumented or thinly documented ones: categories semantics (gov cannot be combined, verify issuer/jurisdiction/status), sources defaulting and the alexandria injection rule, toolDetail levels, domainTools default behavior, and query operator syntax. It leaves tbs, filter, limit, location and enterprise entirely unexplained, so it is not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Search web, news, or image sources') plus the return shape (ranked results with highlights). It explicitly distinguishes itself from firecrawl_scrape by pointing at it for full-page content, so an agent can tell it apart from its siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules across several axes: prefer a provider over scraping when the task needs consistent fields across entities or exact figures; use web results when they already answer the question; add categories:['developer'] or ['gov'] for those domains; and use firecrawl_gov_search / firecrawl_research_* for their dedicated surfaces. Names alternatives and the conditions that select them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesOct 17, 2026
- Changedfirecrawl_scrape1 field changed
  - addedInput schema / required
```
Added value: +[
+  "objective"
+]
```
- Changedfirecrawl_search1 field changed
  - changedInput schema / required
```
Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "objective"
+]
```

1 tool updateOct 17, 2026

Changedfirecrawl_search1 field changed

changedInput schema / properties / sources / description

Previous value: -"Search sources; authenticated sessions default to web + alexandria, keyless sessions to web only. A search with sources: [\"web\"] omits semantic provider discovery; domainTools: true can still return website-matched tools. Web-only results use domainTools: false. Use [\"alexandria\"] alone for provider discovery without web results."New value: +"Search sources; authenticated sessions default to web + alexandria, keyless sessions to web only. Authenticated searches always add alexandria to the sources, so sources: [\"web\"] also returns providers; domainTools: false turns off website-matched tools only. enterprise zdr or anon searches do not add it. Use [\"alexandria\"] alone for provider discovery without web results."

2 tool updatesOct 14, 2026
- Changedfirecrawl_scrape1 field changed
  - removedInput schema / required
```
Removed value: -[
-  "objective"
-]
```
- Changedfirecrawl_search1 field changed
  - changedInput schema / required
```
Previous value: -[
-  "query",
-  "objective"
-]New value: +[
+  "query"
+]
```

3 tool updatesOct 13, 2026

Changedfirecrawl_parse1 field changed

removedOutput schema / description

Removed value: -"Parsed document content, or the upload instructions for the hosted two-call flow."

Changedfirecrawl_scrape1 field changed

removedOutput schema / description

Removed value: -"A scraped document, or the Alexandria execution envelope when `alexandria` was passed."

Changedfirecrawl_search2 fields changed

removedInput schema / properties / clientModel

Removed value: -{
-  "description": "Optional model identifier, if known.",
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}

removedOutput schema / description

Removed value: -"Ranked search results grouped by source."

2 tool updatesOct 12, 2026

Changedfirecrawl_scrape1 field changed
- addedInput schema / required
```
Added value: +[
+  "objective"
+]
```

Changedfirecrawl_search2 fields changed

changedInput schema / properties / objective / description

Previous value: -"Optional broader goal for this search, if known. Avoid sensitive information."New value: +"The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information."

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "objective"
+]

1 tool updateOct 12, 2026

Changedfirecrawl_scrape1 field changed

addedInput schema / properties / objective

Added value: +{
+  "description": "The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information.",
+  "maxLength": 1000,
+  "minLength": 1,
+  "type": "string"
+}

2 tool updatesOct 9, 2026

Changedfirecrawl_scrape1 field changed

changedInput schema / properties / formats / items / enum

Previous value: -[
-  "markdown",
-  "html",
-  "rawHtml",
-  "screenshot",
-  "links",
-  "summary",
-  "changeTracking",
-  "branding",
-  "json",
-  "query",
-  "audio"
-]New value: +[
+  "markdown",
+  "html",
+  "rawHtml",
+  "screenshot",
+  "links",
+  "images",
+  "summary",
+  "changeTracking",
+  "branding",
+  "json",
+  "query",
+  "audio"
+]

Changedfirecrawl_search1 field changed

changedInput schema / properties / scrapeOptions / properties / formats / items / enum

Previous value: -[
-  "markdown",
-  "html",
-  "rawHtml",
-  "screenshot",
-  "links",
-  "summary",
-  "changeTracking",
-  "branding",
-  "json",
-  "query",
-  "audio"
-]New value: +[
+  "markdown",
+  "html",
+  "rawHtml",
+  "screenshot",
+  "links",
+  "images",
+  "summary",
+  "changeTracking",
+  "branding",
+  "json",
+  "query",
+  "audio"
+]

1 tool updateOct 8, 2026

Changedfirecrawl_search1 field changed

changedInput schema / properties / categories / description

Previous value: -"Limit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation; `gov` searches the Government Index of US federal, state, and local legal and regulatory sources, the index behind firecrawl_gov_search, and cannot be combined with other categories. `developer` and `gov` return hits in `data.web` with `category` set to their name; the other categories also filter `data.web`."New value: +"Limit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation; `gov` searches the Government Index of US federal, state, and local legal and regulatory sources, the index behind firecrawl_gov_search, and cannot be combined with other categories; gov hits can include historical versions, bill text, agency guidance, and third-party reproductions, so verify the issuer, jurisdiction, enacted/effective status, and version before citing current governing law, clarify a missing jurisdiction or ambiguous as-of date, and use general search for non-US questions or missing coverage (no hits does not establish that no applicable law exists). `developer` and `gov` return hits in `data.web` with `category` set to their name; the other categories also filter `data.web`."

1 tool updateOct 6, 2026

Changedfirecrawl_search2 fields changed

changedInput schema / properties / categories / description

Previous value: -"Limit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation. `developer` returns hits in `data.web` with `category: \"developer\"`; the other categories also filter `data.web`."New value: +"Limit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation; `gov` searches the Government Index of US federal, state, and local legal and regulatory sources, the index behind firecrawl_gov_search, and cannot be combined with other categories. `developer` and `gov` return hits in `data.web` with `category` set to their name; the other categories also filter `data.web`."

changedInput schema / properties / categories / items / enum

Previous value: -[
-  "research",
-  "pdf",
-  "developer"
-]New value: +[
+  "research",
+  "pdf",
+  "developer",
+  "gov"
+]

Related MCP Connectors

mcp A
ai.llmse
Public MCP server for the LLM Search Engine
Search RAG Systems Developer Tools
102
agentwork-mcp A
io.github.ferm-ai
Official MCP server for Agentwork — delegate tasks to AI agents with human-in-the-loop
Agent Orchestration Autonomous Agents App Automation
2
IndicesOAuth
io.indices
Official Indices MCP server. Turn any website into a reliable API.
Web Scraping Browser Automation
1
Subfeed MCP
app.subfeed.mcp
Official MCP server for subfeed.app — the cloud for agents. 15+ tools for AI agents to register, build, and deploy other agents. Zero human required. Start here: subfeed.app/skill.md
Agent Orchestration Cloud Platforms Autonomous Agents
2

Related MCP Servers

mcp-firecrawl
Web Scraping Browser Automation Search
pipeworx-io
A
license
Not graded
quality
B
maintenance
Web scraping and search MCP server that wraps Firecrawl API for URL discovery and web search with optional content retrieval.
Updated 23 days ago (2026-09-26 12:27 UTC)
14 npm
1
MIT
WebSearch
Web Scraping Browser Automation Search
josemartinrodriguezmortaloni
F
license
C
quality
C
maintenance
Built as a Model Context Protocol (MCP) server that provides advanced web search, content extraction, web crawling, and scraping capabilities using the Firecrawl API.
Updated 4 months ago (2026-06-17 03:44 UTC)
4
1
-
web-fetch-mcp
Web Scraping Search
bpzx
A
license
A
quality
C
maintenance
MCP server for web page fetching (converting to Markdown/text with automatic fallback between Tavily and Firecrawl) and web search via Tavily.
Updated 4 months ago (2026-06-21 07:24 UTC)
2
MIT
webcrawl-mcp
Web Scraping Search
andyliszewski
A
license
B
quality
B
maintenance
Lightweight MCP server for web scraping, search, and crawling. Uses local trafilatura/DuckDuckGo by default with optional Firecrawl fallback for transport-blocked pages.
Updated a month ago (2026-09-09 20:39 UTC)
4
16
MIT

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources