shipstores — an MCP server for releasing apps to the App Store and Google Play from your AI agent

⚡ The gist in 5 seconds - shipstores — an MCP server that takes your app through App Store Connect and Google Play Console end to end: from eas build to the "Waiting for Review" status. - Connects to Claude or any MCP client; it uses the stores' public APIs, eas-cli, and console automation via a separate logged-in browser profile. - Publishing a mobile app takes roughly 40 manual steps across the two consoles, half of which have no public API. ### 🔍 What was found The FidelisMM/shipstores project is an MCP server that connects an agent to App Store Connect (public API), the Google Play Developer API, and Expo EAS (eas-cli). For operations without a public API — privacy labels, country availability, App Review responses, and the "App content" forms in Play — it uses console automation via a dedicated logged-in browser profile built on browser-harness. There are 60 tools in total. Some steps are covered by APIs in both stores: build upload, versions, listing, screenshots, age rating, categories, price, and URLs. Subscriptions and in-app purchases, as well as reading a rejection and responding to App Review (with video; HEVC is converted to H.264), are Apple-only. Privacy labels and country availability go through Apple's internal console API, Data safety goes through the Play console, and the 11 "App content" forms only through automation. Neither store lets you create an app record via API: *_create_app_form opens the required page in the logged-in browser and returns the exact values to fill in. Everything else is automated. ### 💡 Why it matters Agents can write an app but stumble at the store — and that's exactly the gap this project closes. The tool list is short (60), and tools that publish or submit for review explicitly say so in their descriptions, so the agent will ask before acting. The authors directly compare the solution with app-publish-mcp and mobile-release-mcp: those cover public APIs well, while shipstores focuses on API-less steps that are usually done by hand. ### 🧩 Context The authors built shipstores because publishing was always the slowest part of shipping an app, and every quirk described in the repo cost at least one rejected build. Requirements: Python 3.12+, uv, an App Store Connect API key and/or a Google Play service account, and for iOS uploads, Xcode command line tools (xcrun altool). It's installed into Claude Code with the command claude mcp add shipstores … uvx shipstores: uvx pulls the package from PyPI. The agent is then asked to run store_doctor — it verifies both sets of credentials with real calls and detects the Apple Team ID. The SHIPSTORES_TOOLSETS variable (apple, play, eas; core diagnostics is always enabled, all groups by default) limits the tool set; the same is configured in ~/.config/shipstores/config.toml. Console features are optional and require a one-time login via uvx --from shipstores python -m shipstores.browser login with 2FA; they rely on undocumented console endpoints — the same family of…

🔗 Read on github.com