Firecrawl MCP Server
Related Servers
Alternatives to Firecrawl MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server implementation that integrates with Firecrawl for web scraping capabilities.158,347 npm1MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables web scraping, crawling, and content extraction capabilities through integration with Firecrawl.8158,347 npm2MIT
- FlicenseAqualityDmaintenanceA production-ready Model Context Protocol (MCP) server that integrates with the Firecrawl API to give AI assistants the power to scrape, crawl, and search the web.3-
- FlicenseCqualityCmaintenanceBuilt as a Model Context Protocol (MCP) server that provides advanced web search, content extraction, web crawling, and scraping capabilities using the Firecrawl API.41-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform advanced web scraping, crawling, searching, and data extraction through the Firecrawl API.9158,347 npmMIT
- FlicenseBqualityDmaintenanceAn MCP Server for Web scraping and Crawling, built using Crawl4AI224-
TDQS
Scored across 28 tools
Core scrape/crawl/map/agent/monitor operations are distinct, but search is split across firecrawl_search, firecrawl_developer_search, firecrawl_gov_search, and firecrawl_research_search_papers, while feedback is split between firecrawl_feedback and firecrawl_search_feedback. The descriptions clarify use cases, but an agent must still choose among overlapping search and feedback entry points.
All tools use the firecrawl_ prefix and snake_case, giving a predictable overall surface. Minor inconsistencies remain in compound ordering and status naming, such as firecrawl_check_crawl_status versus firecrawl_agent_status and firecrawl_monitor_checks versus firecrawl_monitor_check.
At 28 tools the set is heavy for an MCP surface, even for a broad web-data platform. Monitor CRUD, feedback variants, research tools, and specialized searches add many operations that could be consolidated or grouped to improve selection.
The set covers the full lifecycle for its apparent domain: scrape, crawl, map, search, agent research, browser interaction, document parsing, status checks, monitor CRUD/run/checks, research paper tools, feedback, and credit usage. Only minor gaps like job cancellation exist, and agents can work around them.