Scraper Maintenance MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment (usually 'production' for deployment) | production |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_scraper_configC | Load a scraper configuration file |
| initialize_browserC | Initialize browser for inspection with custom options |
| navigate_to_pageB | Navigate browser to a specific URL |
| inspect_field_manuallyB | Start manual inspection for a specific field using visual element selection |
| auto_detect_fieldC | Automatically detect elements for a field using AI-like heuristics |
| validate_selectorsB | Validate existing selectors and check their reliability |
| generate_selectorsC | Generate multiple selector variations for an element |
| test_extractionC | Test data extraction using current selectors |
| update_configA | Update scraper configuration with new selector mappings |
| run_maintenance_checkC | Run comprehensive maintenance check on scraper configuration |
| generate_extractor_codeC | Generate extractor code based on current configuration |
| take_screenshotC | Take a screenshot of the current page |
| close_browserA | Close the browser and cleanup resources |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.