OneStore

Manage App Store and Google Play apps from your assistant: listings, screenshots, builds, releases, reviews and metrics. Remote server, OAuth; read-only by default, store writes wait for approval.

Hosted MCP Server

npx add-mcp 'https://www.onestore.so/api/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Your AI ships. You stay in control.

Connect Claude, Cursor, ChatGPT or Codex to OneStore: listings, builds, releases and reviews on the App Store and Google Play, from a chat. You choose the apps, the permissions and what it may do on its own.

Works with

Your cursor has a reflection in the other store. Click a listing or the top bar.Tap a listing or the top bar: Clawd handles both sides.

43 tools. All of OneStore, from your assistant.

Every tool stays within the connection’s permissions, and a store action waits for your approval until you grant more autonomy.

Listings

Read, write, translate and publish the text of every language, within each store’s character limits.

“Translate the listing into German and Japanese, then publish it.”

list_listings create_listing update_listing push_listings delete_listing

Screenshots

Upload HD screenshots, OneStore produces every store’s sizes. Reorder or remove them.

“Replace the screenshots with the ones in the screens folder.”

list_assets list_asset_formats prepare_asset_upload finalize_asset_upload reorder_assets delete_asset

Builds

Upload the.ipa or.aab built on your machine, push it to the store and attach it to the version.

“Build the Android release and send it to internal testing.”

prepare_upload finalize_upload list_bundles update_bundle push_bundle attach_build cancel_upload delete_bundle

Releases

Create the version, write the notes, check nothing is missing, submit, promote, roll out gradually on Google Play.

“Ship 1.6.0 to the App Store and Google Play.”

list_releases create_apple_release update_release push_release_notes check_apple_release submit_release cancel_review promote_track set_rollout

Reviews

Read reviews from both stores, spot the critical ones and reply.

“Reply to this week’s negative reviews, in a calm tone.”

list_reviews reply_review

Apps and stats

Installs, revenue and subscriptions, sync with the stores, each app’s settings.

“Is 1.6.0 doing better than 1.5?”

list_apps get_app get_app_metrics sync_app get_sync_job update_app delete_app

Control

See its permissions, read OneStore guides, prepare an action without running it, follow an operation to the end.

“Prepare the submission, but wait for my approval.”

get_connection get_guide list_actions plan_action execute_operation get_operation

Your AI, your apps

Read your data, prepare listings and screenshots, upload builds and manage releases from your assistant. Each connection has its own apps, platforms, permissions and autonomy.

Build locally, deliver through OneStore

Your agent builds with the project and tools on your computer, then transfers the.ipa or.aab to OneStore. A chat without access to your computer manages existing uploads.

Stay in control of publishing

Approve every action, autonomous preparation, autonomous test distribution or full autonomy within the granted permissions. Approvals happen in OneStore with the action’s details, and your team’s permissions still apply.

Connect my assistant

MCP server URL (HTTP + OAuth)

https://www.onestore.so/api/mcp

Install the MCP and skill

Node.js 20 or later. Download the script, then run it for your selected assistant. It adds OneStore to the configuration and installs use-onestore for your local account.

curl -fsSL https://www.onestore.so/mcp/onestore.mjs -o onestore.mjs
node onestore.mjs setup --client cursor --origin https://www.onestore.so

View / download script

Open Cursor MCP settings and authenticate OneStore.

Run setup again to update. Edited files and other connections are preserved. Cursor/Claude Code also accept --scope project. To remove this installation:

node onestore.mjs uninstall --client cursor --origin https://www.onestore.so

Also revoke the connection in OneStore to invalidate its access. The installer stores no token; your client manages OAuth.

Verify the connection

After selecting your apps and permissions, ask: “Check my OneStore connection and list my accessible apps.” The assistant should use get_connection and list_apps.

Optional network diagnostic: node onestore.mjs doctor. This checks public OAuth discovery, not your account authentication.

Read the skill · Download the skill bundle

The server also accepts a OneStore key in clients supporting an Authorization header. Create it in settings and keep it in your client’s private storage.


How it works

  1. Connect your assistant

    Add the MCP server URL to Claude, Cursor, ChatGPT or Codex, or run the installer. The connection uses OAuth: your assistant never sees your password.
  2. Choose what it can do

    Workspace, apps, platforms, permissions (read, drafts, uploads, store, publish) and autonomy level. Each connection can be revoked at any time in settings.
  3. Ask

    Your assistant prepares listings, uploads builds and runs releases. An action that needs your approval opens in OneStore with its exact details.

Frequently asked questions

What is MCP?

The Model Context Protocol is an open standard that lets an AI assistant use external tools. OneStore’s MCP server gives it access to your listings, builds, releases and reviews on the App Store and Google Play, within the limits you set.

Can my assistant publish without my approval?

Only if you decide so. For each connection you choose: approve every action, autonomous preparation, autonomous test distribution or full autonomy within the granted permissions. Approvals happen in OneStore with the action’s details.

Are my App Store Connect and Google Play keys exposed?

No. The assistant goes through OneStore, which keeps your keys encrypted on the server. It never receives your credentials, only the result of the actions you allowed.

Can my assistant build my app?

Yes, if it has access to your computer (Cursor, Claude Code, Codex): it builds with your project’s tools, then uploads the.ipa or.aab to OneStore. A web chat manages builds already uploaded, without building.

Which assistants are compatible?

Any MCP client that supports HTTP transport and OAuth: Claude, Claude Code, Cursor, Codex, and ChatGPT depending on your plan. Clients that accept an Authorization header can also use a OneStore key created in settings.