Scrapeer MCP Server
OfficialRelated Servers
Alternatives to Scrapeer MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to search for and execute automated browser workflows through Autopilot Browser's API, allowing web scraping, data extraction, and other browser automation tasks via natural language commands.21MIT
- FlicenseNot gradedqualityAmaintenanceEnables language models to perform AI-powered web scraping, structured extraction, search, crawling, schema generation, and scheduled monitoring through an integrated web-scraping API.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to scrape and extract web data, run searches and crawls, generate schemas, and manage scheduled monitors through an external web-scraping API.-
- FlicenseNot gradedqualityAmaintenanceEnables language models to use AI-powered web scraping, extraction, search, crawling, schema generation, monitors, and account history through an API integration.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to open URLs in a persistent headless browser and interact with pages by clicking, typing, selecting, reading content, evaluating JavaScript, waiting for elements, and capturing screenshots.39 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables language models to scrape and extract web content, run searches, crawl multiple pages, generate JSON schemas, schedule monitors, and manage account history through a unified protocol interface.-
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: flows, runs, account, and block catalog are separate. The two run tools are clearly differentiated (immediate vs wait), and update_flow vs patch_flow are distinguished by scope (full replace vs granular ops). No two tools appear to do the same thing.
All tools follow a consistent scrapeer_verb_noun pattern in snake_case (list_flows, get_flow, run_flow, get_run_status, create_flow). Even compound names like run_flow_and_wait and get_block_catalog maintain the pattern, making the set highly predictable.
15 tools is within the ideal 3-15 range and each tool earns its place by covering a distinct aspect of flow and run lifecycle management. The count feels well-scoped for a scraping platform, not bloated or thin.
The tool set covers flow management (list, get, create, update, patch, validate) and run management (run, wait, status, results, steps, list, cancel) plus account and block catalog. The main gap is the lack of a delete_flow tool, but core workflows are otherwise well covered.