Skip to main content
Book a demo

Connect FireCrawl to Claude Cowork

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

Book a demo Claude Cowork setup guide

Set up

Add FireCrawl to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork 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 Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, FireCrawl’s 28 tools show up in Claude Cowork’s own tool list.

    Claude Cowork 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 Cowork

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

Tools

28 FireCrawl tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork 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 Cowork

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Anthropic inference hooks (available)

    Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.

  • OTLP telemetry (available)

    Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.

In Claude Cowork

  • Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.

Frequently asked questions

Connect more

Find another combination