App Store Connect Mcp
Let your agent read and update App Store Connect metadata, builds, and listing data without clicking through Apple's web console.
Overview
App Store Connect MCP is an MCP server for the Launch phase that lets coding agents interact with Apple's App Store Connect API for store and release tasks.
What is this MCP server?
- Python PyPI package `app-store-connect-mcp` (version 0.3.0) with stdio transport
- Authenticates with App Store Connect API Key ID, Issuer ID, and a .p8 private key path
- Supports optional defaults: `APP_STORE_APP_ID`, `APP_STORE_KEY_TYPE`, `APP_STORE_SCOPE`
- Exposes Apple's App Store Connect API to MCP clients for automated store workflows
- Team vs individual key type configurable via environment
- Server version 0.3.0 on PyPI identifier `app-store-connect-mcp`
- Three required environment variables for API authentication (key ID, issuer ID, private key path)
- stdio transport only in published package metadata
Community signal: 1 GitHub stars.
What problem does it solve?
Shipping and updating an iOS app in App Store Connect is repetitive portal work that agents cannot do unless you build custom API scripts yourself.
Who is it for?
Solo developers shipping Apple apps who already have App Store Connect API keys and want agent-assisted metadata, build, and listing workflows.
Skip if: Web-only or Android-only products with no App Store Connect account, or builders unwilling to manage .p8 keys and issuer IDs securely.
What do I get? / Deliverables
After MCP registration with valid Connect API credentials, your agent can call App Store Connect operations through stdio tools instead of manual dashboard steps.
- MCP-exposed App Store Connect API operations for your default or configured app
- Credential-driven authentication using team or individual key type settings
- Repeatable agent workflows for store-facing launch tasks
Recommended MCP Servers
Journey fit
App Store Connect is the operational surface for shipping and tuning iOS/macOS listings after the app exists; MCP access belongs in Launch when distribution and store presence matter. ASO and store listing operations are the primary shelf: API keys target the Connect API used for versions, metadata, and release management rather than in-IDE coding.
How it compares
Apple API MCP bridge, not an ASO copywriting skill or TestFlight replacement UI.
Common Questions / FAQ
Who is App Store Connect MCP for?
Indie iOS/macOS builders using AI agents who need programmatic access to App Store Connect during launch and listing updates.
When should I use App Store Connect MCP?
Use it in Launch when you are preparing releases, adjusting store metadata, or automating Connect tasks after the app build exists.
How do I add App Store Connect MCP to my agent?
Install the PyPI package, configure stdio MCP with `APP_STORE_KEY_ID`, `APP_STORE_ISSUER_ID`, and `APP_STORE_PRIVATE_KEY_PATH` to your .p8 file, then optionally set app ID and scope env vars.