Skip to main content
Start with Connect Firecrawl MCP to choose account OAuth, unattended API-key access, or keyless access. These client-specific examples use that same mode-aware contract.

Running on Cursor

Install the hosted keyless server in one click (no API key required): Add Firecrawl MCP server to Cursor Or add it to ~/.cursor/mcp.json manually:

Running locally with an API key

Note: Requires Cursor version 0.45.6+ For the most up-to-date configuration instructions, please refer to the official Cursor documentation on configuring MCP servers: Cursor MCP Server Configuration Guide To configure Firecrawl MCP in Cursor v0.48.6
  1. Open Cursor Settings
  2. Go to Features > MCP Servers
  3. Click ”+ Add new global MCP server”
  4. Enter the following code:
To configure Firecrawl MCP in Cursor v0.45.6
  1. Open Cursor Settings
  2. Go to Features > MCP Servers
  3. Click ”+ Add New MCP Server”
  4. Enter the following:
    • Name: “firecrawl-mcp” (or your preferred name)
    • Type: “command”
    • Command: env FIRECRAWL_API_KEY=your-api-key npx -y firecrawl-mcp@3.22.4
If you are using Windows and are running into issues, try cmd /c "set FIRECRAWL_API_KEY=your-api-key && npx -y firecrawl-mcp@3.22.4"
Replace your-api-key with your Firecrawl API key. If you don’t have one yet, you can create an account and get it from https://www.firecrawl.dev/app/api-keys After adding, refresh the MCP server list to see the new tools. The Composer Agent will automatically use Firecrawl MCP when appropriate, but you can explicitly request it by describing your web data needs. Access the Composer via Command+L (Mac), select “Agent” next to the submit button, and enter your query.

Running on Windsurf

Add this to your ./codeium/windsurf/model_config.json:

Running with Streamable HTTP Mode

To run the server using streamable HTTP transport locally instead of the default stdio transport:
Use the url: http://localhost:3000/v2/mcp locally, or the hosted https://mcp.firecrawl.dev/v2/mcp

Installing via Smithery (Legacy)

To install Firecrawl for Claude Desktop automatically via Smithery:

Running on VS Code

For one-click installation, click one of the install buttons below… Install with NPX in VS Code Install with NPX in VS Code Insiders For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others:
Note: Some users have reported issues when adding the MCP server to VS Code due to how it validates JSON with an outdated schema format (microsoft/vscode#155379). This affects several MCP tools, including Firecrawl. Workaround: Disable JSON validation in VS Code to allow the MCP server to load properly. See reference: directus/directus#25906 (comment). The MCP server still works fine when invoked via other extensions, but the issue occurs specifically when registering it directly in the MCP server list. We plan to add guidance once VS Code updates their schema validation.

Running on Claude Desktop

For an interactive account connection, add the account endpoint and complete the browser OAuth flow:
For an unattended or API-key-backed configuration, use https://mcp.firecrawl.dev/v2/mcp with an Authorization: Bearer <FIRECRAWL_API_KEY> header instead. If you get a “Couldn’t reach the MCP server” error, your Claude Desktop version may not support streamable HTTP transport. Use the local npx approach instead (requires Node.js):
If you see a spawn npx ENOENT error, Node.js is not installed or not in your system PATH. Install Node.js from nodejs.org (LTS version), then fully restart Claude Desktop. On Windows, you can also run where npx in Command Prompt and use the full path (e.g. C:\\Program Files\\nodejs\\npx.cmd) as the command value.

Running on Claude Code

Add the Firecrawl MCP server using the Claude Code CLI. You can use the remote hosted URL or run locally:

Running on Google Antigravity

Google Antigravity allows you to configure MCP servers directly through its Agent interface. Antigravity MCP Installation
  1. Open the Agent sidebar in the Editor or the Agent Manager view
  2. Click the ”…” (More Actions) menu and select MCP Servers
  3. Select View raw config to open your local mcp_config.json file
  4. Add the following configuration:
  1. Save the file and click Refresh in the Antigravity MCP interface to see the new tools
Replace YOUR_FIRECRAWL_API_KEY with your API key from https://firecrawl.dev/app/api-keys.

Running on n8n

To connect the Firecrawl MCP server in n8n:
  1. Get your Firecrawl API key from https://firecrawl.dev/app/api-keys
  2. In your n8n workflow, add an AI Agent node
  3. In the AI Agent configuration, add a new Tool
  4. Select MCP Client Tool as the tool type
  5. Enter the MCP server Endpoint:
  1. Set Server Transport to HTTP Streamable
  2. Set Authentication to Bearer and paste your Firecrawl API key, or leave it as None to use the keyless free tier
  3. For Tools to include, you can select All, Selected, or All Except - this will expose the Firecrawl tools (scrape, crawl, map, search, extract, etc.)
For self-hosted deployments, run the MCP server with npx and enable HTTP transport mode:
This will start the server on http://localhost:3000/v2/mcp which you can use in your n8n workflow as Endpoint. The HTTP_STREAMABLE_SERVER=true environment variable is required since n8n needs HTTP transport.