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
- AlicenseNot gradedqualityDmaintenanceMCP server to scrape web pages to clean Markdown via headless Chromium, with support for single or batch URLs.MIT
- 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.54 npm5MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to fetch webpages and crawl sites, extract main content, and convert it into clean Markdown with preserved links for fast, token-efficient scraping.-
TDQS
Scored across 63 tools
The browser_* family is granular but the descriptions actively disambiguate overlapping pairs (browser_fill vs browser_type, browser_get_text vs browser_get_html vs browser_get_attribute vs browser_query_selector_all, the three browser_wait variants). Cross-references also clarify scrape vs extract vs batch_create vs crawl_create and batch_status vs batch_wait. A few reading/waiting tools and crawl_get vs crawl_results still border on overlap, but an agent can reliably select the right tool.
Everything is snake_case with clear namespace prefixes (browser_, batch_, crawl_, account_) that map to the platform's sub-APIs, and most tools follow verb_noun (browser_click, batch_create, crawl_wait). Minor deviations exist: crawl_results and crawl_content are noun phrases among verb-prefixed crawl tools, and scrape/extract/prepare_domain/prepared_domain_status depart from the prefixed scheme.
63 tools is very heavy and well beyond the 3-15 sweet spot; an agent must wade through ~38 browser_* tools before reaching scrape/extract/batch/crawl. The breadth is legitimately backed by four distinct sub-APIs (browser, scraper, batch, crawl), so it is not a trivial-scope mismatch, but the surface is large enough to burden selection and context.
The surface covers full lifecycle for every sub-API: browser automation (navigate, interact, tabs, storage/cookies, waits, evaluate, screenshot/PDF, close), scraping (scrape, extract, prepare_domain + status), batch (create, wait, status, results, content, pause/resume/cancel/rerun/delete, list), and crawl (create, wait, get, results, content, download, stop, list), plus account usage and signup. No obvious dead ends for the stated platform scope.