Drive App Store Connect from any AI agent.

What you can do with it

Anything that's in App Store Connect's REST API — and a few things that aren't (chunked screenshot upload, "What's New" generated from git commits, AI-translated metadata across all locales, build attach-and-submit flow). Here's the surface area, grouped:

Build upload (which Apple ships through Transporter, not REST) is wrapped by upload_binary — agents can submit .ipa / .pkg files end-to-end. Only create_app (which Apple still gates to the App Store Connect web UI) returns an unsupported-feature note pointing the agent there.

Two ways to plug it in

Option 1 — Standalone MCP binary (no Mac app needed)

If you only want agent access — no GUI — install the standalone server. Talks JSON-RPC 2.0 over stdio. Your ASC API key lives in ~/.asc-credentials.json; the agent never sees it.

# Build & install
git clone https://github.com/williamjiamin/SimpleAppShipper.git
cd SimpleAppShipper/SimpleAppShipperMCP
swift build -c release
sudo cp .build/release/SimpleAppShipperMCP /usr/local/bin/

# Drop your ASC key in place
mkdir -p ~/.asc-credentials
cat > ~/.asc-credentials/config.json <<EOF
{
  "keyID":    "XXXXXXXXXX",
  "issuerID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "privateKeyPath": "/path/to/AuthKey_XXXXXXXXXX.p8"
}
EOF

Option 2 — Use the Mac app's embedded server

The Simple App Shipper Mac app runs the same MCP protocol on localhost:29117 by default. Open the app once to set up your ASC credentials, toggle "Agent API server" on in the Terminal panel, and any agent on the same machine can drive it. The app's Agent Activity Feed shows every call as it happens — pause, resume, audit.

Connect your client

Pick whichever you use day-to-day. All of them speak MCP.

Claude Code config

{
  "mcpServers": {
    "simple-app-shipper": {
      "command": "/usr/local/bin/SimpleAppShipperMCP",
      "args": [],
      "env": { "ASC_CREDENTIALS": "~/.asc-credentials/config.json" }
    }
  }
}

Cursor config

{
  "mcpServers": {
    "simple-app-shipper": {
      "command": "/usr/local/bin/SimpleAppShipperMCP"
    }
  }
}

Codex (TOML)

# ~/.codex/config.toml
[mcp_servers.simple-app-shipper]
command = "/usr/local/bin/SimpleAppShipperMCP"

Real example prompts

The agent calls the right tools automatically. You don't memorize tool names — just say what you want.

Prep a release

› Bump my app's version to 2.4.0, write release notes from the
   last 14 commits, AI-translate "What's New" into every locale,
   attach build 47, and stage it for review (don't submit).

Audit a release

› For my app, list versions in review or rejected. For each,
   show the rejection reason, the contact info on the review
   detail, and any failed pre-submit checks.

A/B test an icon

› Create a PPO experiment named "icon-v3-test" at 80% traffic
   with my candidate icon vs the current default. Print the
   App Store Connect analytics URL when done.

Localize an entire listing

› Read my en-US version metadata, then translate the description,
   promotional text, what's new, and keywords into all 28 locales
   on this version. Save as drafts. Don't submit.

Safeguards

• Submit for Review still requires a human password set at app onboarding. The agent prepares everything and stops. You press Submit.
• Destructive deletes (apps, versions, builds, IAPs, screenshots) require the same password.
• Activity feed in the Mac app logs every tool call with method, params, status, duration. Pause or audit at any time.
• Localhost-only. The embedded server in the Mac app binds 127.0.0.1, never the LAN.
• Your credentials. Your ASC API key never leaves disk; the agent calls Apple's API through the server, not directly.

Get started

The Mac app + the MCP server come bundled in the Lifetime Beta license. One purchase, both surfaces, and every future update.