Firecrawl MCP Server

Firecrawl file parsing

firecrawl_parse

Read-only

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.

Input Schema

TableJSON 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

TableJSON 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}`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

removedOutput schema / description

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

First observedSep 29, 2026

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.

All Firecrawl MCP Server tools Inspect

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.