Let your agent run your ASO

It researches the market, writes your title, subtitle and keywords, and ships them to App Store Connect. Nothing changes at Apple until you approve it.

Where will you be using it?

What are you connecting?

In the terminal, from any folder.

1

Run this once.

Terminal

claude mcp add --transport http aso-studio https://asostudio.app/mcp

2
Start Claude Code, run /mcp, and choose to authenticate.
3
Sign in with Apple and approve the connection in the browser it opens.

Run /mcp. ASO Studio should read as connected rather than needing authentication.

Step by step for one tool: Claude Code · Claude · ChatGPT · Codex · Cursor

What it can do

Write your title, subtitle and keyword field, and ship them to App Store Connect
Create and update your listing in other languages
Run your Apple Search Ads: new campaigns, keywords, bids and pauses
Plan your next release, ship it, and see how it did thirty days later
Read your sales, keywords, rankings and history
Research the live App Store: who does what you do, and what their users ask for
Track and untrack keywords and apps, tag them, write notes
Answer the judgements ASO Studio would otherwise need an AI key for

It is the same set of tools the assistant inside the app uses, against the same workspace. A change made from your terminal appears in the window in front of you. App Store Connect and Apple Search Ads use the keys you connect in ASO Studio, and the agent never sees them.

What it will not do

Anything you switched off when you connected it
Spend money without showing you the amount
Write to the App Store without showing you every field, before and after
Work while ASO Studio is closed, because the work happens there

Every tool starts switched on when you connect it, and you can turn any of them off. Whatever you leave on, a change to your App Store listing or a deletion asks every time: in your own tool if it can ask, and in the ASO Studio window if it cannot. What we do and do not carry is in the privacy policy.

From connection to research

Research your app with Claude, ChatGPT, or another MCP client

Connect a compatible AI assistant to ASO Studio and ask it to investigate your App Store market using the app's research. It can inspect competitors, read reviews, explore and measure search terms, and read your saved release plans. Your Mac must be awake with ASO Studio running, and the connection needs permission for the actions you request.

An example research request

Research my app in the US App Store. Find competitors that solve the same job, read recent reviews for recurring requests and complaints, and compare relevant search terms. Separate observations from estimates, name the source apps and storefront, and suggest one next step. Read only for now; do not change my listing or campaigns.

Name the app and market

Give the assistant the App Store link or ID and the storefront. Ask it to confirm which app and workspace it is using before starting the research.

Ask for evidence, then interpretation

Have it read competitors, recent reviews, and measured terms. Ask for source apps, original review wording, measurement dates where available, and gaps in coverage. The assistant's explanation should be distinguishable from the data ASO Studio returned.

Review a specific next step

Ask it to explain a product opportunity or listing change using the findings. It can read saved plans and, with the relevant permissions and App Store Connect setup, help apply supported metadata changes after a preview. Review the actual diff before authorizing a write.

The result should connect a recommendation to the observations behind it: which apps were compared, what users asked for, which searches were measured, and what remains uncertain. This is an example request, not a precomputed report or a guarantee that every app has enough public evidence.

The research workspace lives on your Mac. Information returned to a connected assistant is shared with that assistant, so its own data handling also applies. A local MCP connection describes the transport; it does not mean a hosted model runs locally.