Firecrawl (local) logo

Firecrawl (local)

Beta

Firecrawl's web scraping and crawling server. The pages it reads pass through Firecrawl's API.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Firecrawl

How it works

Every agent request passes through Ferentin policy before it reaches Firecrawl (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y firecrawl-mcp.

Ferentin's endpoint agent finds Firecrawl (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Firecrawl (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Firecrawl (local)

Firecrawl's web scraping and crawling server. The pages it reads pass through Firecrawl's API.

Frequently asked about Firecrawl (local)

How do I connect Firecrawl (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Firecrawl (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Firecrawl (local) integration generally available?
The Firecrawl (local) integration is currently beta on Ferentin.