Connect FireCrawl to GitHub Copilot
Give GitHub Copilot governed access to FireCrawl’s 28 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add FireCrawl to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve FireCrawl in Runlayer
Add FireCrawl from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches FireCrawl’s 28 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to FireCrawl
An admin adds FireCrawl credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use FireCrawl from GitHub Copilot
FireCrawl’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
28 FireCrawl tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot 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.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every FireCrawl call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more