Your AI Can Submit Apps to the App Store Now. No, Seriously.

I spent 45 minutes uploading screenshots to App Store Connect last Tuesday. Different sizes for every device. 6.7-inch, 6.5-inch, 5.5-inch — because apparently Apple thinks we still care about the iPhone 8 Plus. Then I had to do the same thing on Google Play. Different aspect ratios, different requirements, same soul-crushing repetition.

And that was just screenshots. I hadn't even touched the release notes, the build processing, the phased rollout config, or the seventeen other fields that App Store Connect demands before it lets you click "Submit for Review."

I'm done with it. I think you should be too.

The Dashboard Problem

Here's the thing nobody talks about: app store dashboards are some of the worst developer tools in existence. Not because they're broken — they work fine. They're just painfully manual.

App Store Connect has this beautiful habit of spreading a single release across about nine different tabs. You update your description here, your keywords there, your screenshots somewhere else, your in-app purchases in a completely different section. Google Play Console is marginally better, but "marginally better than App Store Connect" is not a compliment.

For indie devs and small teams, this overhead is brutal. You finally finish building your feature, you're excited, and then you spend the next hour clicking through dashboards and resizing PNGs. It kills momentum. It kills joy. It kills the part of your brain that actually enjoys making software.

And don't even get me started on TestFlight. The workflow of "upload build, wait for processing, add testers, write test notes, submit" is simple in theory and annoying in practice. Every. Single. Time.

Enter app-publish-mcp

So I found app-publish-mcp last week, and I'll be honest — I was skeptical. Another MCP server? Cool. But this one actually solves a real problem I have.

It's a Model Context Protocol server that gives your AI agent direct access to both the App Store Connect API and the Google Play Developer API. We're talking 91 tools. 56 for Apple, 35 for Google. One unified interface.

The setup is straightforward. Drop this into your MCP config:

{
  "mcpServers": {
    "app-publish": {
      "command": "node",
      "args": ["/path/to/app-publish-mcp/dist/index.js"],
      "env": {
        "APPLE_KEY_ID": "your-key-id",
        "APPLE_ISSUER_ID": "your-issuer-id",
        "APPLE_P8_PATH": "/path/to/AuthKey.p8",
        "GOOGLE_SERVICE_ACCOUNT_PATH": "/path/to/service-account.json"
      }
    }
  }
}

You'll need to clone the repo and build it first (npm install && npm run build), then point the config at the built file. Apple needs the App Store Connect API key (you generate this in Users and Access), and Google needs a service account JSON with the right Play Console permissions. Standard API auth stuff — nothing exotic.

What It Actually Looks Like

Here's where it gets interesting. Instead of clicking through dashboards, you just... talk.

Me: Submit version 2.3.1 of Tempo to TestFlight. Release notes:
    "Fixed the sync bug that was driving everyone insane. Also improved
    offline playback performance by ~40%. Please test the new playlist
    sharing flow — it's behind the share button on the Now Playing screen."

Claude: I'll handle the TestFlight submission for Tempo v2.3.1. Let me:
    1. Look up the app and latest build...
    2. Found build 2.3.1 (build 847), processed and ready.
    3. Creating beta app review submission with your release notes...
    4. Adding to external testing group "Beta Testers"...
    Done. Build 2.3.1 is now submitted for beta review.
    142 testers in "Beta Testers" will get it once approved.

No dashboard. No clicking. No context switching. You stay in your terminal, in your flow.

And it handles the weird stuff too. Need to create a new in-app purchase? Respond to an App Store review? Manage your TestFlight beta groups? All of it is exposed through the tools. The agent figures out which API calls to chain together.

Here's another one I use constantly — updating store metadata across both platforms at once:

Me: Update the app description for both iOS and Android. New first paragraph:
    "Tempo syncs your music library across every device, instantly.
    No cloud storage limits. No subscription required."
    Keep everything else the same.

Claude: Updating descriptions for both platforms...
    - App Store Connect: Updated en-US description for v2.3.1
    - Google Play Console: Updated en-US listing, default language
    Both store listings now have the new opening paragraph.

That used to be two dashboards, four clicks minimum, and a lot of copy-pasting. Now it's one sentence.

Why This Actually Matters

I'm not going to pretend this is revolutionary technology. It's an API wrapper with an MCP interface. But the right API wrapper at the right abstraction layer can change your entire workflow.

For indie devs, this is huge. If you're a one-person shop shipping on both platforms, the operational overhead of app publishing is a real tax on your time. Cutting that from 45 minutes to 2 minutes of conversation isn't a nice-to-have — it's the difference between shipping weekly and shipping monthly.

For small teams, it means your mobile lead doesn't have to be the designated "dashboard person" anymore. Anyone with terminal access and the right API keys can push a release, and the AI handles the platform-specific details.

For CI/CD pipelines, this is the obvious next step after Fastlane. You're already automating your builds — why not automate the submission too? Hook an MCP-capable agent into your release pipeline and let it handle the App Store Connect dance.

The Honest Take

Is it perfect? No. There are edge cases where you'll still need the dashboard — complex in-app purchase configurations, resolving specific review rejections that need manual screenshots. Apple's review process is still Apple's review process, and no amount of automation will make them approve your app faster.

The Google Play side is a bit thinner at 35 tools versus Apple's 56, which makes sense given that Google's API surface is simpler to begin with. But the core workflows — listing updates, release management, track promotion — are all covered.

The real unlock here isn't any single tool. It's the cumulative effect of never opening App Store Connect again for routine operations. Every minute you don't spend in a dashboard is a minute you spend building the actual product.

I pushed two releases last week without opening a browser. That's not a flex — it's just how it should have always worked. The app stores gave us APIs years ago. It just took MCP to make them actually usable from where developers live: the terminal.

Try it. Your future self, the one who doesn't have to resize screenshots at 11 PM before a release, will thank you.

---

Alan West is a full-stack developer based in San Francisco who ships too many side projects and complains about developer tools on the internet. Find him on GitHub or don't — he'll be in his terminal either way.