shipstores
shipstores automates mobile app publishing end to end for App Store Connect, Google Play, and Expo EAS.
Diagnose credentials, browser sessions, and audit listings for identity leaks.
Apple: register bundle IDs; assist app creation; upload/list builds; create/manage versions; edit listing/app info; set age rating, price, availability, and privacy labels; upload screenshots; read/reply to App Review; resubmit/cancel submissions; manage TestFlight invites and subscriptions.
Google Play: assist app creation; inspect tracks; upload bundles; promote releases; edit listings; upload/list screenshots; manage contact details; get signing SHA-1; check submission status and send for review; complete App content declarations and Data safety via CSV.
Expo/EAS: list, start, poll, download builds, and submit them to stores.
Publishing/submitting tools are marked as external actions so the agent confirms before acting.
Drives App Store Connect end to end: manages builds, versions, store listings, screenshots, app info, age ratings, pricing, availability, privacy labels, review details, subscriptions, and App Review messages, replies, and submissions.
Integrates with Expo EAS to start, list, poll, download, and submit iOS and Android builds as part of the store publishing workflow.
Drives Google Play Console end to end: creates app records, uploads bundles, promotes releases, manages listings and screenshots, contact details, signing SHA1, submission status, App content declarations, and Data safety forms.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@shipstores submit the latest iOS build for App Review"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
shipstores drives App Store Connect and Google Play Console end to end — builds, store listings, screenshots, privacy labels, review submission and even replying to App Review — so Claude (or any MCP client) can take an app from eas build to "Waiting for Review" without you clicking through two consoles.
Built because publishing was always the slowest part of shipping an app. Every quirk documented below cost at least one rejected build to discover.
flowchart LR
A["🤖 Claude / any MCP client"] -->|"tools"| M["shipstores"]
M -->|"public API"| ASC["App Store Connect"]
M -->|"public API"| GP["Google Play Developer API"]
M -->|"eas-cli"| EAS["Expo EAS builds"]
M -.->|"console automation<br/>(dedicated browser profile)"| C["Privacy label · availability<br/>App Review replies · Play App content"]Why
Publishing a mobile app is ~40 manual steps across two consoles, half of which have no public API. AI agents can write your app, but they stall at the store. This server closes that gap:
App Store Connect | Google Play | |
Upload build, versions, listing, screenshots | ✅ API | ✅ API |
Subscriptions / in-app purchases | ✅ API | — |
Age rating, categories, price, URLs | ✅ API | ✅ API |
Privacy label & country availability | ✅ console's internal API | ✅ Data safety via console |
Read the rejection & reply to App Review (with video) | ✅ console | — |
"App content" declarations (11 forms, no API) | — | ✅ console automation |
Create the app record | 🧭 opens the right form, tells you what to type | 🧭 same |
Expo / EAS builds | ✅ start, poll, download, submit | ✅ |
Neither store lets anyone create an app record through an API, so *_create_app_form opens the right page in a logged-in browser and returns the exact values to fill. Everything else is automated.
How it compares
There are other good MCP servers for the stores, such as app-publish-mcp and mobile-release-mcp, and they cover the public APIs well. shipstores focuses on the steps that have no public API and usually end up done by hand: replying to App Review, the App Store privacy label and Google Play's "App content" declarations. It also keeps the tool list short (60 tools), and tools that publish or submit say so in their description, so the agent asks before acting.
If you only need what the public APIs offer, any of them will do. If you keep getting stuck on the console-only steps, that's the gap this project fills.
Related MCP server: App Store Connect MCP
Quick start
Requirements: Python 3.12+, uv, an App Store Connect API key and/or a Google Play service account. Xcode command line tools for iOS uploads (xcrun altool).
Add it to Claude Code (no clone needed, uvx fetches it from PyPI and runs it):
claude mcp add shipstores \
-e ASC_KEY_ID=ABC123XYZ \
-e ASC_ISSUER_ID=00000000-0000-0000-0000-000000000000 \
-e ASC_PRIVATE_KEY_PATH=~/.config/shipstores/AuthKey_ABC123XYZ.p8 \
-e PLAY_SERVICE_ACCOUNT_PATH=~/.config/shipstores/play-service-account.json \
-- uvx shipstoresThen ask your agent: "run store_doctor". It checks both credentials with real calls and detects your Apple Team ID for you.
Credentials
Variable | Required | What it is |
| iOS | App Store Connect → Users and Access → Integrations → API key (role Admin or App Manager) |
| iOS | the |
| no | detected by |
| Android | service account JSON invited in Play Console with release permissions |
| console forms | the number after |
| no | comma-separated tool groups to expose: |
For example, SHIPSTORES_TOOLSETS=apple,eas exposes only Apple and EAS tools, plus core diagnostics. The same setting can be configured as [server] toolsets = ["apple", "eas"] in ~/.config/shipstores/config.toml. Values can also live in that file — see config.example.toml. Nothing secret is ever written to the repo.
Console features (optional)
Privacy labels, availability, App Review replies and Play "App content" forms run through the store consoles' own web endpoints in a dedicated, logged-in browser profile, driven by browser-harness. Log in once:
uvx --from shipstores python -m shipstores.browser login # opens a window; sign in to both consoles (2FA included)⚠️ These features use undocumented console endpoints (the same family fastlane's Spaceship relies on). They work today and are isolated behind small modules, but Apple or Google can change them without notice. PRs that keep them working are very welcome.
Tools
Diagnostics — store_doctor, store_browser_session, store_audit_identity
Apple: build & release — apple_list_apps, apple_register_bundle_id, apple_create_app_form, apple_upload_build, apple_list_builds, apple_create_version, apple_list_versions, apple_set_version_string, apple_attach_build, apple_submit_for_review, apple_resubmit_for_review, apple_cancel_submission, apple_testflight_invite
Apple: listing & app setup — apple_update_listing, apple_upload_screenshots, apple_set_app_info (subtitle, URLs, categories, copyright, content rights), apple_set_age_rating, apple_set_free_price, apple_set_availability, apple_set_app_privacy, apple_review_details, apple_set_review_details
Apple: App Review — apple_review_messages (read the rejection and its guideline), apple_reply_review (answer with text + attachments; iPhone HEVC videos are converted to H.264)
Apple: subscriptions — apple_create_subscription_group, apple_create_subscription, apple_list_price_points, apple_set_subscription_price, apple_set_subscription_availability, apple_create_intro_offer, apple_list_subscriptions, apple_upload_subscription_screenshot
Google Play — play_create_app_form, play_track_status, play_upload_bundle, play_promote_release, play_update_listing, play_upload_screenshots, play_list_screenshots, play_contact_details, play_set_contact_details, play_signing_sha1, play_submission_status, play_submit_for_review
Play Console forms — play_content_status, play_content_open, play_content_options, play_content_answer, play_content_save, play_data_safety_fill, play_data_safety_export, play_data_safety_import
Expo / EAS — eas_build_list, eas_build_start, eas_build_status, eas_build_download, eas_submit
Tools that publish or submit (apple_submit_for_review, apple_resubmit_for_review, apple_reply_review, apple_cancel_submission, apple_set_*, apple_testflight_invite, play_upload_bundle, play_promote_release, play_upload_screenshots) say so in their description, so the agent confirms with you first.
Workflows
New iOS app
apple_register_bundle_id → apple_create_app_form → [fill in the browser]
→ apple_list_apps → eas_build_start / apple_upload_build → apple_list_builds (wait for VALID)
→ apple_attach_build → apple_update_listing → apple_set_app_info → apple_set_age_rating
→ apple_set_free_price → apple_set_availability → apple_set_app_privacy
→ apple_upload_screenshots → apple_set_review_details → apple_submit_for_reviewNew Android app
play_create_app_form → [fill in the browser] → play_upload_bundle (track=internal)
→ play_update_listing → play_content_* / play_data_safety_fill → play_promote_release (production)Rejected with "Guideline 2.1 – Information Needed" (standard for new developer accounts)
apple_review_messages → record the iPhone walkthrough → apple_set_review_details (answers in Notes)
→ apple_reply_review (answers + video) → apple_resubmit_for_reviewHard-won lessons
The part people bookmark. Each one cost a rejected build or a lost afternoon.
App Store Connect
New developer accounts get "2.1 Information Needed" on the first submission, regardless of app quality. Apple wants a screen recording from a physical device that starts at app launch from the Home Screen and shows login, the main flow and account deletion, plus purpose, access instructions, external services, regional differences and regulated-industry info — in the reply and in the review Notes. Replying is not enough: the version stays "Rejected" until you resubmit it (
apple_resubmit_for_review, or "Update Review" on the version page).Health apps must ship from an organization account (Guideline 5.1.1(ix)). An app rejected on an individual account can't be transferred (transfers need a released version): it becomes a new app with a new bundle ID.
You can't learn your Team ID from the API until a bundle ID exists; then it's the bundle's
seedId.Privacy label records need category + purpose + protection in the same record. Separate records are accepted one by one, then publishing fails with "An app data usage is missing a category/purpose or data protection type".
Availability needs every territory in the payload, each flagged available or not — and the public API returns 409 anyway; the console endpoint works.
Cancelling a submission also cancels its subscriptions, and that can't be undone by API. Re-adding them requires the console (details in
docs/apple-subscriptions.md).An app with an auto-renewable subscription is auto-rejected (3.1.2) without a working Terms of Use link in the listing. The standard Apple EULA link fixes it without a new build.
xcrun altoolwon't take a key path argument, but it honorsAPI_PRIVATE_KEYS_DIR.Screenshots belong to a version on iOS (a released version won't accept new ones — create the next version) but to the listing on Play (live immediately).
Expo / EAS
eas submit --non-interactiverefuses App Store Connect API keys; this server downloads the.ipaand uploads withaltoolinstead.eas build:viewrejects--non-interactive("Nonexistent flag") — a classic source of silent failures in wrappers.APNs keys are per team. After moving an app to another Apple team, a push key from the old team silently stops delivering (
InvalidProviderToken).
Google Play
The 11 "App content" declarations have no API. The Material radio
<input>sits ~15px above the visible circle; clicking the center focuses but doesn't select. The accessibility tree is the source of truth.Play Console app and developer ids only appear in console URLs; no API resolves them from a package name.
Contributing
Contributions are what make this useful for everyone — new stores' quirks change monthly. See CONTRIBUTING.md. Good first issues are labeled good first issue.
Contributors
Star history
License
MIT © Matheus Fidelis. Not affiliated with Apple or Google; App Store Connect and Google Play are trademarks of their owners.
The animated demo features Clawd, the Claude Code mascot by Anthropic. shipstores is an independent project, not affiliated with or endorsed by Anthropic.
Available Tools
60 toolsapple_attach_buildA
Attach a processed build to an App Store version.
The build must have processingState VALID (see apple_list_builds).
Inputs: build_id (required), version_id (required). Returns: object
apple_cancel_submissionA
Pull a version submitted for review out of the queue (before Apple decides). External action.
Use it to swap the build without waiting for the review: the version goes back to DEVELOPER_REJECTED and can be resubmitted with apple_submit_for_review.
Inputs: app_id (required). Returns: object
apple_create_app_formA
Open the App Store Connect new-app form in the browser.
Apple's API does not expose app creation (there is no POST /v1/apps), so this step is assisted: the tool opens the page in the already logged-in Chrome and returns the values you need to fill in. Register the Bundle ID first with apple_register_bundle_id.
Inputs: bundle_id (required), suggested_name (required). Returns: object
apple_create_intro_offerA
Create the subscription's introductory offer (free trial). External action.
duration: THREE_DAYS, ONE_WEEK, TWO_WEEKS, ONE_MONTH, TWO_MONTHS, THREE_MONTHS, SIX_MONTHS or ONE_YEAR. Apple has no "14 days" — TWO_WEEKS is the exact equivalent.
offer_mode: FREE_TRIAL (free), PAY_AS_YOU_GO or PAY_UP_FRONT. The last two charge a lower price and require a price point, which this tool does not cover.
territory is REQUIRED, one offer per country: Apple refuses to create the
offer without it. To apply in several countries, call once per territory.
Inputs: subscription_id (required), duration, territory, offer_mode, +1 more. Returns: object
apple_create_subscriptionA
Create a subscription product inside a group. External action.
product_id is IMMUTABLE and cannot be reused later — check it against what
the app sends to the store before calling. name is the internal reference
name; display_name and description are what customers read on the App Store.
subscription_period: ONE_WEEK, ONE_MONTH, TWO_MONTHS, THREE_MONTHS, SIX_MONTHS or ONE_YEAR. The App Store has no installment plans.
The product starts in MISSING_METADATA: it still needs a price (apple_set_subscription_price) and availability (apple_set_subscription_availability).
Inputs: name (required), group_id (required), product_id (required), description (required), +3 more. Returns: object
apple_create_subscription_groupA
Create a subscription group and its localization. External action.
reference_name is internal (only you see it); display_name is shown to
customers on the App Store. Every subscription product lives inside a group,
and free-trial eligibility is counted PER GROUP: someone who already had a
trial does not get another one, even when switching products within the group.
Inputs: app_id (required), display_name (required), reference_name (required), locale. Returns: object
apple_create_versionA
Create a new App Store version for an existing app.
Fails if an editable version already exists — in that case reuse the existing one (apple_list_versions) instead of creating another.
Inputs: app_id (required), version_string (required), platform. Returns: object
apple_list_appsA
List the apps in the App Store Connect account with id, bundleId and name.
The returned app_id is the App ID (ascAppId) used by every other Apple tool.
Inputs: no named parameters. Returns: result
apple_list_buildsB
List an app's builds and the processing state of each.
processingState PROCESSING means the build cannot be attached to a version yet; VALID means it is ready to use.
Inputs: app_id (required), limit. Returns: result
apple_list_price_pointsA
List the price points available for a subscription in a territory.
Apple does not accept arbitrary prices: you pick a point from its price table.
Pass around to see only the points near the price you want (e.g. 79.90).
Inputs: subscription_id (required), around, territory. Returns: result
apple_list_subscriptionsA
List the app's subscription groups, with the products in each.
state tells whether the product can go to review yet: MISSING_METADATA
means a price, availability or localization is missing. Only READY_TO_SUBMIT
can be included in a submission.
Inputs: app_id (required). Returns: result
apple_list_versionsB
List an app's App Store versions, with the review state of each.
Inputs: app_id (required), limit. Returns: result
apple_register_bundle_idB
Register a new Bundle ID in the Apple Developer portal.
This is the first step for a new app and IS supported by the API. After it, the app record itself must be created through the form (apple_create_app_form).
platform: IOS, MAC_OS or UNIVERSAL.
Inputs: name (required), identifier (required), platform. Returns: object
apple_reply_reviewA
Reply to App Review on a rejected submission, with attachments. External action.
For a "Guideline 2.1 - Information Needed" request: send the answers in
text (up to 4000 characters) and the video recorded on the iPhone in
attachments. HEVC video is converted to H.264 at 1920px before upload. Copy
the same information into the review notes with apple_set_review_details, as
Apple asks. Replying is not enough: the version stays Rejected until you
resubmit it ("Update Review" on the version page, then resubmit).
Inputs: text (required), app_id (required), attachments. Returns: object
apple_resubmit_for_reviewA
Resubmit a rejected version after replying to App Review or fixing it. External action.
Same as "Update Review" on the version page followed by "Resubmit to App Review": marks the rejected items as resolved and submits the same review submission again. Replying in the Resolution Center alone keeps the version Rejected. Attach a new build first (apple_attach_build) if the fix needed one.
Inputs: app_id (required). Returns: object
apple_review_detailsA
Read a version's App Review information (contact, demo account, notes).
The demo account password is masked — the goal here is to check what Apple will see, not to extract credentials.
Inputs: version_id (required). Returns: object
apple_review_messagesA
Read the review messages (Resolution Center) and the rejection reasons.
The public API does not expose this: it reads through the console's internal API, in the dedicated Chrome session (check store_browser_session if it fails due to login).
Inputs: app_id (required). Returns: object
apple_set_age_ratingA
Answer the age rating questionnaire. External action.
Starts from all "no/NONE" and applies overrides with what the app actually has.
Frequency values: NONE, INFREQUENT_OR_MILD, FREQUENT_OR_INTENSE.
E.g. a health app: {"healthOrWellnessTopics": true,
"medicalOrTreatmentInformation": "INFREQUENT_OR_MILD"}.
Inputs: app_id (required), overrides. Returns: object
apple_set_app_infoA
Fill in the listing fields that apple_update_listing does not cover. External action.
Subtitle and privacy policy URL live on the appInfo; support URL, marketing URL and copyright live on the editable version; categories use Apple IDs (e.g. MEDICAL, HEALTH_AND_FITNESS, LIFESTYLE, EDUCATION, PRODUCTIVITY, BOOKS). Only the fields passed are changed.
Inputs: app_id (required), locale, subtitle, copyright, +6 more. Returns: object
apple_set_app_privacyA
Replace and publish the "App Privacy" declaration (privacy nutrition label). External action.
usages: one item per collected data type: {"category": "NAME", "purposes": ["APP_FUNCTIONALITY"], "linked": true, "tracking": false} Empty list = "we do not collect data". Accepted categories and purposes are in apple_console.DATA_CATEGORIES / DATA_PURPOSES. Uses the console's internal API.
Inputs: app_id (required), usages (required). Returns: object
apple_set_availabilityB
Choose the countries where the app is available (3-letter ISO, e.g. ["BRA"]). External action.
Uses the console's internal API (the public one answers 409), in the dedicated Chrome session. Including the European Union requires the trader declaration (DSA) on the account.
Inputs: app_id (required), territories (required), available_in_new_territories. Returns: object
apple_set_free_priceC
Make the app free (price 0 in the base territory). External action.
Inputs: app_id (required), base_territory. Returns: object
apple_set_review_detailsA
Fill in the information App Review reads before testing. External action.
Only the fields passed are changed. When the app has content behind a login, the demo account must be able to reach what Apple wants to evaluate: in a subscription app, an account that already has everything unlocked hides the purchase screen, and review rejects the app for not being able to test it.
Passing demo_account_name turns on demoAccountRequired automatically.
Inputs: version_id (required), notes, contact_email, contact_phone, +4 more. Returns: object
apple_set_subscription_availabilityB
Set the countries where the subscription is sold. External action.
Without this the product stays in MISSING_METADATA and cannot go to review. The default is Brazil only (BRA).
Inputs: subscription_id (required), territories, available_in_new_territories. Returns: object
apple_set_subscription_priceA
Set the subscription price from a price point. External action.
Get the price_point_id from apple_list_price_points, and list it AFTER
setting availability: price points are issued per territory.
preserve_current_price keeps existing subscribers on their current price when
the price goes up, and only applies to a price CHANGE. Sending this attribute
on the initial price makes Apple answer 409 with "An error occurred while
processing the pricing information" — that is why the default is None, which
omits the field.
Inputs: price_point_id (required), subscription_id (required), preserve_current_price. Returns: object
apple_set_version_stringB
Rename an editable version. External action.
Useful to reuse a REJECTED version: while it occupies the slot, Apple refuses to create another one ("You cannot create a new version of the App in the current state"). Renaming it to the new build's version number avoids wiping the already filled-in listing.
Inputs: version_id (required), version_string (required). Returns: object
apple_submit_for_reviewA
Submit a version for Apple review. External action, hard to reverse.
Confirm with the user before calling. Requires the version to already have a build attached and complete metadata.
Inputs: version_id (required). Returns: object
apple_testflight_inviteA
Invite someone to the app's internal TestFlight (a group that receives every build). External action.
Internal testing skips review, but the person must be a user on the team in
App Store Connect (check under Users and Access). If no internal group named
group_name exists, one is created.
Inputs: email (required), app_id (required), last_name, first_name, +1 more. Returns: object
apple_update_listingB
Update the store listing texts of a version, for one locale.
Only the fields passed are changed. whats_new is the version's "What's New"
text; it cannot be used on an app's first version.
Inputs: version_id (required), locale, keywords, whats_new, +2 more. Returns: object
apple_upload_buildA
Upload an .ipa to App Store Connect via xcrun altool.
Build processing takes a few minutes after the upload — track it with apple_list_builds. platform: ios, osx or appletvos.
Inputs: ipa_path (required), platform. Returns: object
apple_upload_screenshotsA
Upload the App Store listing screenshots, in order. External action.
Uploads every image in the folder, in alphabetical order of file name, and pins that order in the store — without this the order falls back to creation order, which Apple does not guarantee. Name the files with a numeric prefix (01-, 02-).
A screenshot belongs to a VERSION: a READY_FOR_SALE version cannot be changed.
Create the next one with apple_create_version and point to it — the new
version inherits the previous one's screenshots, and replace swaps them for
these.
display_type: APP_IPHONE_67, APP_IPHONE_65, APP_IPHONE_61, APP_IPAD_PRO_3GEN_129, among others.
Inputs: folder (required), version_id (required), locale, replace, +1 more. Returns: object
apple_upload_subscription_screenshotA
Upload a subscription's App Review screenshot. External action.
Every subscription needs a screenshot showing where the purchase happens in the app, otherwise it stays stuck in MISSING_METADATA and cannot be part of any submission — even with price, localization, availability and offer all set. Use the screen where the subscription is offered, not the home screen.
App Store Connect uploads happen in three steps: reserve the asset, send the bytes to the URL it returns, and commit with the checksum.
Inputs: image_path (required), subscription_id (required). Returns: object
eas_build_downloadA
Download the binary of a finished EAS build to a local path.
This is the link between EAS and the publishing tools: download the artifact and pass the path to apple_upload_build or play_upload_bundle.
Inputs: build_id (required), destination (required), project_path (required). Returns: object
eas_build_listA
List an Expo project's EAS builds, with the artifact URL.
Use this to find out whether a ready binary already exists before spending a new
build. A present artifact_url means it can be published directly.
platform: ios or android. status: finished, in-queue, in-progress, errored.
Inputs: project_path (required), limit, status, platform. Returns: result
eas_build_startA
Start an EAS build and return immediately, without waiting for it to finish.
Builds take 10 to 40 minutes. This tool does NOT block — track progress with eas_build_status using the returned build_id.
platform: ios, android or all. profile: a profile defined in eas.json.
Inputs: platform (required), project_path (required), profile. Returns: object
eas_build_statusB
Get the state of an EAS build by id.
status FINISHED with artifact_url set means it is ready to publish.
Inputs: build_id (required), project_path (required). Returns: object
eas_submitA
Submit an EAS build straight to the store, using the submit profile in eas.json.
External action: this really publishes. Confirm the profile and platform with the user.
iOS: downloads the .ipa from EAS and uploads it via altool with this server's key (eas submit does not accept an API key without a prompt). Android: eas submit with the submit profile in eas.json. Without build_id, uses the most recent finished build.
Inputs: platform (required), project_path (required), profile, build_id. Returns: object
play_contact_detailsB
Read the public contact details of the app's Play listing.
These fields (contactEmail, contactWebsite, contactPhone) ARE covered by the API — do not automate the console form for them.
Inputs: package_name (required). Returns: object
play_content_answerA
Select an option by its text in the open declaration and confirm it took effect.
Material's sits ~15px above the visible circle, so a click at the center toggles nothing. This tool tries several offsets and only reports success when the accessibility tree confirms the state.
option: the option's label as shown in the console UI (pt-BR, e.g. "Não"). nth: when the same text appears several times (e.g. several "Não"), which occurrence to select, starting at 0.
Inputs: option (required), package_name (required), nth, save_after. Returns: object
play_content_openA
Open an "App content" declaration in the browser and return its text.
Use it to see the questions and options before answering. URL slugs do not follow the form name (e.g. "financial" lives at /finance, "app_access" at /testing-credentials) — this mapping is already resolved.
form: privacy_policy, ads, app_access, government, financial, health, data_safety, content_rating.
Inputs: form (required), package_name (required). Returns: object
play_content_optionsA
List the controls (radios/checkboxes) of the open declaration and the state of each.
Reads from the accessibility tree, not the DOM — Angular Material controls are not usable via querySelector. Call play_content_open first.
Inputs: package_name (required). Returns: result
play_content_saveB
Save the open declaration and dismiss the dialog the console opens afterwards.
button: the console button label, matched literally against the pt-BR UI: "Salvar" (Save), "Avançar" (Next, in multi-step wizards) or "Salvar como rascunho" (Save as draft).
Inputs: package_name (required), button. Returns: object
play_content_statusA
Show how many "App content" declarations are still missing before the app can publish.
A draft app on Play only leaves draft once all of them are complete. None of them has an API endpoint — they are console forms.
Inputs: package_name (required). Returns: object
play_create_app_formA
Open the Play Console app list in the browser to create a new app.
The Google Play Developer API cannot create a new packageName — the initial registration must go through the console. This tool opens the page and returns what to fill in.
Inputs: package_name (required), suggested_name (required). Returns: object
play_data_safety_exportB
Download the Data safety declaration CSV template.
The declaration is a 5-step wizard with hundreds of checkboxes, but it accepts CSV import — much faster and more reliable than clicking screen by screen. The download requires Browser.setDownloadBehavior (Page. does not work) and the file arrives with a GUID name, which this tool renames to datasafety-template.csv.
Inputs: package_name (required), destination_dir (required). Returns: object
play_data_safety_fillA
Fill in the Data safety CSV and return a summary of what was declared.
Imports nothing — it generates the file for review. An incorrect declaration here can take down a published app, so review the summary with the user before play_data_safety_import.
collected_data maps the Response ID of each collected data type (e.g. "PSL_EMAIL") to {"group": "PSL_DATA_TYPES_PERSONAL", "shared": false, "optional": false, "purposes": ["PSL_APP_FUNCTIONALITY", "PSL_ACCOUNT_MANAGEMENT"]}.
Inputs: template_path (required), collected_data (required), destination_path (required), supports_deletion, +2 more. Returns: object
play_data_safety_importA
Import the filled-in CSV into the Data safety declaration.
External action: replaces the app's entire declaration. Review the summary from play_data_safety_fill with the user before calling.
Inputs: csv_path (required), package_name (required). Returns: object
play_list_screenshotsB
List the published screenshots of one listing image type. Read-only.
Returns the sha256 of each image, in the order they appear in the store — you can compare them with local files to confirm what is published.
Inputs: package_name (required), language, image_type. Returns: object
play_promote_releaseA
Promote an already uploaded versionCode to another track, without a new upload.
External action: promoting to production publishes the app. Confirm with the user. For a staged rollout use status=inProgress with user_fraction (e.g. 0.1 = 10%).
Inputs: track (required), package_name (required), version_code (required), status, +2 more. Returns: object
play_set_contact_detailsA
Update the public contact details of the app's Play listing and commit.
External action: these details are shown to users on Google Play. Double-check that the e-mail and website belong to the publishing entity (see store_audit_identity).
Inputs: package_name (required), contact_email, contact_phone, contact_website. Returns: object
play_signing_sha1A
Download Play's app signing certificates and return the SHA-1 of each.
Use when "Sign in with Google" works on a local build but fails with the store
APK — symptom: the account picker opens, the user picks an account and lands
back on the login screen, with no error. With Play App Signing the distributed
APK is re-signed by Google, and the SHA-1 that reaches the device is the one
from deployment_cert.der.
The SHA-1 shown as text on the "App signing" page is the UPLOAD key's and does not work. This is the value to register as an Android OAuth client (package + SHA-1) in the Google Cloud Console — there is no API for that, UI only.
Inputs: download_dir (required), package_name (required). Returns: object
play_submission_statusB
Report whether there are changes waiting to be sent, in review, or nothing pending.
Reads the "Publishing overview" page. "Changes in review" means the changes were already sent to Google; "Send N changes for review" means they are still waiting to be sent.
Inputs: package_name (required). Returns: object
play_submit_for_reviewA
Send the app's pending changes to Google for review.
External action. On a new app this does NOT publish: "Send for review" and "Publish" are separate steps, and the second one remains yours. On an already published app with managed publishing turned off, approval publishes automatically — confirm before using it in that case.
Before calling, the release must be confirmed (Production -> Releases -> Edit release -> Next -> Save). Use play_submission_status to check.
Inputs: package_name (required). Returns: object
play_track_statusA
List the app's Play tracks and the active releases on each.
Read-only — opens and discards an edit without committing anything. Also useful to confirm that the service account has access to the app.
Inputs: package_name (required). Returns: result
play_update_listingA
Update the Play Store listing texts, for one language.
External action: the commit publishes the texts to the store. Google's limits — title 30 characters, short description 80, full description 4000.
Inputs: package_name (required), title, language, full_description, +1 more. Returns: object
play_upload_bundleA
Upload an .aab and release it on a Play track, in a single committed edit.
External action: on commit, the release becomes visible to the track's testers (or to the public, if track=production). Confirm the track with the user.
track: internal, alpha, beta or production. status: completed, draft, inProgress or halted.
Inputs: aab_path (required), package_name (required), track, status, +2 more. Returns: object
play_upload_screenshotsA
Upload the Play Store listing screenshots, in order. External action.
The commit publishes to the listing immediately — it does not depend on a release or on review. Store order is upload order, so images go in alphabetical order of file name: name them with a numeric prefix (01-, 02-).
image_type: phoneScreenshots, sevenInchScreenshots, tenInchScreenshots, tvScreenshots or wearScreenshots. Each size is a separate set — call once per folder.
Inputs: folder (required), package_name (required), replace, language, +1 more. Returns: object
store_audit_identityA
Scan both stores for text that should not be there.
Built to catch identity leaks — the wrong company's e-mail or name in a public
listing, review notes or contact details. pattern is a case-insensitive regex;
pass the domains/names that must not appear (the default is only a placeholder).
Returns what matched and where.
Inputs: pattern. Returns: object
store_browser_sessionA
Login state of the dedicated browser on both consoles.
Console forms (App content, Data safety, app creation) run in a headless Chrome with its own profile, so they do not fight the user for the screen. Apple's session expires often; when it does, the automation ends up reading the login screen and returns meaningless results — so check here before investigating a form that "did not save".
With relogin=True, opens Chrome WITH a window so a person can authenticate
(2FA cannot be automated). Pass console ('play' or 'apple') to open only
the one that expired.
Inputs: console, relogin. Returns: object
store_doctorA
Check the credentials for both stores with real API calls.
Use this before investigating any authentication error. Returns, for each store, whether the credential authenticates and what is missing.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 60 tools
Tools are mostly distinct with clear prefixes (apple_, play_, eas_, store_) and specific actions, making it easy to select the right one for a given store or task. However, multiple submission-related tools (e.g., eas_submit, apple_submit_for_review, play_submit_for_review) and several 'set_' tools for different metadata fields could cause confusion without careful reading of descriptions.
Tool names follow a highly consistent pattern: a platform prefix (apple_, play_, eas_, store_) followed by a verb_noun structure (e.g., list_apps, create_version, upload_build). There are no deviations in casing or style, making the set predictable and easy to navigate.
With 60 tools, the server far exceeds the typical 3–15 range and even the 25-tool threshold for being overly heavy. While the domain (two app stores plus EAS builds) is broad, the sheer number of tools risks overwhelming an agent and suggests the server could be split into more focused sets.
The tool surface covers the full lifecycle for both Apple and Google Play: builds, uploads, metadata, submissions, subscriptions, screenshots, and content declarations. Minor gaps exist, such as reading Play reviews or managing Apple in-app purchases beyond subscriptions, but these are not critical for the core publishing workflows.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
App Store Connect operator for AI agents: icons, TestFlight builds, listings, IAP, rejection fixes.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Your agent needs app-store data — what an app looks like on the App Store and Google Play, what reviewers say, and what ranks for a search in a given country. **What you can ask for** • "What does this app's store listing look like, and how is it rated?" • "Pull recent reviews for this app and group the complaints." • "What apps rank for this search term in Japan?" • "List the top apps in this category on both stores." • "Compare this app's listing on iOS and Android." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-apps/mcp and sign in with OAuth — there is no key to create or paste. 37 tools: Apple App Store and Google Play app info, app lists, category listings, reviews and store search results, in live and queued forms, with categories, languages and locations for each. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Read the store listing here, then ask the same agent what the app's website ranks for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Related MCP Servers
- AlicenseBqualityBmaintenanceUnified MCP server for App Store Connect & Google Play Console — manage listings, screenshots, releases, reviews & submissions188234 npm41MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that exposes the entire Apple App Store Connect API (1,200+ operations) as MCP tools, enabling AI assistants to query apps, manage builds, handle submissions, read analytics, and more.106 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for managing mobile app releases on App Store Connect and Google Play. It exposes 101 tools for iOS and Android release lifecycle and reacts to EAS/GitHub webhooks automatically.46 npmMIT
- AlicenseNot gradedqualityBmaintenanceGoogle Play Console MCP server — lets AI agents manage releases, track rollouts, reply to reviews, and pull crash/acquisition reports directly from Google Play Console.61 npm1MIT