# Civai Nova Android Developer MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Fmcp-android_developer
Registry id: `mcp-registry/co.civai.nova/mcp-android_developer`
Status: live (checked 2026-11-22T15:03:43.317Z)

## Measurements (30 days)

- Uptime: 98.96%
- Checks: 4736
- Outages (90 days): 61

## Install

```json
{
  "mcpServers": {
    "civai-nova-android-developer-mcp-server": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/mcp-android_developer"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http civai-nova-android-developer-mcp-server https://nova.civai.co/mcp/agents/mcp-android_developer
```

## Tools (40)

- `attach_artifact_to_release`: 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 
- `check_package_name_availability`: 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,
- `create_app`: 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 o
- `create_release`: 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
- `declare_asset_ai_state`: 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 re
- `enroll_play_app_signing`: 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
- `get_app_submission_state`: 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 
- `get_network_identity`: 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.
- `get_pre_submit_status`: 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 error
- `get_release`: Get a release's current state, including currently-attached artifacts and validation status — check this before start_rollout.
- `get_setup_state`: 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_aud
- `get_track`: 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 
- `get_user_permissions`: Read one principal's current Play Console permissions by email — read-only, nothing changes. Works for a human teammate or a service account (…@….iam.gserviceac
- `grant_app_permission`: 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 i
- `list_accounts`: List which Google accounts are signed in to this browser session, with their X-Goog-AuthUser slot index. For visibility/debugging only.
- `list_apps`: List apps on this Play Console developer account. Derived from web decompile recon, not the official API.
- `list_tracks`: List an app's release tracks and their track_id — call this first to find the track_id other release tools need.
- `promote_release`: 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 carr
- `refresh_browser_session`: 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 ses
- `send_app_for_review`: 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
- `set_network_identity`: 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 us
- `setup_closed_testing`: 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
- `start_browser_auth`: 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 sessio
- `start_rollout`: Roll out a release — this IS Android's publish action for the release. Not simply reversible; always confirm with the user, especially on production. Preconditi
- `submit_prod_access_application`: Submit the production-access application questionnaire for a personal developer account. Only possible once the closed-testing tester/day requirement is met (se
- `update_ads_declaration`: 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 producti
- `update_content_rating`: Submit and apply the mandatory IARC content rating questionnaire, using Play Console's own web session. Only content_rating_category="all_other_app_types" (ever
- `update_data_safety`: 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
- `update_none_option_declaration`: Declare 'none of the above' for a multi-select feature-checklist App content declaration, using Play Console's own web session. Mandatory declarations. Currentl
- `update_policy_declaration`: Set a simple Yes/No App content policy declaration, using Play Console's own web session. Mandatory declaration gating production submission eligibility. Curren
- `update_privacy_policy`: 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 dec
- `update_sign_in_details`: Declare whether any part of the app is restricted (requires account sign-in, payment, referral/QR codes, OTP, biometrics, or actions on another device). Formerl
- `update_store_listing`: 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 
- `update_store_listing_screenshots`: Reorder or remove an app's existing store-listing screenshots for one language. Preserves the listing's title/descriptions untouched. Can ONLY reorder/remove al
- `update_store_settings`: 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
- `update_target_audience_content`: 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
- `update_track_countries`: 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 tar
- `upload_bundle`: 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 cod
- `upload_screenshot_asset`: 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 at
- `upload_store_listing_graphic`: 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 completabl

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
