Skip to main content
Book a demo

Connect FireCrawl to Claude Code

Give Claude Code governed access to FireCrawl’s 28 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add FireCrawl to Claude Code in four steps

Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.

  1. 1

    Approve FireCrawl in Runlayer

    Add FireCrawl from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, FireCrawl’s 28 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to FireCrawl

    An admin adds FireCrawl credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use FireCrawl from Claude Code

    FireCrawl’s approved tools appear in Claude Code. Every call is checked against policy and recorded.

Tools

28 FireCrawl tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • Agent

    Run web research that returns structured data when the URLs are not known or the answer spans several sites.

  • Agent status

    Retrieve progress or final results for a firecrawl_agent job ID.

  • Check crawl status

    Retrieve the current status, progress, and available results for an existing crawl ID.

  • Crawl

    Start a multi-page crawl at a website URL, poll it to a terminal state, and return the final status and collected data.

  • Credit usage

    Get the authenticated Firecrawl team's current credit balance or historical credit consumption.

  • Developer search

    Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation for programming questions that need external documentation or upstream evidence.

  • Feedback

    Submit concise quality feedback for a completed search, scrape, parse, or map job.

  • Find tools

    Browse Alexandria data providers and workflows or read a selected contract.

See all 28 FireCrawl tools

Control

What Runlayer can see and stop in Claude Code

Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.

  • Gateway policy (available)

    Every FireCrawl call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination