zenrows-mcp
OfficialRelated Servers
Alternatives to zenrows-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceRemote MCP server for web scraping with anti-bot evasion. Provides stealth HTTP fetching, headless browser with Cloudflare bypass, CSS selectors, YouTube transcripts, and Markdown conversion.1MIT
- AlicenseAqualityAmaintenanceMCP server for web scraping with natural language, enabling site crawling, page fetching, and extraction of emails, phones, links, and social profiles. Returns clean markdown, handles JavaScript rendering, and respects rate limits.241MIT
- FlicenseNot gradedqualityDmaintenanceMCP server to scrape web pages to clean Markdown via headless Chromium, with support for single or batch URLs.-
- AlicenseAqualityDmaintenanceMCP-native web scraping and search API for AI agents. Converts any URL to clean Markdown with 90% success rate, including Cloudflare-protected sites and JS SPAs. Real-time web search via Brave Search API. CAPTCHA solving built-in. 10 free scrapes/day.52 npm5MIT
- AlicenseAqualityAmaintenanceEnables fetching any public web page through managed proxies, with optional JavaScript rendering, returning markdown, text, HTML, or structured JSON.137 npm33 PyPI11MIT
TDQS
Scored across 52 tools
Most tools target distinct actions or resources, and the descriptions explicitly differentiate overlapping pairs such as browser_type vs browser_fill, scrape vs extract, and batch vs browser_batch. However, with 52 tools there are still several close pairs (browser_get_text vs browser_query_selector_all, crawl_get vs crawl_results, and the three browser wait variants) that could occasionally be confused.
All tool names use consistent snake_case with predictable domain prefixes (browser_, crawl_, batch_) and clear verb/noun structure. The few unprefixed tools (scrape, extract, account_usage) are still readable and fit the overall convention.
52 tools is far above the typical 3–15 range, even for a platform spanning scrape, extract, crawl, batch, and browser automation. The tools are largely non-redundant, so the set is not chaotic, but the surface is still too heavy for an agent to manage comfortably.
The server covers the full Zenrows workflow: single-page scrape, structured extract, async crawl (create/get/list/results/content/download/stop/wait), async batch (create/status/results/cancel/wait), browser sessions with comprehensive interaction and query tools, and account usage. No major lifecycle gaps are apparent.