Skip to main content

​
Connect with OAuth

https://mcp.firecrawl.dev/v2/mcp-oauth is a server URL for your MCP client. It is not a page to open directly in a browser. Your client starts the browser sign-in flow.
Use OAuth when a person is present to sign in, choose a Firecrawl team, and approve access. The client receives tokens for that connection instead of asking you to copy a Firecrawl API key into the conversation. The sign-in page asks you to choose a team and approve the connection. If the client asks for an OAuth Client ID or Client Secret, leave both blank. Compatible clients identify themselves automatically. Requests made through this connection use the selected team. You can review or revoke the connection from MCP settings. Need an unattended connection instead? Use the API-key setup. Do not paste the key into an agent conversation or put it in the MCP URL.

​
Verify the connection

Start a new client session, then try:
If no Firecrawl tools appear, open the client’s MCP status, confirm that firecrawl is authenticated, and check that only one Firecrawl server entry is active.

​
Switch an existing keyless connection

Update or replace the existing firecrawl server with the OAuth server URL. Do not add a second Firecrawl entry. After the change, start a new client session before retrying the request.

​
Codex

Run:
Codex replaces the existing server with the same name. Enter /mcp and confirm that firecrawl is connected.

​
Claude Code

Claude Code does not overwrite an existing server with the same name. Remove the current entry, then add the OAuth entry:
Open /mcp in Claude Code and complete the browser sign-in.

​
Other clients

Edit the existing firecrawl server and set its URL to:
Save the configuration, complete the sign-in started by the client, then open a new client session.

​
Compatibility and security details

Existing OAuth tokens issued for /v2/mcp remain supported there. New interactive connections use /v2/mcp-oauth, and tokens issued for that account resource are not accepted by /v2/mcp.
Firecrawl uses OAuth Authorization Code with PKCE. Compatible clients can identify themselves with a Client ID Metadata Document or Dynamic Client Registration, so they do not need a client secret.Firecrawl accepts HTTPS redirect addresses and loopback redirects on localhost, 127.0.0.1, or [::1]. For a native client using a loopback redirect, the port may change between runs. The rest of the registered redirect address must match exactly.
Access tokens expire after one hour. Refresh tokens rotate after a successful refresh. Each connection is bound to its OAuth client, user, team, scope, and MCP resource.A new token issued for /v2/mcp-oauth is not accepted by /v2/mcp. Tokens with a missing or ambiguous audience fail closed.
Open MCP in Firecrawl Settings and revoke the connection. Revocation invalidates its access and refresh tokens. Reconnect from the client to authorize it again.
Requests made through a connection consume the credits of the team selected during sign-in, under that team’s plan. Each connection is listed in MCP settings, where it can be reviewed and revoked at any time. For SSO and organization-wide controls, see Enterprise.

​
More resources

Compare connection options

Return to the MCP setup chooser.

Choose a tool

Review the Firecrawl MCP tool surface.