Skip to main content
Choose the setup that matches how the connection will run. You do not need to decide whether you are a human or an agent.

Try instantly

No account or key. Use Search, Scrape, and Parse with a daily limit shared by users on the same public IP.

Sign in with your account

Browser sign-in (OAuth) from ChatGPT, Claude.ai, Codex, Claude Code, and other interactive clients. Broader tool access.

Use an API key

Stable access for agents, CI, and backends. Keep the key outside chat and source control.
The hosted keyless and API-key server URL is:
This is a server URL for your MCP client, not a page to open directly in a browser. OAuth uses a different server URL and your client starts its browser sign-in flow.
If you choose an API key, never put it in an MCP URL, an agent conversation, or a committed project file. Configure it through an environment variable or your client’s secret storage.

​
Fix a broken connection

Use this section when a Firecrawl error mentions KEYLESS_QUOTA_EXHAUSTED, KEYLESS_TOOL_NOT_AVAILABLE, KEYLESS_ACCESS_NOT_AVAILABLE, KEYLESS_ELIGIBILITY_UNAVAILABLE, CREDENTIAL_INVALID, OAUTH_CONNECTION_INVALID, or a credential that is “invalid or revoked.”
  • Keyless limit reached: wait for the error’s retry_after_seconds (when present), or ask the human operator to connect with OAuth or configure an API key. Search, Scrape, and Parse remain available after the limit resets.
  • Keyless access unavailable: for KEYLESS_ELIGIBILITY_UNAVAILABLE, retry after the indicated interval. If it persists, or the error is KEYLESS_ACCESS_NOT_AVAILABLE, ask the human operator to connect with OAuth or configure an API key.
  • Tool not available on keyless (KEYLESS_TOOL_NOT_AVAILABLE): the tool exists but is not on the keyless surface. Connect with OAuth or configure an API key to use it; Search, Scrape, and Parse keep working keyless.
  • API key invalid or revoked: the human or system operator must replace the key in the existing server configuration, outside the agent conversation.
  • OAuth connection invalid on /v2/mcp: either add an API key to that existing server or change its URL to https://mcp.firecrawl.dev/v2/mcp-oauth and sign in through the client. Do not open that URL directly in a browser.
  • OAuth connection invalid on /v2/mcp-oauth: sign in again through the client’s account-connection flow.
After any credential or server-URL change, keep one firecrawl server entry, start a new client session, and retry. See OAuth connection or API-key setup for exact steps.

​
Go deeper

Choose a tool

Match a job to the right Firecrawl MCP tool and check which tools each connection mode provides.

Run MCP locally

Run the open-source MCP server over stdio or Streamable HTTP.