Getting started

Ploa takes your app to the App Store and Google Play through MCP, from your coding agent: Claude Code, Cursor, Codex, VS Code with Copilot and others. There are three steps, and you do the first one once.

1. Connect Ploa to your agent

   In your app's folder, on the computer where you work:

   curl -fsSL https://ploa.dev/install.sh | sh
   ploa login
   ploa mcp install

   The first line installs Ploa's command line tool, ploa login opens Ploa in the browser to confirm a code, and ploa mcp install adds Ploa to Claude Code, Cursor, VS Code (Copilot) and Codex. Restart the agent. On Windows, the first line in PowerShell is irm https://ploa.dev/install.ps1 | iex (see Working from Windows).

   Agent on the web, like Claude in the browser? Add https://ploa.dev/mcp as a connector and approve it on Ploa instead. Choose Drafts, builds and requests: it writes and builds, and asks you for App Review and production, which you approve. It never changes the stores directly. Every agent, npx and settings by hand: Connect your agent.

2. Ask your agent to ship the app

   In plain words:

   Ship this app to the App Store and Google Play with Ploa.

   The agent asks how you want it to work (on its own, or asking you before each review and release), shows you the stages, and does its part: links the app, checks the project, writes the store page from your code, makes the screenshots, builds, signs and sends to TestFlight and Google Play internal testing. Steps only you can do in a store come to you one at a time, each with its exact link. More requests that work well: What to ask.

3. Approve the rest yourself

   App Review, production, prices and testers who get an email wait for your OK, on the dashboard or from a notification on your phone. Builds reach testers on their own. Everything is recorded under the agent's name. How it works and how to change it: Access and approvals.

What you need

• A Ploa account. Sign up at ploa.dev/join; ploa login also offers it. Every feature is on the free plan.
• A developer account at Apple, at Google Play, or both.
• An app for iOS, Android or both: Expo, React Native, Flutter, Capacitor, Swift or Kotlin. Anything else ships as a built .ipa or .aab. See Builds and signing.
• A coding agent that speaks MCP, and Node 24 or newer on the computer for ploa.

Builds run where it suits you: on your Mac, on GitHub or in your own Google Cloud. The agent asks you, and you don't need a Mac for Android.

What only you do, the first time

Apple and Google keep a few steps for people. The agent tells you each one when it's due, with the link, and Ploa checks it off once it sees it done:

• Connect the stores to Ploa: an App Store Connect API key, and an invite of Ploa's email to Play Console. See Stores and apps.
• Create the app in each store. Apple has no API for it; Ploa registers the bundle ID first, so you only pick it.
• Answer the forms with no API: Apple's App Privacy and most of Play Console's App content. The agent works out the answers from your code and says what to tick; Ploa sends Data safety to Google for you.
• Decide what's yours to decide: the store page's languages, countries, price, who the app is for, and the contacts. The agent asks and waits.

After the first release

Each new version is one request: Send a new version to testers, then Submit it for App Review or Promote it to production, and you approve. Ploa hears App Review's answer within minutes and tells you.

Where next