Firecrawl Mcp Server

Created By
mendableaia year ago
Official Firecrawl MCP Server - Adds powerful web scraping to Cursor, Claude and any other LLM clients.
Overview

What is Firecrawl MCP Server?

Firecrawl MCP Server is an implementation of the Model Context Protocol (MCP) that enhances web scraping capabilities for various LLM clients, including Cursor and Claude.

How to use Firecrawl MCP Server?

To use the Firecrawl MCP Server, you can run it using npx or install it manually via npm. Configuration is required to set up the API key and other environment variables.

Key features of Firecrawl MCP Server?

  • Powerful web scraping with JavaScript rendering support
  • Automatic retries with exponential backoff
  • Efficient batch processing with rate limiting
  • Comprehensive logging and credit usage monitoring
  • Support for both cloud and self-hosted instances

Use cases of Firecrawl MCP Server?

  1. Scraping content from websites for data analysis
  2. Automating data collection for research purposes
  3. Extracting structured information from web pages using LLM capabilities

FAQ from Firecrawl MCP Server?

  • Can I use Firecrawl MCP Server for any website?

Yes, as long as the website allows scraping, you can use Firecrawl MCP Server to extract data.

  • Is there a limit to the number of requests I can make?

Yes, there are rate limits in place to prevent overwhelming the server, but you can configure these settings.

  • How do I monitor my credit usage?

The server includes a credit usage monitoring feature that alerts you when you reach specified thresholds.

Server Config

{
  "mcpServers": {
    "firecrawl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "fc-af1b3ac1a0c2402485402fd0e34da158"
      }
    }
  }
}
Project Info
Featured
Created At
a year ago
Updated At
a year ago
Author Name
mendableai
Star
3317
Language
JavaScript
License
MIT license
Category

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago