Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions mcp-server.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,28 +20,25 @@ Choose how the connection will authenticate. Signing in and adding an API key ar
</Card>
</CardGroup>

## Add an API key
## Sign in

[Create a Firecrawl API key](https://www.firecrawl.dev/app/api-keys), then add it as a bearer token in your client config:
Point your client at the OAuth server URL. Your client opens a browser window where you sign in to Firecrawl and approve a team:

```json
{
"mcpServers": {
"firecrawl": {
"type": "http",
"url": "https://mcp.firecrawl.dev/v2/mcp",
"headers": {
"Authorization": "Bearer <FIRECRAWL_API_KEY>"
}
"url": "https://mcp.firecrawl.dev/v2/mcp-oauth"
}
}
}
```

Configure the key through an environment variable or your client's secret storage, never in the MCP URL.
No API key or headers are needed. Review and revoke connections from [MCP settings](https://www.firecrawl.dev/app/settings?tab=mcp).

<Note>
This is a server URL for your MCP client, not a page to open directly in a browser. Sign-in connections use `https://mcp.firecrawl.dev/v2/mcp-oauth` instead, and your client starts the browser flow.
This is a server URL for your MCP client, not a page to open directly in a browser. API-key connections use `https://mcp.firecrawl.dev/v2/mcp` with a bearer token instead; see [Add an API key](/mcp-server/keyless#add-an-api-key).
</Note>

## Client setup
Expand Down
Loading