Store Scraper MCP
Related Servers
Alternatives to Store Scraper MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables app intelligence across Google Play and the Apple App Store, including details, reviews, and search via a unified API.-
- AlicenseNot gradedqualityCmaintenanceEnables retrieval of App Store and Google Play reviews, ratings summaries, and ASO keyword rankings for any app using its store ID or package name.371 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides live App Store rankings, charts, app details, reviews, and search across 55 countries, enabling AI assistants to query app store data.38 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides live App Store and Google Play data as MCP tools, enabling search, app details, reviews, charts, estimates, and more through natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching the App Store, retrieving app details, discovering trending apps, and accessing screenshots and release information via Apple's public APIs.3 npm4MIT

@sonarapp/mcpofficial
AlicenseAqualityBmaintenanceProvides App Store Optimization tools for AI agents, enabling app lookup, keyword research, ASO audit, review mining, and revenue estimation across iOS and Google Play.4381 npmMIT
TDQS
Scored across 20 tools
There is significant overlap between App Store and Google Play tools with unclear boundaries. For example, 'list' and 'gp_list' both get app rankings, 'developer' and 'gp_developer' both get apps by developer, and 'reviews' and 'gp_reviews' both get reviews with pagination. This creates ambiguity about when to use which tool, especially since the descriptions don't clarify the differences beyond platform indication.
The naming is mixed but readable. Most tools use snake_case (e.g., 'gp_categories', 'versionHistory'), but there's inconsistency with 'versionHistory' using camelCase. The 'gp_' prefix for Google Play tools provides some structure, but the App Store tools lack a corresponding prefix, creating a naming asymmetry that reduces overall consistency.
With 20 tools, the count is borderline high for a store scraper server. While covering two platforms (App Store and Google Play) justifies more tools, the duplication between platforms suggests the count could be optimized. It feels heavy but not extreme, as the domain scope is reasonably broad.
The tool set provides good coverage for app store scraping, including search, rankings, reviews, developer info, and metadata like privacy and permissions. Minor gaps exist, such as no explicit update or delete operations (which may not be needed for scraping), but agents can work around this. The surface supports core workflows for both platforms effectively.