Firecrawl + OpenClaw
How to connect Firecrawl to OpenClaw
Connect Firecrawl to OpenClaw through Agent200's MCP server: no separate key, ready-made tools and one API key.
On this page
Overview
This guide connects Firecrawl to OpenClaw through Agent200's MCP server. When you finish, OpenClaw can search, read and act in Firecrawl with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to OpenClaw with your Agent200 API key. Firecrawl is reached with that key, so there is no separate Firecrawl key to manage.
- Connector
- Firecrawl
- Works with
- OpenClaw ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Firecrawl enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Firecrawl to OpenClaw
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to OpenClaw in the next step, as "Authorization: Bearer <your key>". One key covers Firecrawl and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose
Test your connection
Run one request to check everything is wired up.
Ask
Read the pricing page of this site and list the plans
What should come back
- An answer built from Firecrawl results.
-
Behind the scenes, OpenClaw calls an Agent200 tool for Firecrawl, such as
firecrawl_scrape_page.
If OpenClaw says it has no Firecrawl tool, check that Firecrawl is enabled for your project in the dashboard.
Get your API key
Create a key in the Agent200 dashboard. It reaches Firecrawl and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Firecrawl to OpenClaw.
Goal: connect Firecrawl to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/firecrawl/framework/openclaw/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Firecrawl is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands. 4. Check it works with this request: "Read the pricing page of this site and list the plans" What should come back: - An answer built from Firecrawl results. - Behind the scenes, OpenClaw calls an Agent200 tool for Firecrawl, such as `firecrawl_scrape_page`. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /tools/firecrawl/framework/openclaw.md
Firecrawl tools OpenClaw can call
-
Scrape a page
Readfirecrawl_scrape_pageRead one URL as clean Markdown, HTML or a screenshot.
-
Map a site
Readfirecrawl_map_siteList the URLs of a website.
-
Start a crawl
Readfirecrawl_start_crawlCrawl a website from a starting URL, with path and depth limits.
-
Get crawl results
Readfirecrawl_get_crawlRead the status and pages of a crawl.
-
Search the web
Readfirecrawl_search_webSearch the web and get the content of the results.
-
Extract data
Readfirecrawl_extract_dataPull structured fields from pages, following a schema or a prompt.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in Firecrawl.
-
02
OpenClaw picks a tool
It sees the Firecrawl tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches Firecrawl with your Agent200 API key, within the endpoints your project allows.
-
04
OpenClaw answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The connection fails right after adding the server
Check the transport is streamable-http: when it is missing OpenClaw uses SSE, which Agent200 does not serve.
Authentication refused (401)
Check headers.Authorization is Bearer ${AGENT200_API_KEY} and that AGENT200_API_KEY is set for the process running OpenClaw.
The doctor warns about a literal header value
Replace the pasted key with ${AGENT200_API_KEY} and move the key to ~/.openclaw/.env.
Changes do not reach your agent
A Gateway or agent running elsewhere needs its own reload or a restart.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Firecrawl and the tools you need are enabled in the dashboard's Connectors settings.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in OpenClaw's MCP settings, and stop using the old one. Paste the key only into OpenClaw's settings, never into a chat.