FireCrawl MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is FireCrawl MCP Server?

FireCrawl MCP Server is a server implementation that integrates with FireCrawl for advanced web scraping capabilities, enabling users to efficiently extract content from various websites.

how to use FireCrawl MCP Server?

To use the FireCrawl MCP Server, install it via npm, generate an API key from FireCrawl, and configure your application to use the MCP server with the provided API key.

key features of FireCrawl MCP Server?

  • JavaScript rendering for scraping content from JS-heavy sites.
  • Supports mobile and desktop views.
  • Smart rate limiting to manage requests efficiently.
  • Handles multiple output formats including HTML, Markdown, and screenshots.
  • Allows batch processing for scraping multiple URLs at once.
  • Content filtering options to include or exclude specific HTML tags.

use cases of FireCrawl MCP Server?

  1. Scraping product data from e-commerce websites.
  2. Extracting content from dynamic web pages for data analysis.
  3. Automating the retrieval of news articles from various sources.

FAQ from FireCrawl MCP Server?

  • What types of content can be scraped?

You can scrape HTML, Markdown, screenshots, and more from any accessible URL.

  • Is there a rate limit on requests?

Yes, the free tier allows 3 requests per minute, with higher limits on paid plans.

  • How do I configure my API key?

Follow the installation guide to set your API key in your environment configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
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)

a day ago