App Store Connect MCP Server
Related Servers
Alternatives to App Store Connect MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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.52228 npm23MIT
- 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
- 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.63228 npm2MIT
- 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-
- AlicenseNot gradedqualityDmaintenanceMCP 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 60 tools
Most specialized tools target distinct resources and actions, but the generic read_api/write_api tools overlap with nearly every specific list/get/create/update tool. upload_build and upload_reserved_asset also overlap for build-file uploads. Descriptions help clarify intent, but an agent still faces real selection ambiguity.
Tool names consistently use snake_case with a verb-first noun pattern (list_apps, get_build, create_iap, set_subscription_price, submit_for_review). Even the generic API tools follow the same convention. There is no mixed casing or chaotic verb style.
At 60 tools, the surface is far beyond a well-scoped set and exceeds the rubric's 50+ extreme threshold. While App Store Connect is a broad domain, this many tools creates substantial selection overhead and increases the chance of choosing the wrong operation.
Core App Store Connect workflows are well covered: apps, versions, builds, TestFlight, review submission, IAPs, subscriptions, pricing, experiments, custom product pages and localizations. Some gaps remain, such as app-level metadata beyond description/whats-new/keywords and user/provisioning operations, but the search/read/write API tools provide a general escape hatch.