workingproxysites.

Web-data service integration · Official publisher

Firecrawl MCP

Start with keyless access for a small Search, Scrape or Parse task. Choose OAuth or an API key when your workflow needs the account tool surface. The connection decision controls which operations your assistant can discover.

Server publisher: Firecrawl. Guide maintained by Working Proxy Sites.

Documentation reviewed · Next review

What you can use it for

  • Read a known URL as content or structured fields.
  • Find relevant pages before extracting them.
  • Run a bounded crawl or an authenticated browser interaction.

Documented capabilities: Web search · Scraping & extraction · Browser automation.

Account & usage

Account required
No for the listed keyless tools
Required product
Keyless hosted Search, Scrape and Parse; a Firecrawl account/team for authenticated tools.
Billing basis
Keyless use has daily per-IP caps. Account use consumes plan credits and any option charges; returned target error pages can be billable. Scrape JSON adds extraction credits, and browser sessions use separate time-based billing. Provider pricing.
Server software license
MIT

When to choose Firecrawl MCP

A useful fit when

  • An assistant that needs web search followed by content from a selected URL.
  • A workflow that chooses explicitly between readable content, schema-guided fields and an authenticated crawl.

Check another approach when

  • A raw residential-proxy endpoint to put in an HTTP client.
  • Assuming every hosted tool is available anonymously or under every team policy.
Sources: Firecrawl current MCP tools and troubleshooting, Firecrawl keyless and bearer-key configuration, Firecrawl MCP connection modes

Use the HTTP API in your application

For request bodies, output formats and response checks, read the Firecrawl API guide.

Connect to Firecrawl MCP

Choose a connection profile below and replace credential placeholders in your own MCP client. The transport describes the MCP connection.

Try Search, Scrape and Parse without an account

Streamable HTTP · hosted

Endpoint
https://mcp.firecrawl.dev/v2/mcp
Authentication
No key or account; daily per-IP request and credit caps apply.

Before you connect

  • Cursor or another client supporting remote Streamable HTTP.
  • Use the three documented keyless tools; broader tool access requires sign-in or a key.

Cursor mcp.json (JSON) Sources: Firecrawl keyless and bearer-key configuration, Firecrawl keyless and account rate limits, Cursor MCP configuration and authentication

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Configuration guide.

{
  "mcpServers": {
    "firecrawl": {
      "url": "https://mcp.firecrawl.dev/v2/mcp"
    }
  }
}

Sign in to a Firecrawl team

Streamable HTTP · hosted

Endpoint
https://mcp.firecrawl.dev/v2/mcp-oauth
Authentication
OAuth sign-in in a compatible client; no API key pasted into this profile.

Before you connect

  • A Firecrawl account and a client supporting MCP OAuth.
  • Complete browser sign-in and choose the intended team; available tools follow its plan and policy.

Cursor mcp.json (JSON) Sources: Firecrawl MCP connection modes, Firecrawl OAuth account connection, Cursor MCP configuration and authentication

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Configuration guide.

{
  "mcpServers": {
    "firecrawl": {
      "url": "https://mcp.firecrawl.dev/v2/mcp-oauth"
    }
  }
}

Use a Firecrawl API key

Streamable HTTP · hosted

Endpoint
https://mcp.firecrawl.dev/v2/mcp
Authentication
Authorization bearer header; replace YOUR_FIRECRAWL_API_KEY in your private client configuration.

Before you connect

  • A Firecrawl account API key and a client supporting HTTP headers.
  • Use protected client settings for the real key; do not commit a populated configuration or put the key in the endpoint URL.

Cursor mcp.json (JSON) Sources: Firecrawl keyless and bearer-key configuration, Cursor MCP configuration and authentication

Cursor: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Configuration guide.

{
  "mcpServers": {
    "firecrawl": {
      "url": "https://mcp.firecrawl.dev/v2/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_FIRECRAWL_API_KEY"
      }
    }
  }
}

Find a page, choose the output, then validate it

A suggested sequence using the documented tools. Check the connected server's tool schema before making a call.

  1. Check the connection and tool list

    Save one profile in Cursor, complete any required sign-in, and inspect the discovered tools. A saved JSON file alone does not establish a working connection.

    Sources: Firecrawl keyless and bearer-key configuration, Firecrawl OAuth account connection, Cursor MCP configuration and authentication
  2. Find the URL only if needed

    Use Search when the source is unknown. If you already know the page, proceed to Scrape; a search result is a lead to inspect, not evidence that its content answers the task.

    Tools: firecrawl_search

    Sources: Firecrawl current MCP tools and troubleshooting
  3. Request the useful output

    Use Scrape for content from the selected URL. For fixed fields, choose its JSON format and supply the client schema or prompt. Check the returned target content before accepting it; extraction can add credits.

    Tools: firecrawl_scrape

    Sources: Firecrawl current MCP tools and troubleshooting, Firecrawl credit billing
  4. Keep larger work bounded

    Authenticate before a crawl and give it an explicit scope. Resume a timed-out wait with the existing crawl ID. If the task uses Interact, stop its session when finished.

    Tools: firecrawl_crawl, firecrawl_check_crawl_status, firecrawl_interact_stop

    Sources: Firecrawl current MCP tools and troubleshooting

