> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firecrawl.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Web Search & Scrape in Executor

> Add Firecrawl web scraping and search to Executor, the agent connector gateway

Add Firecrawl's hosted MCP server to [Executor](https://executor.sh) so every agent connected to Executor can search and scrape the web through one endpoint.

<Note>
  These steps are for Executor 1.x (`npm install -g executor`). Executor 2 (beta) organizes MCP servers as apps and accounts; see [Executor's docs](https://executor.sh/docs) for that flow.
</Note>

## Quick setup

[Create a Firecrawl API key](https://www.firecrawl.dev/app/api-keys), then start Executor:

```bash theme={null}
npm install -g executor
executor web
```

In the web UI, add an integration and choose **Firecrawl** from the catalog, or enter the MCP URL yourself:

```text theme={null}
https://mcp.firecrawl.dev/v2/mcp
```

Executor detects the MCP server and indexes its tools. When it asks for credentials, enter your Firecrawl API key so requests carry an `Authorization: Bearer <key>` header.

You can check the server from the command line first:

```bash theme={null}
executor call executor mcp probeEndpoint '{"endpoint":"https://mcp.firecrawl.dev/v2/mcp","headers":{"Authorization":"Bearer '"$FIRECRAWL_API_KEY"'"}}'
```

Then connect your agent to Executor's own MCP endpoint (`http://127.0.0.1:4788/mcp` for a local server):

```bash theme={null}
npx add-mcp http://127.0.0.1:4788/mcp --transport http --name executor
```

Run `executor tools integrations` and confirm that `firecrawl` is listed with a tool count above zero.

## Try it

```text theme={null}
Search the web for the latest Tailwind CSS release notes and summarize the sources.
```

```text theme={null}
Scrape https://firecrawl.dev and explain what it does.
```

## Troubleshooting

* **Tool count is 0:** Executor creates tools per account, so finish connecting the Firecrawl account with your API key, then refresh the source.
* **Add-server command pauses:** Executor asks you to approve adding an MCP server; accept it with `executor resume --execution-id <id> --action accept --content '{}'`.
* **Your agent does not see the tools:** most clients load MCP servers at startup, so restart the client or open a new session after adding Executor.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.