Skip to main content
Book a demo

Connect FireCrawl to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add FireCrawl to GitHub Copilot CLI in four steps

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

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

    GitHub Copilot CLI 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 GitHub Copilot CLI

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

Tools

28 FireCrawl tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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 GitHub Copilot CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot CLI 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 or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

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

Frequently asked questions

Connect more

Find another combination