Connect FireCrawl to Goose
Give Goose governed access to FireCrawl’s 28 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add FireCrawl to Goose in four steps
Admins approve the server once. Everyone in Goose 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 Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches FireCrawl’s 28 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose 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 Goose
FireCrawl’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
28 FireCrawl tools in Goose
Runlayer policy decides which of these Goose 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 Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every FireCrawl call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose 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 Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more