Skip to main content
Book a demo

Connect FireCrawl to Windsurf

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

Book a demo Windsurf setup guide

Set up

Add FireCrawl to Windsurf in four steps

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

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches FireCrawl’s 28 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf 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 Windsurf

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

Tools

28 FireCrawl tools in Windsurf

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Windsurf 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Windsurf runs it.

  • Block output after it runs (not available)

    Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination