Skip to content
CNTECH

Open source

The tools we use to ship.

The tooling we use to release our own apps, published on npm under the MIT license. Two Model Context Protocol servers that let an AI agent like Claude Code or Codex work with the App Store and Google Play through their official APIs.

App Store MCP

38 tools · MIT

App Store Connect API

Manage App Store Connect releases from an AI agent: upload an IPA, edit metadata and screenshots, run TestFlight groups, reply to reviews, and submit a version for review.

  • Builds & IPA upload
  • Metadata
  • Screenshots
  • TestFlight
  • Reviews
  • Submission & release
npx -y @cntechio-dev/app-store-connect-mcp

Play Store MCP

22 tools · MIT

Google Play Developer API

Manage Google Play releases from an AI agent: upload an AAB, stage and validate a track release inside an app edit, update store listings and testers, and reply to reviews.

  • AAB upload
  • Track releases
  • Store listings
  • Testers
  • Reviews
  • Internal sharing
npx -y @cntechio-dev/play-store-mcp

How they're built

Safe to hand to an agent.

Official APIs only

Both servers call the App Store Connect API and the Google Play Developer API directly. Nothing scrapes a console.

Changes are labelled

Every tool that publishes, uploads, or changes store state says so in its description, so the agent and the person approving it can tell a read from a write.

Publishing needs a yes

On Google Play, committing an edit requires an explicit confirmPublish flag. An agent can stage and validate a release without shipping it.