The App Store Connect MCP that does the work
Every other App Store Connect MCP hands your agent 90 raw API endpoints and wishes it luck. Lance is one hosted server, no local setup, and a real operator on a real Mac that carries tasks to done: listings, screenshots, TestFlight, in-app purchases, review.
npx add-mcp https://api.lance.app/mcpThat is the whole install: your client opens a browser, you sign in, done. No API keys to copy. Works with Cursor, Claude Code, Codex, and any client that speaks MCP over HTTP.
Try these prompts
Once connected, these are real asks your agent can delegate today:
- Get my app ready to submit. Bundle id is com.example.app.
- Why was my app rejected? Read the rejection and fix it.
- Create a $4.99 monthly subscription with a 7 day trial.
- Generate an icon and App Store screenshots from my repo.
- What's the live status of version 1.2 in App Store Connect?
Status reads answer in seconds. Bigger tasks run in the background on the operator's Mac while your agent keeps coding.
Why hosted beats another API wrapper
The open source ASC MCPs are API wrappers: your agent gets tool number 47 of 293 and has to figure out App Store Connect's rules itself, spending your tokens while it learns. You also hold the .p8 key locally and hope nothing in your agent's context ever leaks it. Lance inverts that:
An operator, not endpoints
You delegate outcomes in plain language. The operator knows App Store Connect's write semantics: how listings, IAP metadata, and review submissions actually fit together.
Credentials never enter your agent's context
Your App Store Connect keys and Apple session live with the operator on its Mac. Your agent just signs in with OAuth, and you can revoke its access any time. That is the entire blast radius.
It can actually build
Point it at a git repo and it builds, signs, and uploads to TestFlight on real Apple hardware. No Xcode on your machine, no certificates to babysit.
Submission stays consent gated
Lance drives your app to the point of submission and stops. It presses Submit for review only when you say so.
How it works
- 1
Install the MCP: one command, above.
- 2
Connect App Store Connect: authorize once in the Lance dashboard. 500 free credits land on your org.
- 3
Delegate: your agent asks in plain language; the operator works in the background and reports back.
Works with your client
- Cursor: one click deeplink or .cursor/mcp.json, config on the docs page
- Claude Code: one terminal command, full walkthrough in Claude Code to the App Store
- Codex, Windsurf, anything MCP: same URL, same bearer header. Building a fuller setup? See the iOS agent stack
FAQ
Is this free?
Yes to start: connecting your App Store Connect account includes 500 credits, enough to take a first app from repo to ready for submission. No credit card required.
Do I need a Mac or Xcode?
No. Builds run on the operator's Apple hardware. You need an Apple Developer Program membership ($99 per year, paid to Apple). Not enrolled yet? Start with our enrollment guide.
What happens to my Apple credentials?
They stay with the operator. Your coding agent signs in to Lance with OAuth in the browser (no API keys to copy), and you can revoke its access any time. It never sees your ASC API keys, .p8 files, or Apple session.
Can it fix a rejection?
Yes. It reads the rejection in Resolution Center, diagnoses the guideline, patches the listing or review notes, and resubmits. That is the loop most people pay $199 and up rescue services for.
What about the open source App Store Connect MCPs?
They are fine if you want raw API access and enjoy managing .p8 files. If you want the App Store handled, that is Lance.
Not enrolled in the Apple Developer Program yet? Start with our enrollment guide.
Your agent builds the app. Lance ships it.