Skip to main content
Add Firecrawl’s hosted MCP server to Executor so every agent connected to Executor can search and scrape the web through one endpoint.
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 for that flow.

​
Quick setup

Create a Firecrawl API key, then start Executor:
In the web UI, add an integration and choose Firecrawl from the catalog, or enter the MCP URL yourself:
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:
Then connect your agent to Executor’s own MCP endpoint (http://127.0.0.1:4788/mcp for a local server):
Run executor tools integrations and confirm that firecrawl is listed with a tool count above zero.

​
Try it

​
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.