Cursor · App Store Connect

Read and reply to App Store reviews from Cursor

Ask Cursor what users are complaining about this week. MetaRun pulls the reviews, finds the recurring themes, and every reply Cursor drafts is shown to you before it's posted under your app.

Start Free Trial See pricing →

Setup checked October 2026 against Cursor MCP docs, Cursor CLI

01 · Uplink

Connect Cursor once

01 · Add to ~/.cursor/mcp.json (or .cursor/mcp.json for one project)

{
  "mcpServers": {
    "metarun": {
      "url": "https://metarun.dev/api/mcp"
    }
  }
}

02 · Or use the install link

Opens Cursor with the server filled in.

https://cursor.com/link/mcp/install?name=metarun&config=eyJ1cmwiOiJodHRwczovL21ldGFydW4uZGV2L2FwaS9tY3AifQ%3D%3D

03 · Sign in

When Cursor connects, MetaRun opens in your browser. Pick read-only or read and change, and you're back in the editor with the tools listed under MCP.

Prefer a personal access token (scripts, CI)?

Use a token instead

Mint a personal access token in MetaRun under Settings, MCP. It's shown once and can be revoked any time. Cursor reads ${env:METARUN_TOKEN} from your environment. Some Cursor versions start the browser sign-in even when a header is set; if that happens, signing in works the same.

{
  "mcpServers": {
    "metarun": {
      "url": "https://metarun.dev/api/mcp",
      "headers": { "Authorization": "Bearer ${env:METARUN_TOKEN}" }
    }
  }
}

02 · Briefing

What Cursor handles here

Reviews arrive per storefront, in every language, and App Store Connect shows them one at a time. Answering the ones that matter (the bug report with one star, the feature request that keeps coming back) gets pushed to someday.

For a coding agent this is useful in a second way: the complaint and the code are in the same session. Cursor can read a review about a crash, look at the code path, and draft a reply that says the fix is in 2.4.1.

03 · Preflight

Before you start

An API key with the Admin or Customer Support role, to reply.
A decision on tone, and on what you're willing to promise in public.
For crash complaints: the code or crash logs to check against.

04 · Execution

How it runs

01
Pull and sort
Cursor reads recent reviews and sorts them by what needs an answer: low ratings with specific complaints first.
02
Find the themes
aso_mine_reviews groups complaints and praise without an extra model call, and lists words users use that your listing doesn't.
03
Draft replies
The agent drafts. Each reply is a preview showing the review and the exact text that will appear under it.
04
Post on approval
The apply posts the reply. It's public as soon as Apple processes it, so this is the step to read carefully.

05 · Session

An example session in Cursor

Which reviews mention the widget, and what do they say?

apple_list_reviewsThis week's reviews, lowest rating first.
aso_mine_reviewsTop complaint theme: sync on iPad. Top praise: the widget.
apple_preview_respond_to_reviewPreview: the reply, exactly as it will appear under the review.
Cursor asks before running apple_apply_respond_to_review. You read the preview above and approve.
apple_apply_respond_to_reviewPosted. Public once Apple processes it.

Illustrative: your apps, versions and numbers will differ. The tool names and their order are real.

06 · Tools

The MetaRun tools Cursor calls

Tool	What it does
apple_list_reviewsread	Customer reviews with rating, territory, text and any existing reply.
apple_get_review_summaryread	Apple's AI summary of your reviews, the one shown on the product page.
aso_mine_reviewsread	Praise and complaint themes, plus keywords users use that your listing doesn't.
aso_get_territory_ratingsread	Star ratings per storefront and the worldwide average.
apple_preview_respond_to_reviewpreview + apply	Preview a public reply, or an edit to an existing one.
apple_preview_delete_review_responsepreview + apply	Remove a reply.

Each preview has an apply twin (the same name with apply instead of preview) that only runs with the confirm token from a fresh preview, and refuses if App Store Connect changed in between. MetaRun tools save to your MetaRun workspace only (studio projects, tracked keywords), never to Apple.

07 · Apple rules

What Apple enforces, and how MetaRun handles it

Replies are public

A developer response appears under the review on the App Store. Each review has one response; replying again replaces it.

The key needs the right role

Responding needs an App Store Connect API key with the Admin or Customer Support role. A key with a narrower role reads reviews but can't reply.

Ratings without text can't be answered

Only written reviews take a response. Star-only ratings show up in averages, not in the review list.

No ratings endpoint in the API

Apple's API has no per-storefront ratings call. MetaRun reads ratings from the public store lookup instead, so the numbers match what shoppers see.

08 · Comms

What to ask Cursor

Ask Cursor: Which reviews mention the widget, and what do they say?
Ask Cursor: Draft a reply to the German review about pricing, in German.
Ask Cursor: List reviews that already have a reply that's older than the latest version.

09 · Unattended

Run it from a script with Cursor

The Cursor CLI runs one request without the editor with agent -p. Allow only the read tools the request needs in ~/.cursor/cli-config.json (Mcp(metarun:tool_name) rules), and keep MetaRun's apply tools out of that list.

Read-only check, safe to schedule

agent -p "Summarize the last 7 days of reviews for com.example.app: count by rating, the top three complaint themes, and reviews with no reply. Read only." --output-format json

Don't run it with --force for MetaRun: that approves every tool, applies included.

10 · Safety

How Cursor asks before a change

Cursor asks before each MCP tool call by default, following your Run Mode settings. Keep MetaRun's apply tools on ask: that prompt is the confirm step for every App Store change. In the Cursor CLI, allow rules live in ~/.cursor/cli-config.json in the form Mcp(server:tool), so you can allow MetaRun's read tools and leave the applies out.

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

11 · FAQ

Frequently asked questions

Will Cursor post replies on its own?

No. Each reply is a preview first and the apply needs your approval in Cursor. Replies are public, so this is one to keep on ask.

Can it reply in the reviewer's language?

Yes. Cursor writes the reply; MetaRun posts it under the review in whatever language you approved.

Can I edit or delete a reply later?

Yes. Replying again replaces the existing response, and apple_preview_delete_review_response removes it.

Why can't it see some ratings?

Star-only ratings have no text and no reply option. They count in your averages, which aso_get_territory_ratings reports per storefront.

How do I connect Cursor to App Store Connect?

Add https://metarun.dev/api/mcp to ~/.cursor/mcp.json (or use the install link) and sign in to MetaRun when Cursor opens your browser. After that, ask for "reply to reviews" in plain words and Cursor picks the MetaRun tools.

Does Cursor see my App Store Connect key?

No. Your App Store Connect API key stays envelope-encrypted on MetaRun's servers and is decrypted per request. Cursor holds a MetaRun token that you can revoke in Settings at any time.

More with Cursor

Cursor

ASO keywords

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

Open

Cursor

Phased release

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

Open

Cursor

Release notes

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