Crawl-MCP
Related Servers
Alternatives to Crawl-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server integrating Crawl4AI for universal web crawling and data extraction. Enables AI agents to crawl, extract markdown/HTML, take screenshots, generate PDFs, and execute JavaScript on web pages.51 npm7MIT
- AlicenseNot gradedqualityFmaintenanceA lightweight MCP server that exposes Crawl4AI web scraping and crawling capabilities as tools for AI agents, enabling single-page scraping and multi-page crawling with adaptive stopping.117MIT
- FlicenseBqualityDmaintenanceAn MCP Server for Web scraping and Crawling, built using Crawl4AI224-
- AlicenseAqualityBmaintenanceWeb extraction MCP server for AI agents. Extract structured data from any URL with built-in Cloudflare bypass, JavaScript rendering, and intelligent parsing. Returns clean markdown or JSON.5794 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that integrates Crawl4AI with Supabase to enable AI agents to crawl websites, store content in a vector database, and perform RAG queries.8MIT
- FlicenseNot gradedqualityDmaintenanceA locally-hosted MCP server that provides AI assistants with advanced web crawling capabilities, including structured data extraction, deep site crawling, and page screenshots. It enables users to convert single or multiple URLs into clean Markdown content for processing by LLMs without requiring external API keys for basic features.-
TDQS
Scored across 21 tools
Several tools have overlapping boundaries: crawl_url vs crawl_url_with_fallback (same operation with fallback strategies), batch_crawl vs multi_url_crawl (both crawl multiple URLs, differing only in limits/config style), and extract_structured_data vs intelligent_extract (both LLM-based extraction). The deprecated search_google/batch_search_google aliases add further surface duplication, though descriptions do flag them as aliases and help disambiguate.
All names use snake_case and mostly follow a verb_noun pattern (crawl_url, extract_entities, search_web, get_youtube_video_info). A few deviate to adjective-first phrasing (enhanced_process_large_content, intelligent_extract), which is a minor inconsistency but still readable and predictable.
21 tools is on the heavy side for a crawling/search server, and the count is inflated by two deprecated aliases plus redundant crawl variants (batch_crawl/multi_url_crawl, crawl_url/crawl_url_with_fallback). The core capability set is reasonable, but pruning the aliases and merged variants would tighten the surface.
Coverage is broad and coherent: search (single/batch/genres), crawling (single, batch, multi-URL, deep site, fallback), extraction (entities, structured data, LLM), YouTube (info, transcript, comments, batch), and file conversion, plus format/genre discovery tools. Minor gaps like sitemap/robots handling or cache/session management exist but agents can work around them.