Claude Code · Anthropic

App Store Connect, inside Claude Code

Add MetaRun's MCP server with one command and sign in once in your browser. Claude Code can then attach builds, submit for review, translate your listing and reprice 175 storefronts from the same session where you wrote the code. Your Apple key stays on MetaRun's servers.

Setup checked October 2026 against Claude Code MCP docs, permissions

01 · Uplink

Connect Claude Code to MetaRun

01 · Add the server

Run it in any terminal. --scope user makes MetaRun available in every project; leave it out to limit it to the current one.

claude mcp add --transport http --scope user metarun https://metarun.dev/api/mcp

02 · Sign in

In a Claude Code session, run /mcp, choose metarun and authenticate. MetaRun opens in your browser, where you pick read-only or read and change. From a plain shell, claude mcp login metarun does the same.

/mcp

03 · Optional: add the skills too

The MetaRun plug-in bundles the same server with six mission skills (release handoff, worldwide pricing, localization, review inbox, ASO audit, store media).

claude plugin marketplace add metarun/metarun-skills
claude plugin install metarun-skills@metarun
Prefer a personal access token (scripts, CI)?

Add the server with a token

Mint a personal access token in MetaRun under Settings, MCP. It's shown once and can be revoked any time.

claude mcp add --transport http --scope user metarun https://metarun.dev/api/mcp \
  --header "Authorization: Bearer $METARUN_TOKEN"

Or share it with your team in .mcp.json

Project scope writes .mcp.json at the repo root. Claude Code expands ${METARUN_TOKEN} from each person's environment, so the token itself is never committed.

{
  "mcpServers": {
    "metarun": {
      "type": "http",
      "url": "https://metarun.dev/api/mcp",
      "headers": { "Authorization": "Bearer ${METARUN_TOKEN}" }
    }
  }
}
02 · Capabilities

What Claude Code can do in App Store Connect

Each task has a guide: how the job works in App Store Connect, what Apple enforces, and the exact tools Claude Code calls through MetaRun.

Submit for review

Submit for review

Attach the build, clear export compliance, run the readiness sweep, submit.

Phased release

Phased release

Choose how an approved version goes out, then pause, resume or finish a phased rollout.

Release notes

Release notes

Write What's New from your changelog and stage it in every language.

Localize your listing

Localize your listing

Name, subtitle, keywords and description in every App Store language, limits checked.

Screenshots

Screenshots

Design, caption, translate and upload App Store screenshots from a prompt.

Price by country

Price by country

Reprice an app, IAP or subscription across 175 storefronts with PPP or Big Mac indexes.

Subscriptions and IAPs

Subscriptions and IAPs

Create subscription groups, subscriptions and in-app purchases with copy and prices.

Offers and offer codes

Offers and offer codes

Free trials, promotional offers, offer codes and win-back offers, set up by asking.

Reply to reviews

Reply to reviews

Triage App Store reviews, find the themes, and post replies you've approved.

TestFlight

TestFlight

Hand builds to tester groups, write What to Test, and read crash feedback.

ASO keywords

ASO keywords

Find keywords from App Store autocomplete, track ranks, and lint your metadata.

App Privacy and compliance

App Privacy and compliance

Turn your privacy manifests into App Privacy answers; set age rating and export compliance.

03 · Briefing

Why App Store work fits in Claude Code

Most of what App Store Connect asks for already exists in your repo. What's New is in CHANGELOG.md or the commit log. The terms your app uses in every language are in Localizable.xcstrings. Product ids are in the StoreKit configuration file, and App Privacy's answers follow from the PrivacyInfo.xcprivacy files your app and SDKs ship.

Claude Code can read all of that. MetaRun gives it the other half: the live state of your listing, versions, builds and prices, and tools that change them behind a preview. So the release that used to end with an hour in App Store Connect ends in the same terminal session.

04 · Briefing

Xcode's tools in the same session

