App Store Connect MCP Server
Related Servers
Alternatives to App Store Connect MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA 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.10 npmMIT
- AlicenseAqualityDmaintenanceA 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.5240 npm24MIT
- AlicenseAqualityCmaintenanceA 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.6982 npm13MIT
- AlicenseBqualityCmaintenanceAn unofficial MCP server for the App Store Connect API that enables automation of app management, reviews, TestFlight, analytics, and release processes through natural language.6340 npm2MIT
- FlicenseNot gradedqualityBmaintenanceAn 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.2-
- AlicenseNot gradedqualityCmaintenanceMCP server for App Store Connect that enables reading app/version data, analytics reports, sales/finance reports, and safely preparing metadata updates via natural language.MIT
TDQS
Scored across 45 tools
Each tool targets a distinct resource-action pair, with clear separation between apps, versions, builds, beta groups, IAPs, subscriptions, product pages, and experiments. Even similar-sounding tools like list_subscription_groups vs list_subscriptions are unambiguously differentiated by their resource focus.
Tool names generally follow a consistent verb_noun pattern (e.g., list_apps, get_build, create_iap). Minor deviations exist such as 'set_iap_price' vs 'update_iap' and 'submit_for_review' vs 'submit_iap_for_review', but these do not significantly hinder predictability.
With 45 tools, the server is heavily over-scoped for an agent to navigate effectively. Many tools could be consolidated (e.g., update_app_description, update_whats_new, update_keywords could be a single update_localization tool), making this count more appropriate for a library than an MCP server.
The tool set covers a wide range of App Store Connect functionality, but gaps remain: no creation/deletion for beta groups, no update/delete for subscription offers, no delete for experiments, and no app version management beyond listing. These missing lifecycle operations create workflow dead ends.