Android Developer MCP by Nova (CIVAI)
Server Details
Ship a new Android app from chat. AI runs Google Play Console listings, screenshots, releases, uplo…
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 40 tools
Many tools have genuinely distinct targets (upload_bundle vs attach_artifact_to_release vs start_rollout), and the descriptions go out of their way to warn about prior misselection. However, the state-reading cluster (get_pre_submit_status, get_setup_state, get_app_submission_state, get_release, get_track) is explicitly self-described as overlapping and misleading, and upload_screenshot_asset vs upload_store_listing_graphic plus the nine separate update_*_declaration tools force the agent to read long caveats before choosing. Descriptions help, but boundaries are not clean.
Every tool is snake_case with a leading verb (get_/list_/create_/update_/upload_/start_/send_/attach_/grant_/promote_). Domains are named consistently (track, release, listing, declaration) so related tools sort together. No mixed conventions anywhere.
40 tools is heavy even for a genuinely large domain like the Play Console. Several near-duplicates (four+ read-state tools, three upload tools, nine single-field declaration updaters) could be consolidated into parameterized tools, so the surface feels wider than the work it performs.
The publish lifecycle is unusually thorough: app creation, signing enrolment, bundle upload, artifact attach, tracks, countries, listings, graphics, mandatory declarations, review submission, tester setup and permissions. Gaps remain around post-launch operations — no rollout halt/cancel, no release-notes editing, no app or release deletion — but core submission workflows are covered end to end.
Available Tools
40 toolsattach_artifact_to_releaseAInspect
Attach an already-uploaded artifact (version code) to a release — the required step between upload_bundle and start_rollout. Uploading a bundle does NOT attach it, so without this the release has no artifact and start_rollout refuses. Identify the artifact by artifact_id, or give version_code and it is looked up among the app's processed artifacts. Carries the release's existing name and notes forward untouched. Reads the release back afterwards and returns attach_verified plus the attached version codes rather than assuming success. This does NOT publish — call start_rollout for that, and confirm with the user first.
Inputs: track_id (required), release_id (required), play_app_id (required), developer_id (required), +4 more.
check_package_name_availabilityAInspect
Check whether a package name is available before creating a new app. Derived from web decompile recon, not the official API — uses the Play Console web session, not the service account.
Inputs: developer_id (required), package_name (required), google_account_email (required), notification_message.
create_appAInspect
Create a brand-new Android app on Google Play — the one thing the official Android Publisher API cannot do. Derived from web decompile recon of Play Console's own client, not yet verified against a real call; uses the Play Console web session (browser_auth_profile.json), not the service account. Check package_name availability first.
Inputs: app_title (required), developer_id (required), package_name (required), default_language (required), +9 more.
create_releaseAInspect
Create a new draft release on a track. Play Console allows only one draft release per track at a time — fails clearly if one already exists rather than guessing its id. Optionally sets a release_name (cosmetic label only).
Inputs: track_id (required), play_app_id (required), developer_id (required), google_account_email (required), +2 more.
declare_asset_ai_stateAInspect
Declare whether the store listing's images were created or edited using AI. Play Console's listing editor has a second step ("Review") carrying this REQUIRED regulatory declaration, and until it is answered the listing stays Draft, the dashboard's store_listings task stays incomplete, and send_app_for_review refuses with a bare FAILED_PRECONDITION — however complete the listing content is. DRY-RUN BY DEFAULT. This is a statement to a regulator about who made the images: ask the user, never infer it.
Inputs: play_app_id (required), developer_id (required), ai_declaration (required), google_account_email (required), +2 more.
enroll_play_app_signingAInspect
Read, or set, an app's Play App Signing enrolment. An app that is NOT enrolled CANNOT accept an .aab: upload_bundle returns 200 and Play then rejects the bundle during processing (error 3008), leaving a pending upload reference, no artifact, and an unexplained 400 from start_rollout. Call with action="status" first — that is read-only. Enrolment is PERMANENT, sets the app's signing identity for the life of the app and gives Google custody of the app signing key: get the user's explicit agreement to this specific action before enrolling, and ask whether Google should generate a fresh key or reuse another app's deployment key. There is no way to ship an .aab without it.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), action, +3 more.
get_app_submission_stateAInspect
Has this app ever been sent for Google Play review? ANSWERS WHAT get_pre_submit_status CANNOT: that tool reported review_eligible: true for an unreviewed draft app that could not publish by any route. An app that has never been reviewed cannot be rolled out to production at all. ever_submitted_for_review is the trustworthy field. The status codes are RAW AND UNMAPPED on purpose — a previous guess reported a live in-review submission as REJECTED — so do not read a verdict into them; Play Console's Publishing overview is the authority on the real state. If the submission history cannot be read, this returns submission_state_known: false rather than guessing 'never submitted'.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), notification_message.
get_network_identityAInspect
Where this user's requests to the site leave from (a VPN country, the server, or the app's default) and which browser they present. Read-only.
Inputs: no named parameters.
get_pre_submit_statusAInspect
Read-only: what Google Play still requires before this app is review-eligible. Reports each App Content declaration's state, the hub's blocking validation errors, the store listing's validation warnings, and whether the Publishing page considers the app blocked. review_eligible is conservative — if any source could not be read it is false and the unread source is listed in errors, so never report an app as clear on a partial answer.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), store_listing_id, +1 more.
get_releaseAInspect
Get a release's current state, including currently-attached artifacts and validation status — check this before start_rollout.
Inputs: track_id (required), release_id (required), play_app_id (required), developer_id (required), +2 more.
get_setup_stateAInspect
Read the app dashboard's setup checklist. Returns which tasks are complete and which are still open (privacy_policy, app_access, ads, content_rating, target_audience, store_settings, store_listings, prod_countries, prod_release, ...). WARNING: the incomplete list is NOT a list of blockers — measured live, it listed 10 open tasks while Play Console's own Submit button was enabled and the app then submitted fine. It mixes real setup items with the action you are trying to take (sent_for_review), paths the app does not use (open, prereg_*) and consequences that only become true after review and rollout (prod_rollout, serving_in_prod). Still far better than get_pre_submit_status, which reads declarations and listing warnings only. For whether a submission can actually go through, use send_app_for_review's dry run (Play's blocked flag) or the Publishing overview. Read-only.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), notification_message.
get_trackAInspect
Get one release track's current state by track_id, including every release on that track with its release_id, name, status and lifecycle state. This is how you find an existing draft release's id after create_release refuses a second draft.
Inputs: track_id (required), play_app_id (required), developer_id (required), google_account_email (required), +1 more.
get_user_permissionsAInspect
Read one principal's current Play Console permissions by email — read-only, nothing changes. Works for a human teammate or a service account (…@….iam.gserviceaccount.com); both are the same user row keyed by email. Returns account-level permissions and, per app, the exact permission values already held. This is the prerequisite before grant_app_permission: an append has to preserve every app the principal already reaches, so read the current grants first and confirm them with the user.
Inputs: developer_id (required), target_user_email (required), google_account_email (required), notification_message.
grant_app_permissionAInspect
Grant a principal (teammate or service account) access to ONE app, as an APPEND that preserves every existing app grant and all account-level permissions. Use it to give a CI service account release access to a newly-created app — the step the androidpublisher API cannot do for a release-scoped service account (it 403s, it cannot grant itself access); this runs on the owner's Play Console session. DRY-RUN BY DEFAULT: with commit omitted/not "true" it pre-reads and returns the exact before/after WITHOUT writing — show that to the user and get their explicit agreement to this specific account-permissions change, then re-run with commit="true". A relayed approval is not the user's approval. The write is append-only (refuses to drop or shrink any existing grant), scoped so account-level permissions are untouched, and re-reads afterwards to prove the append. For the permission set, prefer copy_permissions_from_app_id (copies an existing grant's values verbatim — matches the account's pattern and names no enum value).
Inputs: developer_id (required), target_app_id (required), target_user_email (required), google_account_email (required), +5 more.
list_accountsAInspect
List which Google accounts are signed in to this browser session, with their X-Goog-AuthUser slot index. For visibility/debugging only.
Inputs: notification_message.
list_appsAInspect
List apps on this Play Console developer account. Derived from web decompile recon, not the official API.
Inputs: developer_id (required), google_account_email (required), page_size, page_token, +1 more.
list_tracksAInspect
List an app's release tracks and their track_id — call this first to find the track_id other release tools need.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), notification_message.
promote_releaseAInspect
Promote an existing release to another track WITHOUT re-uploading the bundle. WARNING, measured 2026-10-28: it creates an EMPTY draft release — it does NOT carry the artifact across, despite what this description used to claim. ALWAYS follow it with attach_artifact_to_release and check attach_verified, or start_rollout will refuse because the release has no artifact. Its new_release_id also echoes the SOURCE release id, so read the destination with get_track rather than trusting the echo. It does NOT publish; call start_rollout afterwards and confirm with the user first.
Inputs: play_app_id (required), developer_id (required), source_track_id (required), destination_track_id (required), +4 more.
refresh_browser_sessionAInspect
Check that the saved Play Console session still works and list the signed-in Google accounts. Read-only: it never refreshes the session (refreshing a copied session signs the user out of Chrome). If the session has expired, the user reconnects with start_browser_auth.
Inputs: notification_message.
send_app_for_reviewAInspect
Send the app's pending changes to Google Play review — the API behind Play Console's "Send app for review". OUTWARD-FACING AND NOT FREELY REVERSIBLE: for an app that has never shipped this is the submission that decides whether it can be published at all. DRY-RUN BY DEFAULT — it reports what would be sent and sends nothing until commit="true". Confirm with the user first, exactly like start_rollout. It fetches the publishing page's continuation token itself and round-trips it, which is what Play actually requires; the dry run also reports Play's own blocked flag, the best machine-readable "can this be sent?" in this capture. A FAILED_PRECONDITION here is NOT reliably a setup-task problem — that was wrong for a whole session. Read the dry run's publishing_page block and Play Console's Publishing overview before blaming the app's state.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), commit, +7 more.
set_network_identityAInspect
Choose where this user's requests to the site leave from and which browser they present, only when the user asks (e.g. 'connect through Nigeria', 'use my own user agent'). Sites may ask the user to sign in again when this changes. reset=true goes back to how they signed in.
Inputs: reset, route, locale, country, +4 more.
setup_closed_testingAInspect
Set up a track's testers: creates or updates a tester email list and attaches it to the track as an audience group. Google requires a personal developer account to run a closed test with a minimum tester count for a minimum number of days before it can even APPLY for production access — this starts that clock, and reports the live required-vs-current tester and day counts so the gap is a number. DRY-RUN BY DEFAULT.
Inputs: track_id (required), play_app_id (required), developer_id (required), google_account_email (required), +4 more.
start_browser_authAInspect
Open Play Console sign-in only when needed. If the saved session is still valid, this tool returns success immediately and does not open the viewer. Call session_status first. Use force_reconnect only when the user explicitly wants to wipe the saved cookie and sign in again (destructive).
Inputs: force_reconnect.
start_rolloutAInspect
Roll out a release — this IS Android's publish action for the release. Not simply reversible; always confirm with the user, especially on production. Preconditions it cannot satisfy itself: the release needs an artifact attached (attach_artifact_to_release — promote_release does NOT attach one), and the track needs at least one EXPLICITLY selected country (target_rest_of_world alone is not a selection — see update_track_countries). A bare FAILED_PRECONDITION here names nothing: open the Console's release review page (.../tracks/{track}/releases/{release}/review) and expand its errors, which is read-only and states the cause in one sentence. Production additionally requires the app to have passed review once.
Inputs: track_id (required), release_id (required), play_app_id (required), developer_id (required), +5 more.
submit_prod_access_applicationAInspect
Submit the production-access application questionnaire for a personal developer account. Only possible once the closed-testing tester/day requirement is met (see setup_closed_testing and get_setup_state). All ten answers are the developer's own words about their testing — never invent them. DRY-RUN BY DEFAULT.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), commit, +11 more.
update_ads_declarationAInspect
Declare whether the app contains ads, using Play Console's own web session. Mandatory App content declaration required before a new app is eligible for production submission/review.
Inputs: play_app_id (required), contains_ads (required), developer_id (required), google_account_email (required), +1 more.
update_content_ratingAInspect
Submit and apply the mandatory IARC content rating questionnaire, using Play Console's own web session. Only content_rating_category="all_other_app_types" (every question answered No, producing the lowest possible rating) is currently supported — the correct choice for a brand-new app with no mature content.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), content_rating_category (required), +2 more.
update_data_safetyAInspect
Submit the Data safety declaration. data_collection="none" declares the app collects and shares NO user data; data_collection="collects" files the per-data-type questionnaire from data_types. REQUIRES update_privacy_policy to have been called first. This is a public, legally-meaningful statement about the app: "none" is a FALSE declaration for any app that collects anything at all, including a push notification token, so confirm what the app actually collects with the user rather than assuming. Nothing is defaulted on your behalf — an unknown data type or a missing purpose is refused, not approximated. An app where users can sign up must also answer the account section (questions 92-96); pass the real account_creation_methods plus the deletion URLs rather than defaulting to "none", which publicly declares the app has no sign-up.
Inputs: play_app_id (required), developer_id (required), data_collection (required), google_account_email (required), +9 more.
update_none_option_declarationAInspect
Declare 'none of the above' for a multi-select feature-checklist App content declaration, using Play Console's own web session. Mandatory declarations. Currently supports none_option_declaration="financial_features" (does the app provide any financial features?) or "health" (does the app use any health features?). Only the 'none apply' answer is supported.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), none_option_declaration (required), +1 more.
update_policy_declarationAInspect
Set a simple Yes/No App content policy declaration, using Play Console's own web session. Mandatory declaration gating production submission eligibility. Currently supports policy_declaration="advertising_id" (does the app use advertising ID?) or "government_app" (is this app developed by or on behalf of a government?).
Inputs: play_app_id (required), developer_id (required), policy_declaration (required), google_account_email (required), +2 more.
update_privacy_policyAInspect
Set the app's privacy policy URL, using Play Console's own web session. Mandatory App content declaration, and a prerequisite for submitting the Data safety declaration.
Inputs: play_app_id (required), developer_id (required), privacy_policy_url (required), google_account_email (required), +1 more.
update_sign_in_detailsAInspect
Declare whether any part of the app is restricted (requires account sign-in, payment, referral/QR codes, OTP, biometrics, or actions on another device). Formerly 'App access'. Mandatory App content declaration and one of the app-dashboard setup tasks that gate send_app_for_review. Both answers are supported: "false" is live-verified; "true" attaches reviewer credentials and its wire shape is derived from Play Console's own bundle but not yet live-verified — check the App access page after filing one.
Inputs: play_app_id (required), developer_id (required), is_restricted (required), google_account_email (required), +2 more.
update_store_listingAInspect
Update an app's main store listing (title, short/full description) for one language using Play Console's own web session. Does NOT need create_edit/commit_edit — it patches the listing directly. On an app whose language has no listing entry yet this CREATES the entry (verified live), so it is the first call before attaching any graphic. Note the PATCH replaces the whole entry for that language, so title, short_description and full_description must all be supplied together.
Inputs: title (required), language (required), play_app_id (required), developer_id (required), +7 more.
update_store_listing_screenshotsAInspect
Reorder or remove an app's existing store-listing screenshots for one language. Preserves the listing's title/descriptions untouched. Can ONLY reorder/remove already-uploaded screenshots (matched by URL) — cannot add a brand-new screenshot image.
Inputs: language (required), play_app_id (required), developer_id (required), screenshot_urls (required), +3 more.
update_store_settingsAInspect
Set the app's store category and public contact details — one of the app dashboard setup tasks that gates send_app_for_review. Until it is done Play refuses the review submission with a bare FAILED_PRECONDITION and Play Console's own Send-for-review button stays greyed out. The contact details are PUBLIC on the store listing. Derived from Play Console's own bundle; not yet live-verified.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), app_category, +4 more.
update_target_audience_contentAInspect
Declare the app's target audience & content, using Play Console's own web session. Mandatory App content declaration. Only target_audience="adults" (18 and over only, not aimed at children) is currently supported — the correct, simplest answer for an app with no child-directed content.
Inputs: play_app_id (required), developer_id (required), target_audience (required), google_account_email (required), +1 more.
update_track_countriesAInspect
Set which countries/regions a release track serves — the precondition for a track's first rollout. CRITICAL, measured 2026-10-28: pass at least one explicit targeted_countries value. target_rest_of_world="true" ALONE writes the rest-of-world flag and leaves the country list empty, and Play's release validator then refuses every rollout with "No countries or regions have been selected for this track" — surfacing from start_rollout as a bare FAILED_PRECONDITION with no detail, while get_setup_state still reports closed_countries/prod_countries as complete. For a worldwide launch pass one real market in targeted_countries AND target_rest_of_world="true". Does not publish anything. Ask the user which countries; never pick for them.
Inputs: track_id (required), play_app_id (required), developer_id (required), google_account_email (required), +3 more.
upload_bundleAInspect
Upload a signed .aab. IMPORTANT: uploading does NOT attach the artifact to the release — it only becomes an app-level artifact (visible with its own version code) while the release's addedArtifacts stays empty, so start_rollout would have nothing to roll out. Call attach_artifact_to_release next, then get_release to check signing/content validation, then start_rollout. This call only confirms the bytes arrived and that Play accepted the bundle for processing.
Inputs: track_id (required), release_id (required), play_app_id (required), developer_id (required), +5 more.
upload_screenshot_assetAInspect
Upload an image into the app's Asset Library. NOTE: for store listing graphics use upload_store_listing_graphic instead — the Asset Library's image cannot be attached to a listing slot (it lacks the blobKey the listing requires, confirmed live). This tool is only for getting an image into the Asset Library itself.
Inputs: play_app_id (required), developer_id (required), google_account_email (required), image_url, +3 more.
upload_store_listing_graphicAInspect
Upload an image AND attach it to a store-listing slot in one call — phone screenshot, feature graphic or app icon. This is what makes a store listing completable from here; upload_screenshot_asset only gets an image into the Asset Library and CANNOT attach it. Play requires at least 2 phone screenshots plus a feature graphic and an icon for a complete listing, so call this once per image. Preserves the listing's existing text and other graphics, and refuses rather than risking a partial overwrite. Give the image ONE of three ways: image_base64 (inline bytes, no hosting needed, 64 KiB cap), image_url (https, any size) or image_path (replay host only).
Inputs: language (required), image_type (required), play_app_id (required), developer_id (required), +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Ship a new iOS app from chat. AI runs App Store Connect, builds, release, and submission through Ap…
Build, host and publish web, web3 (Solana, Base), Android apps and AI agents from a description.
Turn websites into Android apps from your AI agent: create, set icons, build and download APK/AAB.
151AppDeploy turns app ideas described in AI chat into live full-stack web applications
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables managing releases, monitoring Android vitals, analyzing earnings and search terms, optimizing ASO, and preflighting store assets through natural language, with a confirmation gate before destructive writes.17049 PyPI2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate Android release workflows via the Google Play Android Publisher API, including deploying builds, managing listings, and replying to reviews.40MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates Google Play Store management tools with AI assistants to handle app listings, releases, and user reviews. It enables users to manage Play Console tasks like updating store information and retrieving performance statistics through natural language.349 npm11MIT
- AlicenseNot gradedqualityCmaintenanceEnables autonomous AI agents and developers to programmatically manage Google Play apps via the Play Developer API v3, including uploading Android App Bundles, managing release tracks, updating store listings, and replying to user reviews.3MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.