Scrapeer MCP Server
OfficialRelated Servers
Alternatives to Scrapeer MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables 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.21-
- AlicenseNot gradedqualityDmaintenanceEnables web scraping, crawling, structured data extraction, and browser automation through multiple AI agents including OpenAI's CUA, Anthropic's Claude Computer Use, and Browser Use.11 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.62MIT
- AlicenseAqualityCmaintenanceEnables AI agents to crawl, scrape, search, and automate browsers with anti-bot bypass, providing fast web access via 22 tools.2225 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.81 npm1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents and assistants to extract data from social media, search engines, maps, e-commerce sites, and any other website by running thousands of ready-made scrapers, crawlers, and automation tools as callable tools, with OAuth-based connection and optional agentic payments.1117,093 npm2MIT
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.