How to publish to the App Store and Google Play from Claude or ChatGPT (2026)

Version française →

AI assistants can now do store work: rewrite a listing in eight languages, answer the critical reviews from last week, upload a build and submit it for review. They do it through an MCP server, a connector that exposes the App Store Connect and Google Play operations as tools the assistant can call.

This guide uses OneStore's MCP server, because it is the one we build. The same ideas apply to any MCP server for the stores, and the MCP server comparison covers the open-source alternative.

1. Connect your assistant

OneStore's server is a remote HTTP server with OAuth: https://www.onestore.so/api/mcp. There is nothing to install for Claude or ChatGPT: add it as a custom connector, sign in, done.

For Cursor, Claude Code and Codex, an installer adds the server to the client's configuration and installs the use-onestore skill (Node.js 20 or later):

curl -fsSL https://www.onestore.so/mcp/onestore.mjs -o onestore.mjs
node onestore.mjs setup --client cursor --origin https://www.onestore.so

Replace cursor with your client. The installer stores no token; your client handles OAuth. To check it worked, ask: "Check my OneStore connection and list my accessible apps." The assistant should call get_connection and list_apps.

2. Choose what the assistant may do

At sign-in you pick a workspace, the apps and the platforms the connection can see. Access to future apps is opt-in, and each connection has a duration (up to 90 days, or no expiry) and can be revoked in settings. Then you choose capabilities:

Separately, autonomy sets what the assistant may run on its own: prepare allows drafts, uploads and data refreshes; test adds test distribution; full allows every action you already granted. Anything beyond that returns a pending operation with an approval link, and OneStore refuses to run it until you approve. The default is read-only, with every store action waiting for you.

3. What you can ask

• "Which 1 and 2-star reviews on both stores have no reply yet? Draft replies in each reviewer's language."
• "Translate the iOS listing into German, Spanish and Japanese, within each store's limits, and show me before pushing."
• "Compare installs for version 2.3 and 2.4 over their first 14 days."
• "Are there store alerts or broken app links on any of my apps?"
• "Release 2.5.0: upload the build I just made, attach it, and submit it to Apple. Put the Android build on production at 20%."

4. A release, end to end

1. Build on your side. The assistant identifies the app, the version, the signing setup and the target track, then builds with your project's tools. iOS needs macOS, Xcode and your signing setup.
2. Upload. It prepares an upload, sends the bytes directly to storage, then finalizes the file in OneStore. Limits: 500 MiB for an .ipa, 200 MiB for an .aab.
3. Send to the store. A separate action. For Apple, OneStore's macOS worker uploads the build with xcrun altool; the assistant follows processing and attaches the build to the version. For Google, the track and status decide distribution.
4. Submit. Submission follows the connection's rights and approvals. Before an Apple submission, OneStore checks the version (screenshots, export compliance, age rating, What's New in every language) and asks once for any declaration it can't infer.
5. Report. The assistant reports what it observes: uploaded, processing, in review or published. An upload is not a release; Apple and Google agreements, declarations and review still apply.

What it can't do (yet)

• Build your app on OneStore's servers. Builds stay on your machine or your CI.
• Create the app in App Store Connect or Play Console. Neither store's API allows it.
• TestFlight group distribution, Apple's phased release, and the final release of an approved manual Apple version are not exposed.
• Publish a Google Play release held by managed publishing. The Play API has no access to it.

Why approvals matter

Store writes are public and hard to undo. An assistant that can submit a release should not be able to do it by accident. With OneStore, the limit lives on the server: the connection's scope and autonomy decide, and a pending operation waits for a human in OneStore no matter which client sent it. Store keys stay in OneStore's encrypted vault (AES-256-GCM); the assistant only holds an OAuth token you can revoke.

Start on the MCP page or read the MCP documentation.

FAQs