Back
GitHubGitHub RepoNeeds ReviewtoolsNew
firecrawl/firecrawl
Give agents a local scraping and crawling API or MCP server, and set FIRECRAWL_CLOUD=off when failed scrapes must stay local.
GitHubNov 21, 20262 min
Source Summary
Firecrawl Local runs scraping, crawling, and mapping on one machine and can expose a local API or MCP server to coding agents. Some failed local scrapes can fall back to Firecrawl Cloud unless that route is disabled.
Practical Implication
For an agent that needs local web context, the CLI can configure Claude Code, Cursor, Windsurf, Gemini CLI, and Codex, backing up config files first. JavaScript-heavy pages need local Chrome or Chromium, and MCP requires Node.js 22 or newer.
Agent-Ready Context
**Firecrawl Local** runs scraping, crawling, and mapping on your machine without a database, queue, or container. It can connect to coding agents as an MCP server and serve the Firecrawl v2 API on localhost; its API routes need no key. For an agent that needs local web context, the CLI can configure Claude Code, Cursor, Windsurf, Gemini CLI, and Codex, backing up config files first. JavaScript-heavy pages need local Chrome or Chromium, and MCP requires **Node.js 22 or newer**. Some single-page scrapes that fail locally are fetched through Firecrawl Cloud by default; set `FIRECRAWL_CLOUD=off` to keep work local. Cloud features such as Alexandria are not included in self-hosting, and the project is primarily AGPL-3.0 licensed.
Context Map
Uncertainty
Automatically selected from source material; feed7 has not independently tested the claim.
Rate This Item
Personal Note
No note yet. Notes are included in exported bundles.
Related — Every Edge Explained
No approved edges yet for this post.