Connect FireCrawl to OpenCode
Give OpenCode governed access to FireCrawl’s 28 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add FireCrawl to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode 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 OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches FireCrawl’s 28 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode 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 OpenCode
FireCrawl’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
28 FireCrawl tools in OpenCode
Runlayer policy decides which of these OpenCode 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 OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every FireCrawl call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more