Scraper Maintenance MCP
Related Servers
Alternatives to Scraper Maintenance MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for crawling and extracting data from web pages using Selenium with CSS/XPath selectors. Supports 17 tools including smart extraction, pagination, infinite scroll, and screenshots.3-
- AlicenseAqualityBmaintenanceMCP server for AI browser automation with tools for navigation, actions, data extraction, and scripting, supporting local and cloud execution.14374 npm2Apache 2.0
- AlicenseCqualityAmaintenanceMCP server for browser automation that drives Chrome via an extension, preserving login state and offering 45 tools for navigation, interaction, scraping, and screenshots.535MIT
- AlicenseAqualityAmaintenanceMCP server for agent-friendly web scraping with adaptive anti-bot bypass, dynamic rendering, and structured data extraction via 12 tools.12MIT
- FlicenseAqualityBmaintenanceMCP server for remote web scraping, providing a scrape_web tool that fetches pages and extracts content as markdown or JSON, supporting CSS selectors.1-
TDQS
Scored across 13 tools
Each tool has a distinct purpose: browser lifecycle (initialize, navigate, close), config management (load, update), field inspection (manual vs. auto), selector operations (validate, generate), and testing/maintenance (test, audit, code generation). Even similar tools like inspect_field_manually and auto_detect_field are clearly differentiated by manual vs. automatic methodology.
All tool names follow a consistent verb_noun pattern (e.g., load_scraper_config, navigate_to_page, generate_selectors). No mixed conventions or vague verbs; each name clearly indicates its action and target.
With 13 tools, the server is well-scoped for scraper maintenance. Every tool supports the core workflow without redundancy, and the count falls comfortably within the ideal 3-15 range.
The tool set covers the full maintenance lifecycle: load configuration, inspect and detect fields, validate/generate selectors, test extraction, update config, run comprehensive checks, and generate final code. Minor features like exporting configs or handling pagination are absent, but the core workflow has no dead ends.