firecrawl-mcp-server and crawl4ai-mcp-server
These are direct competitors offering similar web scraping capabilities via MCP servers, with Firecrawl being the established cloud-hosted option and Crawl4AI being a self-hosted alternative with lower overhead.
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 crawl4ai-mcp-server
sadiuysal/crawl4ai-mcp-server
🕷️ A lightweight Model Context Protocol (MCP) server that exposes Crawl4AI web scraping and crawling capabilities as tools for AI agents. Similar to Firecrawl's API but self-hosted and free. Perfect for integrating web scraping into your AI workflows with OpenAI Agents SDK, Cursor, Claude Code, and other MCP-compatible tools.
Implements a stdio-based MCP server using Playwright for browser automation, exposing granular tools for single-page scraping (`scrape`), multi-page breadth-first crawling (`crawl`), and large-scale sitemaps (`crawl_site`/`crawl_sitemap`) with optional persistent storage to disk. Supports adaptive crawling that intelligently stops when sufficient content is gathered, safety constraints blocking private IPs, and integration with OpenAI Agents SDK, Cursor, and Claude Code through standardized MCP configuration.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work