Test

Created By
mendableaia year ago
Overview

What is Firecrawl MCP Server?

Firecrawl MCP Server is a Model Context Protocol (MCP) server implementation that integrates with Firecrawl for web scraping capabilities, allowing users to extract data from websites efficiently.

How to use Firecrawl MCP Server?

To use the Firecrawl MCP Server, you can run it using npx with your Firecrawl API key or install it manually. Configuration is required for different environments like Cursor or VS Code.

Key features of Firecrawl MCP Server?

  • Web scraping, crawling, and discovery
  • Search and content extraction
  • Deep research and batch scraping
  • Automatic retries and rate limiting
  • Cloud and self-hosted support
  • SSE support

Use cases of Firecrawl MCP Server?

  1. Extracting content from multiple web pages.
  2. Discovering URLs on a website before scraping.
  3. Conducting in-depth research on various topics.

FAQ from Firecrawl MCP Server?

  • Can I use Firecrawl MCP Server for any website?

Yes, as long as you comply with the website's terms of service.

  • Is there a limit to the number of pages I can scrape?

The limit depends on your API key and the configuration settings you choose.

  • How do I handle errors during scraping?

The server includes robust error handling with automatic retries for transient errors.

Server Config

{
  "mcpServers": {
    "firecrawl-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "firecrawl-mcp"
      ],
      "env": {
        "FIRECRAWL_API_KEY": "YOUR-API-KEY"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mendableai
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago