App Publish MCP server

English | 한국어 | 中文 | 日本語

app-publish-mcp

A unified MCP (Model Context Protocol) server for App Store Connect and Google Play Console. Manage app listings, screenshots, releases, reviews and submissions — all from your AI assistant.

Publishing Boundary

You provide a release-ready, correctly signed Android .aab / .apk or Apple .ipa. The MCP handles supported store-side work from upload through metadata, testing, review submission, and release. It does not compile the app, own signing keys, or replace Xcode, Gradle, or CI.

The first release of a new app still requires manual setup in App Store Connect or Play Console, including developer enrollment, agreements, app records where required, API access, signing, tax and banking details, and policy, privacy, or content declarations. For an existing, fully configured Android app, a signed AAB is usually enough to let the MCP run the update workflow. A Google edit commit only commits the requested changes; store review, managed publishing, or a staged rollout can delay public availability.

When to Use

Use this MCP when you need to:

• "Update my app's App Store description and keywords" — modify version localizations, app info localizations
• "Upload new screenshots for iPhone 16 Pro" — create screenshot sets and upload images
• "Submit a new version for review" — create version, assign build, set review info, submit
• "Check the status of my app review" — list versions and check review state
• "Respond to a user review on Google Play" — list reviews and reply
• "Create a phased release on Google Play" — create edit, create release on a track, commit
• "Manage TestFlight beta testers" — create groups, invite testers, manage access
• "Set up in-app purchases" — create and manage IAPs and subscription groups on both platforms
• "Register a new device for development" — manage devices, certificates, and provisioning profiles

Features

Shortened. The full README is on GitHub.