Xcode ships its own MCP server for external agents. Turn on Allow external agents to use Xcode tools in Xcode's Intelligence settings, run claude mcp add --transport stdio xcode -- xcrun mcpbridge, and Claude Code can build and test through Xcode while MetaRun handles App Store Connect. One session builds the release, the other server ships it.

05 · Briefing

Claude Code, the Claude app, or the plug-in

Claude Code and the Claude app connect to the same MetaRun server with the same sign-in. The difference is context: Claude Code sees your repository, the Claude app sees the conversation. The plug-in is optional and adds six written workflows Claude Code can follow, such as finishing a release after the build uploads.

06 · Comms

Things to ask Claude Code

  • Ask Claude Code: What state is com.example.app in, and what blocks submitting 2.4?
  • Ask Claude Code: Write What's New for 2.4 from CHANGELOG.md and stage it in every language on the listing.
  • Ask Claude Code: Reprice the yearly plan with PPP from $39.99, keeping current subscribers on their price. Preview first.
  • Ask Claude Code: Pull this week's 1-star reviews and find the code path behind the most common complaint.
07 · Safety

How Claude Code asks before a change

Claude Code asks before every MCP tool call by default. You can allow a tool for the session or permanently; allow rules look like mcp__metarun__apple_list_versions for one tool, and mcp__metarun__* allows the whole server, applies included. Allowing reads and previews is reasonable. Leave the apply tools on ask: that prompt is the confirm step for every App Store change.

Unattended

claude -p runs one request with no interactive session. The browser sign-in can't complete inside -p, so sign in once interactively first, or configure the server with a personal access token in CI. Tools missing from --allowedTools are refused in -p mode.

Read-only check, safe to schedule

claude -p "List my apps and the review state of each one's latest version. Read only." \
  --allowedTools "mcp__metarun__apple_list_apps,mcp__metarun__apple_list_versions"

Only reads and previews are on that list, so nothing can reach App Store Connect unattended. Run applies in an interactive session where Claude Code can ask you.

Apple key stays on MetaRun, encryptedPreview before every writeRecorded, revertible from history
08 · FAQ

Frequently asked questions

Do I need an API key to connect Claude Code to App Store Connect?

No. Claude Code signs in to MetaRun through your browser and holds a MetaRun token that refreshes on its own. Your App Store Connect API key is uploaded once to MetaRun, where it stays encrypted. Personal access tokens are there for CI and scripts.

Which scope should I add MetaRun with?

User scope (--scope user) if you want it in every project. Local scope, the default, keeps it to one directory. Project scope writes .mcp.json so your team gets the same server; each person still signs in to their own MetaRun account.

Can Claude Code submit my app or change prices without asking?

Every change is a preview first, and the apply needs the preview's confirm token. Claude Code asks you before running the apply unless you've allowed that tool. Submitting for review also needs an explicit acknowledge.

Does it work in a team workspace?

Yes. A teammate signs in with their own account. They need the workspace owner's Agent access grant, and a read-only grant limits the connection to reads.

Which plans include agent access?

Pro ($39 a month) and Studio ($99 a month), and the 14-day free trial, which needs no card. Starter doesn't include agent access.

How many tools does Claude Code get?

All of them: the same registry that runs MetaRun's dashboard, across App Store Connect, pricing, the screenshot studio, ASO, answer-engine visibility and your app's data workspace.

Other agents

OpenAI

Codex

codex mcp add, a browser sign-in, and Codex can ship releases and edit your listing.

Anysphere

Cursor

Add the server URL, sign in, and Cursor's agent can run your App Store work from the editor.

Apple

Xcode

An Xcode 27 agent plug-in: the coding assistant builds the release, MetaRun ships it.

Anthropic

Claude

A custom connector in Claude: ask about your listing, stage changes, approve them in the chat.

Google

Gemini CLI

gemini mcp add or the MetaRun extension, then a browser sign-in.

All agents

Every way to connect

The full list: MCP clients, the ChatGPT app, the CLI and agent skills.

Agent access

14-day free trial with agent access. No credit card. Your Apple key stays encrypted on MetaRun.