Firecrawl MCP Server

<img src="https://raw.githubusercontent.com/firecrawl/firecrawl-mcp-server/main/img/fire.png" height="140"

Firecrawl MCP Server

A Model Context Protocol (MCP) server that brings Firecrawl to MCP-compatible AI agents — search, scrape, and interact with the live web for clean, agent-ready context.

Big thanks to @vrknetha, @knacklabs for the initial implementation!

Features

• Search the web and get full page content
• Search an index built for coding agents: GitHub issues, merged pull requests, READMEs, and docs
• Scrape any URL into clean, structured data
• Interact with pages — click, navigate, and operate
• Deep research with autonomous agent
• Check current and historical Firecrawl credit usage
• Automatic retries and rate limiting
• Cloud and self-hosted support
• SSE support

Play around with our MCP Server on MCP.so's playground or on Klavis AI.

When to Use This Server

• Use firecrawl_scrape when you have a known URL and want its content as markdown or as JSON matching a schema you supply.
• Use firecrawl_map when you need to discover URLs on a site without fetching their content.
• Use firecrawl_crawl when you need content from many pages under a site; set limit, includePaths/excludePaths, or maxDiscoveryDepth to bound it.
• Use firecrawl_search when you're starting from a query rather than a URL and want ranked web results; add scrapeOptions if you also want page content fetched in the same call (the search-only endpoint never fetches content).
• Use firecrawl_interact when a page needs a click, type, or navigate action before you can read it — pass a url for a fresh page or a scrapeId to continue on one you already scraped.
• Use the firecrawlmonitor tools when the same page needs to be checked on a recurring schedule with diffs and change alerts, rather than fetched once.
• Use firecrawlcreditusage to check credits left or monthly consumption, optionally broken down by API key.
• Consider something else when you need to hold a browser session open across many of your own steps with your own retry and termination logic: each firecrawlinteract call runs one prompt or code turn to completion and returns control — the session can persist across calls via scrapeId and ends with firecrawlinteract_stop, but you cannot drive it interactively step-by-step from the client side within a single call.

This server lists 26 tools when the full profile registers with default settings (feedback tools included, not running in local-keyless mode). Setting FIRECRAWLNOSEARCHFEEDBACK=1 and/or FIRECRAWLNOENDPOINTFEEDBACK=1 removes the corresponding feedback tools and reduces this count, as does local keyless startup. For clients with a tool-slot limit: the hosted keyless endpoint (https://mcp.firecrawl.dev/v2/mcp, no API key) exposes only 3 — firecrawlscrape, firecrawlsearch, firecrawl_parse — and the dedicated search-only endpoint (https://mcp.firecrawl.dev/v2/mcp-search) exposes a fixed set of 8 tools (search, developer and research search, plus Alexandria catalogue lookup and execution).

Installation

Hosted MCP (keyless free tier)

Connect to the remote hosted server with no setup:

https://mcp.firecrawl.dev/v2/mcp

On the keyless free tier, scrape, search, and parse work without an API key (rate-limited). Other tools such as crawl, map, and agent still need a key.

Prefer OAuth or an API key whenever the human can sign up. It unlocks the full tool set and higher limits.

Shortened. The full README is on GitHub.