Firecrawl MCP tools

Choose a Firecrawl MCP tool and understand its availability and operating behavior.

Firecrawl MCP exposes tools for finding, extracting, interacting with, and monitoring web content. Your MCP client receives the exact input schema for every available tool when it connects.

Tool availability

Connection mode	Available tools
Hosted OAuth	Full tool surface, subject to plan and team policy
Hosted API key	Full tool surface, subject to plan and team policy
Hosted keyless	firecrawl_search, firecrawl_scrape, and firecrawl_parse
Local with the Firecrawl cloud API	API-backed tools; direct local-file Parse is unavailable
Local with a self-hosted Firecrawl API	Tools supported by the services enabled in that deployment

Start with Agent MCP or Human MCP to choose OAuth, API-key, or keyless access. Some optional tools can be disabled by environment or team policy.

Choose a tool

Job	Tool	Use it when
Read one page	firecrawl_scrape	You know the URL and need page content or structured fields.
Discover site URLs	firecrawl_map	You need to find pages before deciding what to extract.
Search the web	firecrawl_search	You have a query rather than a known URL.
Parse a file	firecrawl_parse	You need content from a PDF, document, spreadsheet, or HTML file.
Extract many pages	firecrawl_crawl and firecrawl_check_crawl_status	You need to traverse a site or section. The crawl tool polls the job to a terminal state before returning.
Run autonomous research	firecrawl_agent and firecrawl_agent_status	The task spans multiple sources and the exact pages are not known.
Operate a live page	firecrawl_interact and firecrawl_interact_stop	You need clicks, form fills, navigation, or dynamic-page extraction.
Research papers and repositories	firecrawl_research_*	You need paper discovery, paper reading, related work, or public repository search.
Answer a programming question	firecrawl_developer_search	You need primary-source answers from issues, merged pull requests, READMEs, and curated docs.
Monitor changes	firecrawl_monitor_*	You need recurring checks, diffs, and webhook or email notifications.
Send product feedback	firecrawl_search_feedback and firecrawl_feedback	You want to rate search results or report endpoint-level quality.

Use the schema shown by your MCP client for the current arguments. The feature guides below explain the underlying Firecrawl behavior without duplicating those schemas here.

Important behavior

Parse a local file

A local MCP server connected to a self-hosted Firecrawl API can read filePath directly. The hosted server cannot read files from your machine, so it uses a two-call handoff:

1. Call firecrawl_parse with filePath to receive an upload command and uploadRef.
2. Run the upload command on the machine that can read the file.
3. Call firecrawl_parse again with the returned uploadRef.

The upload command uses a short-lived signed target and does not contain your Firecrawl API key. Use firecrawl_scrape for a public document URL.

Check a running crawl

firecrawl_crawl and firecrawl_agent return job identifiers. Use firecrawl_check_crawl_status or firecrawl_agent_status until the job completes or fails.

Close Interact sessions

Start with a url, or reuse the scrapeId from a previous Scrape call. When the workflow is finished, call firecrawl_interact_stop with the scrapeId to release the session.

Manage monitors safely

The firecrawl_monitor_* family creates, lists, updates, runs, and inspects recurring monitors. firecrawl_monitor_delete permanently removes a monitor and should be called only when the user explicitly intends to delete it.

Enable optional feedback tools

Set FIRECRAWL_NO_SEARCH_FEEDBACK=1 to prevent firecrawl_search_feedback from being registered. Set FIRECRAWL_NO_ENDPOINT_FEEDBACK=1 to prevent firecrawl_feedback from being registered.

Feature guides

Scrape

Extract content or structured fields from one URL.

Search

Find relevant web, news, image, and developer sources.

Crawl

Traverse and extract a site or section.

Parse

Convert files into LLM-ready output.

Interact

Operate dynamic pages in a live browser session.

Agent

Run autonomous multi-source research.

Monitoring

Track page changes and receive notifications.

Troubleshooting

• A tool is missing: confirm the connection mode on Agent MCP or Human MCP, reconnect or restart the client, and check whether team policy disables optional tools.
• The client returns 401: repeat the OAuth sign-in or verify that the configured bearer-token environment variable contains a current Firecrawl API key.
• The client is rate-limited: review the current rate limits, wait for the retry interval, or move from keyless to authenticated access.