v0.2.0 — toolsets

Toolsets: expose only the tools you need

shipstores has 60 tools, and every tool costs context in your agent. If you only ship to one store, you can now pick the groups you want:

SHIPSTORES_TOOLSETS=apple,eas   # iOS + Expo only (40 tools)

Or in ~/.config/shipstores/config.toml:

[server]
toolsets = ["play"]

Groups: apple, play, eas. Core diagnostics (store_doctor and friends) are always on, and the default is still everything.

This is the first community contribution to shipstores, by @berkay-byte in #11, about an hour after the issue was opened. Thank you!

Also

• CI now runs the unit tests.

Upgrade: uvx shipstores@latest, or just restart your MCP client: uvx picks up the new version.

v0.1.0 — first public release

First public release. An MCP server that lets AI agents (Claude Code, Cursor, any MCP client) ship iOS and Android apps: App Store Connect, Google Play Console and Expo EAS.

Install

uvx shipstores

Then add it to your MCP client and run store_doctor. Full setup in the README.

What's in it (60 tools)

• App Store Connect: builds, versions, listing, screenshots, subscriptions, age rating, categories, price, availability, privacy label, review submission and cancellation, TestFlight internal invites.
• App Review: read rejection messages, reply with attachments and resubmit the rejected version.
• Google Play: bundles, tracks, listing, screenshots, contact details, signing, App content declarations and data safety.
• Expo/EAS: start, poll, download and submit builds.

Known limits

Most tools use the official APIs. Privacy labels, availability, App Review replies and Play "App content" forms go through the store consoles' web endpoints, which Apple or Google can change without notice. Some write tools in that group have not run against production yet. If one breaks for you, please open an issue.

Want to help?

There are good first issues open: console translations (es, de, fr), unit tests, docs for Flutter and native projects.