How to connect the Firecrawl MCP server

To connect the official Firecrawl MCP server, add https://mcp.firecrawl.dev/v2/mcp to your MCP client as a Streamable HTTP server, then send a bearer token in the Authorization header. Firecrawl documents setup for VS Code.

Docs reviewed 5 Nov 2026Connection tested.

Try in the browser, no sign-in →

Endpoint https://mcp.firecrawl.dev/v2/mcp · Registry io.github.firecrawl/firecrawl-mcp-server 3.37.0

Open in the Firecrawl MCP explorer →Firecrawl API profile →Markdown for agents

Add Firecrawl MCP to your client

.vscode/mcp.json

{
  "servers": {
    "firecrawl": {
      "type": "http",
      "url": "https://mcp.firecrawl.dev/v2/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FIRECRAWL_API_KEY}"
      }
    }
  }
}

Set FIRECRAWL_API_KEY in your environment. Never paste keys into a shared file.

docs.firecrawl.dev/quickstarts

Connect Firecrawl MCP step by step

Before you start

A Firecrawl account and API key for the full tool set and higher limits. Without a key the endpoint offers only search, scrape and parse, rate limited. Which tools a key unlocks depends on your plan, deployment and team policy. docs.firecrawl.dev/mcp-server docs.firecrawl.dev/mcp-server

Authentication

Your client → Firecrawl MCP: Bearer token. docs.firecrawl.dev/mcp-server docs.firecrawl.dev/mcp-server registry.modelcontextprotocol.io/v0.1
Firecrawl MCP → Firecrawl API: Not established by this guide.

Steps

Open Firecrawl's MCP server documentation
docs.firecrawl.dev/mcp-server
Add the Firecrawl MCP server to your client
Add https://mcp.firecrawl.dev/v2/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"), and send your Firecrawl API key as a bearer token in the Authorization header. Keep the key in an environment variable or secret store, not in shared configuration.
docs.firecrawl.dev/mcp-server docs.firecrawl.dev/quickstarts registry.modelcontextprotocol.io/v0.1
Authorization (your Firecrawl API key)
docs.firecrawl.dev/quickstarts registry.modelcontextprotocol.io/v0.1
To sign in instead of using a key, use Firecrawl's OAuth endpoint
Add https://mcp.firecrawl.dev/v2/mcp-oauth with no headers. Your client opens a browser where you sign in to Firecrawl and approve a team. Firecrawl says signing in and adding an API key give the same access. You can review and revoke connections in Firecrawl's MCP settings. Firecrawl's Claude, VS Code and Copilot CLI guides use this endpoint by default.
docs.firecrawl.dev/mcp-server docs.firecrawl.dev/quickstarts docs.firecrawl.dev/quickstarts
To try it without an account, connect without a key
The same https://mcp.firecrawl.dev/v2/mcp endpoint works without credentials. Keyless connections get search, scrape and parse only, with rate limits.
docs.firecrawl.dev/mcp-server
List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
docs.firecrawl.dev/mcp-server

What we observed

5 Nov 2026: HTTP 200 without credentials; the server initialized as firecrawl-fastmcp 3.37.0. Its instructions say keyless sessions expose firecrawl_search, firecrawl_scrape and firecrawl_parse, and an Authorization bearer API key exposes more tools.
5 Nov 2026: initialize and tools/list succeeded without credentials from the API Tracker browser explorer: 3 tools (firecrawl_scrape, firecrawl_search, firecrawl_parse). Tool calls need an API key.

Firecrawl MCP questions

What is the Firecrawl MCP server URL?

The official Firecrawl MCP server is at https://mcp.firecrawl.dev/v2/mcp and uses the Streamable HTTP transport.

How do I authenticate with the Firecrawl MCP server?

Send a bearer token in the Authorization header.

Which AI clients can use the Firecrawl MCP server?

Firecrawl's documentation covers VS Code. Other clients that support remote Streamable HTTP MCP servers may also work.

What do I need before connecting Firecrawl MCP?

A Firecrawl account and API key for the full tool set and higher limits. Without a key the endpoint offers only search, scrape and parse, rate limited. Which tools a key unlocks depends on your plan, deployment and team policy.

Has this Firecrawl MCP guide been tested?

Firecrawl's documentation was reviewed on 2026-11-05. The connection was tested.

Sources and review

Firecrawl's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.

Guide source and binding

MCP connection guide (draft 0.1) for io.github.firecrawl/firecrawl-mcp-server 3.37.0, bound to /remotes/0 of the Registry record by SHA-256 8eb68547e20a….

Guide JSON Source snapshot

docs.firecrawl.dev/mcp-server · checked 5 Nov 2026
docs.firecrawl.dev/mcp-server/keyless · checked 5 Nov 2026
docs.firecrawl.dev/quickstarts/github-copilot · checked 5 Nov 2026
docs.firecrawl.dev/quickstarts/claude-desktop · checked 5 Nov 2026
registry.modelcontextprotocol.io/v0.1/servers/io.github.firecrawl%2Ffirecrawl-mcp-server/versions/3.37.0 · checked 5 Nov 2026

All MCP connection guides →How we review MCPs →