Selected tools & example tasks

Troubleshoot the connection

401 after saving the connection

For /v2/mcp-oauth, sign in again through the client. For /v2/mcp, check the configured key or switch that entry to the OAuth URL. Start a new client session after the change.

Sources: Firecrawl current MCP tools and troubleshooting

429 or an unexpectedly long wait

Check the response and current request/concurrency limits. Reduce concurrent work and wait before retrying. Anonymous caps differ from the account plan; signing in changes the applicable limits.

Sources: Firecrawl keyless and account rate limits

Limits & undocumented behavior

  • Keyless hosted access exposes Search, Scrape and Parse only; other selected tools require authenticated access and may depend on plan or team policy.
  • The current tool guide deprecates the former Extract MCP tool. Use Scrape with JSON for a known page or Agent when sources must be discovered.
  • A hosted Parse request cannot directly open a local file. Follow its signed-upload handoff; never assume a local path has already been uploaded.
  • The hosted service version and target success rate were not measured. Client-discovered schemas determine the arguments for the connected tool surface.
  • A local MCP process is a separate deployment choice and can still call the cloud API. The profiles on this page cover hosted connections.

Firecrawl MCP: questions & answers

Does Firecrawl MCP require an API key?

The hosted server has keyless Search, Scrape and Parse. OAuth is another route to authenticated account tools without pasting an API key. A bearer key is available when that fits your client.

Sources: Firecrawl MCP connection modes, Firecrawl keyless and bearer-key configuration, Firecrawl OAuth account connection
Should I use the former Extract MCP tool?

The current guide marks it deprecated. Use Scrape with JSON for a known URL. Firecrawl recommends Agent when source pages must be discovered; inspect the connected tool schema and its account requirements.

Sources: Firecrawl current MCP tools and troubleshooting
Is a returned page necessarily successful or free to retry?

No. A returned target error page can still consume credits. Inspect the content before accepting it or retrying, and account for extraction and other optional charges.

Sources: Firecrawl credit billing

Sources & review history

This listing is documentation-confirmed. We reviewed the primary sources below; this does not establish successful tool execution.

Record updated . Review due .

  1. Firecrawl MCP connection modesChecked · Hosted keyless, OAuth and API-key modes; plan and team scope
  2. Firecrawl keyless and bearer-key configurationChecked · Remote endpoint, Cursor examples, keyless tools and bearer header
  3. Firecrawl OAuth account connectionChecked · OAuth endpoint and client sign-in
  4. Firecrawl current MCP tools and troubleshootingChecked · Tool names, access scope, Extract deprecation, upload and session behavior
  5. Firecrawl keyless and account rate limitsChecked · Daily anonymous caps versus team account rate and concurrency limits
  6. Firecrawl credit billingChecked · Base credits, extraction modifiers and failure exceptions
  7. Cursor MCP configuration and authenticationChecked · mcpServers JSON, HTTP headers, OAuth and configuration locations
  8. Official Firecrawl MCP repositoryChecked · Publisher, server implementation and MIT license
  9. Firecrawl plans and pricingChecked · Account plan offers; consult detailed billing for option charges

Spotted a change? Share the source and the affected setup step in Site Feedback.

Alternatives to Firecrawl MCP

These integrations share documented capabilities with Firecrawl MCP. Compare their setup and product requirements for your task.

Bright Data MCP

Search the public web, retrieve page content and use optional browser tools through Bright Data’s hosted or local MCP integration.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Streamable HTTP · Local stdio
Product to check
Bright Data Web Unlocker API; additional products may be used by optional tools.
Compare setup & authentication →

Evomi MCP

Inspect Evomi proxy products, targeting and usage, rotate sessions, and run scraping jobs through a local Python MCP server.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Local stdio
Product to check
Evomi Public API access plus the proxy or Scraper API product used by the tool.
Compare setup & authentication →

Novada MCP

Search, extract pages, use browser tools and configure proxy connections through Novada’s hosted endpoint or local npm package.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Streamable HTTP · Local stdio
Product to check
Novada account with access to the scraping, browser or proxy product selected by the tool.
Compare setup & authentication →

Oxylabs MCP

Connect an agent to Oxylabs scraping and AI Studio tools, with separate credentials for each product.

Shared capabilities
Web search · Scraping & extraction · Browser automation
Connection choices
Streamable HTTP
Product to check
Oxylabs Web Scraper API for the included setup; AI Studio requires its own key.
Compare setup & authentication →