Skip to main content
Book a demo

Connect FireCrawl to Cursor

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

Book a demo Cursor setup guide

Set up

Add FireCrawl to Cursor in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, FireCrawl’s 28 tools show up in Cursor’s own tool list.

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

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

Tools

28 FireCrawl tools in Cursor

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

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

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination