firecrawl-mcp-server and scrapegraph-mcp
These are competitors—both provide MCP servers for web scraping, but Firecrawl offers more comprehensive features (LLM-optimized markdown conversion, search capabilities) and broader client integration, while ScrapeGraphAI focuses specifically on AI-powered graph-based scraping.
About firecrawl-mcp-server
firecrawl/firecrawl-mcp-server
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
Implements MCP (Model Context Protocol) server using stdio transport with optional HTTP Streamable mode, exposing Firecrawl's scraping, crawling, search, and agent-browser automation capabilities as callable tools. Supports both cloud and self-hosted Firecrawl instances with configurable retry logic, exponential backoff, and credit usage monitoring. Integrates directly with Cursor, Claude Desktop, VS Code, and Windsurf through standardized MCP server configuration.
About scrapegraph-mcp
ScrapeGraphAI/scrapegraph-mcp
ScapeGraph MCP Server
Implements an MCP server exposing 8 web scraping tools—from basic markdown conversion to agentic multi-step workflows—that integrate with the ScrapeGraph AI API for structured data extraction, infinite scroll handling, and JavaScript rendering. Deploys via Smithery for seamless Claude Desktop and Cursor integration, with both local and remote hosting options. Supports asynchronous multi-page crawling, custom output schemas, and persistent sessions for complex extraction workflows.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work