asomaster-mcp
Related Servers
Alternatives to asomaster-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceApp Store and Google Play ASO: keyword rankings, competitors, reviews, audits and an action queue.116AGPL 3.0
- AlicenseBqualityAmaintenanceStorelift's MCP server lets Claude, ChatGPT, Cursor or any MCP client read your App Store and Google Play keyword ranks, rivals, reviews, store pages, charts and AI visibility from your Storelift workspace. The remote server is included on every plan, including Free (1 app, 25 keywords in each of 2 storefronts, no end date); the local server and public API come with Pro and Studio.85319 npm1MIT

AppmanAi MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query live App Store and Google Play data — keyword demand, rank history, top charts, competitor sets, reviews and ratings — across 100+ countries, directly inside a chat instead of a dashboard. Exposes 35 read-only tools covering app search, ASO keyword profiling, ranking trajectories, and worldwide market comparisons through a remote OAuth-authenticated endpoint.3MIT- AlicenseAqualityAmaintenanceConnects App Store and Google Play keyword data to AI assistants, enabling ASO tasks like rank tracking, keyword analysis, competitor visibility, and top charts through natural language.3089 npmMIT

@sonarapp/mcpofficial
AlicenseAqualityCmaintenanceProvides App Store Optimization tools for AI agents, enabling app lookup, keyword research, ASO audit, review mining, and revenue estimation across iOS and Google Play.43201 npmMIT
ASO Atlas MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to research App Store keywords with popularity and difficulty scores, track daily rankings across 59 storefronts, find competitor keyword gaps, optimize metadata, and review App Store Connect performance. Read tools only inspect the signed-in account, while write tools manage tracked apps, keywords, competitors, and saved lists mid-conversation.MIT
TDQS
Scored across 70 tools
Most tools have distinct purposes and the descriptions are very detailed, but with 70 tools several lifecycle groups overlap: get_overview/get_project_board/get_audit, optimizer_start/more_options/save_option/edit_locale, and add_keywords/suggest_keywords/localize_keyword. An agent can usually tell them apart by reading descriptions, but some boundaries require careful attention.
The surface is predominantly snake_case and readable, but conventions are mixed: many tools are verb_noun (get_audit, add_keywords), while optimizer_* and screenshots_* use resource-first prefixes and popular_searches is noun-only. The grouping is intentional but not a single consistent pattern.
70 tools is far beyond the well-scoped 3-15 range and above the 25+ 'too many' threshold, reaching the extreme-mismatch level in the rubric. Even though the ASO domain is broad and many tools are grouped, the total surface is unwieldy for an agent and would benefit from consolidation.
The tool set covers the full ASO lifecycle: projects, keywords, rank checks, real popularity, listing optimization, screenshots, console connections, publishing, assistant workflows, background jobs, settings, import/export, and alerts. CRUD operations exist for the main resources, and screenshot image editing is explicitly delegated to the app rather than left as an agent-facing gap.