web-scraper-server
Related Servers
Alternatives to web-scraper-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a real browser that bypasses bot detection (Cloudflare, Turnstile) for AI agents, enabling navigation, clicking, typing, screenshots, and data collection through MCP tools.354 npmMIT
- AlicenseAqualityBmaintenanceProvides MCP tools for web scraping, including smart fetching, proxy rotation, and browser rendering to bypass anti-bot challenges and render JavaScript-heavy sites.4493 npm6MIT
- FlicenseNot gradedqualityCmaintenanceHeadless browser automation for LLM agents via REST API or MCP tools. Enables navigating pages, reading structured content, clicking elements, filling forms, and executing JavaScript.-
- AlicenseNot gradedqualityAmaintenanceEnables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.11Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to navigate, interact with, and automate websites through an anti-detection browser backend, offering 47 tools for tabs, navigation, interaction, observation, search, downloads, sessions, profile reuse, and batch workflows.544 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides a headless Chromium browser through MCP, enabling AI agents to browse JavaScript-rendered pages, search the web, capture screenshots, extract tables and data, and run stateful multi-step interactions like clicking, typing, and form submission.1,726,779 npm1MIT
TDQS
Scored across 62 tools
Multiple overlapping tool pairs exist, such as `screenshot` vs `browser_screenshot`, `click_element` vs `browser_click`, `get_sitemap` vs `crawl_site`, and `save_pdf` vs `download_file`. The split between browser-based and non-browser-based workflows adds confusion, forcing agents to choose between near-equivalent tools based on session state.
Tool names are predominantly snake_case with a verb_noun convention (`scrape_url`, `get_metadata`, `list_jobs`). The `browser_` prefix provides a consistent subgroup, and most deviations are minor (e.g., `health_check` instead of `check_health`). Long diagnostic tool names are slightly awkward but still follow the general pattern.
With 62 tools, the server far exceeds a coherent scope. Many tools are highly specialized diagnostics or configuration variants that could be consolidated. The sheer volume makes the surface overwhelming and dilutes the clarity of the core scraping workflow.
The tool set covers the full web scraping lifecycle: URL validation, fetching, content extraction, crawling, browser automation, job scheduling, configuration, caching, session management, and diagnostics. No major scraping capability appears to be missing, making the server functionally comprehensive.