asc-mcp
Related Servers
Alternatives to asc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for App Store Connect API with 208 tools across 25 workers. Manage apps, builds, TestFlight, in-app purchases, subscriptions, reviews, provisioning, screenshots, analytics, and more — directly from Claude, Cursor, VS Code, or any MCP client. Multi-account support, worker filtering, JWT auth.82MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that exposes the entire Apple App Store Connect API (1,200+ operations) as MCP tools, enabling AI assistants to query apps, manage builds, handle submissions, read analytics, and more.16 npm1MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that exposes the Apple App Store Connect API to AI agents, enabling management of apps, metadata, in-app purchases, subscriptions, TestFlight, provisioning, reviews, analytics, and more through 113 curated tools plus two generic JSON:API escape-hatch tools.3-
- AlicenseBqualityDmaintenanceAn unofficial MCP server for the App Store Connect API that enables automation of app management, reviews, TestFlight, analytics, and release processes through natural language.63243 npm2MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects Cursor, Claude Desktop, and other MCP clients to the official App Store Connect API—so you can manage iOS/macOS apps, TestFlight, in-app subscriptions, and store metadata via chat or automated tool calls.69104 npm14MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) server for Apple's App Store Connect API. Manage your iOS, macOS, tvOS, and visionOS apps directly from Claude, Cursor, or any MCP-compatible client.52243 npm22MIT
TDQS
Scored across 41 tools
Tools are largely distinct, with detailed descriptions differentiating similar areas (e.g., set_app_metadata vs. update_version_metadata, submit_for_review vs. release_version). A few pairs (review_status/app_details, release_version/manage_phased_release) could be momentarily confused, but descriptions resolve it.
All tool names use snake_case, which is consistent. Most follow a verb_noun pattern, but several are noun-only (app_details, review_status) and three use an asc_ prefix for meta tools, creating minor inconsistency.
41 tools is far above the ideal 3-15 range and exceeds the 25+ threshold for 'too many'. The domain is broad, but the sheer number increases the chance of selection errors and cognitive load.
Covers many ASC workflows, but notable gaps exist: IAP/subscription management supports only creation (no list/update/delete), screenshots only upload, and beta testers only invite. These missing operations create dead ends for common management tasks.