Schema | Scraper Maintenance MCP

Scraper Maintenance MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`NODE_ENV`	No	Node environment (usually 'production' for deployment)	production

Features and capabilities supported by this server

Capability	Details
`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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fuahyo/mcp-scraper-inspect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server