Firecrawl MCP Server

Firecrawl's MCP server enables AI agents to crawl complex, JavaScript-rendered websites and convert raw web pages into clean, LLM-ready markdown or structured JSON. It equips agents to crawl entire subdomains, extract clean text without boilerplate, and ingest clean web documentation directly into agent prompts.

Start for free

Benefits with Ory + Firecrawl MCP Server

Firecrawl's MCP server lets your agents scrape single pages, map and crawl whole sites, search the web, and extract structured data, all on your Firecrawl account. A quick scrape is cheap, while a broad crawl can run long and use credits fast. Ory Agent Security decides which of your agents can use Firecrawl tools based on who they work for, and it ties every tool call to the user and agent behind it.

View documentation

Use Cases

— 01 use case

Agent IAM

Scrapers and searchers at Read, crawl and extraction agents at Write, live browser work at Admin, and Block set for agents that should spend nothing.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Firecrawl MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for agents doing quick scrapes and searches, write for data agents responsible for larger jobs, admin for the specialized agents your data team trusts, and no access for agents with no reason to send URLs to Firecrawl.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied crawl stops before it reaches your Firecrawl account, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents start crawls and how much they use without blocking anything, so you can apply Ory's pre-built policy for the Firecrawl MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Firecrawl MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent started a crawl and on whose behalf.