# How to connect Firecrawl to Grok Bot (paste one key, 29 tools) > Connect Firecrawl to Grok Bot with ClawLink: paste your Firecrawl key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/grokbot/firecrawl Grok Bot runs on its own cloud computer, so most Firecrawl guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Firecrawl setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Firecrawl actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect firecrawl` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Firecrawl. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Firecrawl** — `npx -y @useclawlink/cli connect firecrawl`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect firecrawl # connect Firecrawl (browser OAuth) npx -y @useclawlink/cli actions firecrawl # list available actions npx -y @useclawlink/cli run firecrawl --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect firecrawl ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Firecrawl to batch scrape and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Firecrawl is connected in the dashboard, that agent calls the same 29 Firecrawl tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Firecrawl MCP for Grok Bot Looking for a Firecrawl MCP server for Grok Bot? ClawLink connects Firecrawl to Grok Bot and exposes 29 Firecrawl tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Firecrawl integration](https://claw-link.dev/openclaw/firecrawl) and the [Hermes Firecrawl integration](https://claw-link.dev/hermes/firecrawl) connect the same ClawLink account the same way. ## What the Grok Bot Firecrawl integration can do 29 Firecrawl tools are ready for Grok Bot once the account is connected. The 28 below are the ones people reach for most; your agent can call all 29. ### 28 of 29 Firecrawl tools for Grok Bot | Tool | What it does | |---|---| | **Batch scrape** `firecrawl_batch_scrape` | Scrape multiple URLs in batch with concurrent processing | | **Batch scrape cancel** `firecrawl_batch_scrape_cancel` | Cancel a running batch scrape job | | **Crawl** `firecrawl_crawl` | Initiate a web crawl from a given URL with filtering and extraction rules | | **Crawl cancel** `firecrawl_crawl_cancel` | Cancel an active or queued web crawl job | | **Crawl get** `firecrawl_crawl_get` | Retrieve the status and results of a crawl job | | **Crawl v2** `firecrawl_crawl_v2` | Initiate a Firecrawl v2 web crawl with enhanced features and natural language configuration | | **Credit usage get** `firecrawl_credit_usage_get` | Get current team credit usage information | | **Extract** `firecrawl_extract` | Extract structured data from web pages using natural language or a JSON schema | | **Extract get** `firecrawl_extract_get` | Retrieve the status and results of an extract job | | **Get agent status** `firecrawl_get_agent_status` | Get the status and results of an agent job | | **Llms txt generate** `firecrawl_llms_txt_generate` | Generate an LLMs.txt file for a website | | **Map multiple URLS based on options** `firecrawl_map_multiple_urls_based_on_options` | Map a website by discovering URLs from a starting base URL | | **Scrape** `firecrawl_scrape` | Scrape a publicly accessible URL and retrieve content in specified formats | | **Search** `firecrawl_search` | Search the web and scrape content from top results | | **Start agent** `firecrawl_start_agent` | Start an agent job for agentic web extraction with multi-page navigation | | **Batch scrape get** `firecrawl_batch_scrape_get` | Retrieves the current status and results of a batch scrape job using the job ID | | **Batch scrape get errors** `firecrawl_batch_scrape_get_errors` | Retrieve error details from a batch scrape job, including failed URLs and URLs blocked by | | **Crawl get errors** `firecrawl_crawl_get_errors` | Retrieve errors from a Firecrawl crawl job | | **Crawl list active** `firecrawl_crawl_list_active` | Retrieve all active crawl jobs for the authenticated team | | **Crawl params preview** `firecrawl_crawl_params_preview` | Preview crawl parameters before starting a crawl by generating optimal configuration from | | **Credit usage get historical** `firecrawl_credit_usage_get_historical` | Retrieve historical team credit usage on a monthly basis | | **Get deep research status** `firecrawl_get_deep_research_status` | Retrieves the status and results of a deep research job by its ID | | **Get the status of a crawl job** `firecrawl_get_the_status_of_a_crawl_job` | Retrieves the current status, progress, and details of a web crawl job, using the job ID | | **Llms txt get** `firecrawl_llms_txt_get` | Get the status and results of an LLMs.txt generation job | | **Queue get** `firecrawl_queue_get` | Retrieve metrics about the team's scrape queue | | **Token usage get** `firecrawl_token_usage_get` | Retrieve the current team's token usage and balance information for Firecrawl's Extract feature | | **Token usage get historical** `firecrawl_token_usage_get_historical` | Retrieve historical team token usage on a monthly basis | | **Agent cancel** `firecrawl_agent_cancel` | Cancel an in-progress agent job by its ID | ## Example prompts **Batch Scrape** > Use Firecrawl to batch scrape and walk me through the result in plain English. **Batch Scrape Cancel** > Use Firecrawl to batch scrape cancel and walk me through the result in plain English. **Crawl** > Use Firecrawl to crawl and walk me through the result in plain English. **Crawl Cancel** > Use Firecrawl to crawl cancel and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Firecrawl working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Firecrawl API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Firecrawl account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Firecrawl. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Firecrawl actions to the runtime in a format your agent can reliably use. | 29 tools for Firecrawl are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Firecrawl to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Firecrawl in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Firecrawl key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Firecrawl from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Firecrawl tools Firecrawl tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Firecrawl call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Firecrawl returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Firecrawl has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Grok Bot Firecrawl integration? Yes. ClawLink is the fastest way to connect Grok Bot to Firecrawl: link your Firecrawl account once in the browser and Grok Bot can call the Firecrawl API through 29 ready-made tools — no custom code or token handling. ### How do I connect Firecrawl to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect firecrawl` to authorize Firecrawl. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files, and the Firecrawl key you paste is stored server-side instead of in your environment. ### How long does it take to connect Firecrawl to Grok Bot? About two minutes. Sign in, click Connect next to Firecrawl in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Firecrawl up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Firecrawl working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [PostHog](https://claw-link.dev/grokbot/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/grokbot/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Grok Bot Metabase integration](https://claw-link.dev/grokbot/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.