Developer · Local MCP server

Play Console MCP

Manage Google Play Console: releases, listings, monetization, reviews, and Android Vitals.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.wiseappsai/play-console-mcp
Version
0.3.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-05-31
Updated
2026-05-31
Publisher
wiseappsai (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/wiseappsai) · how
Repository
github.com/wiseappsai/play-console-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@wiseappsai/play-console-mcp0.3.0stdioPLAY_SERVICE_ACCOUNT_JSON (secret), GOOGLE_APPLICATION_CREDENTIALS, PLAY_DEVELOPER_ACCOUNT_ID, PLAY_REPORTS_BUCKET, PLAY_STORAGE_CREDENTIALS, PLAY_TOOLSETS, PLAY_READ_ONLY

How to connect Play Console MCP

Play Console MCP runs locally from a Node.js package published to the npm registry: @wiseappsai/play-console-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @wiseappsai/play-console-mcp@0.3.0. It reads these environment variables: PLAY_SERVICE_ACCOUNT_JSON (secret), GOOGLE_APPLICATION_CREDENTIALS, PLAY_DEVELOPER_ACCOUNT_ID, PLAY_REPORTS_BUCKET, PLAY_STORAGE_CREDENTIALS, PLAY_TOOLSETS and PLAY_READ_ONLY; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "play-console-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@wiseappsai/play-console-mcp@0.3.0"
      ],
      "env": {
        "PLAY_SERVICE_ACCOUNT_JSON": "<secret>",
        "GOOGLE_APPLICATION_CREDENTIALS": "<value>",
        "PLAY_DEVELOPER_ACCOUNT_ID": "<value>",
        "PLAY_REPORTS_BUCKET": "<value>",
        "PLAY_STORAGE_CREDENTIALS": "<value>",
        "PLAY_TOOLSETS": "<value>",
        "PLAY_READ_ONLY": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Plate Website SourceRead-only catalog of free Plate website source projects a coding agent can adapt.Remote · HTTPLive check: ✓ handshakegetplate.pages.dev
Plateau Creative MCPPLATEAU 3D city data as scene-editing and glTF export tools for creative LLM agents.Local · stdionpm: @yodolabs/plateau-creative-mcp
PlatformBackend for AI-built apps: database, auth, files, email, AI, payments, deploy, realtime. 170+ tools.Remote · HTTPLive check: sign-in requiredmcp.somewhere.tech
PlatformIOPlatformIO for AI agents: build, flash, serial monitor, tests, crash decoding, size reports.Local · stdioPyPI: platformio.mcp
Play Declaration Gap Lint15 checks that name every Play Console declaration your manifest opens.Local · stdionpm: @readystack/play-declaration-gap-lint
Play Release Blocker LintFinds the lines that make Google Play reject your release - target API below 36, Billing Library bel.Local · stdionpm: @readystack/play-release-blocker-lint
PlayrunnerDiscover Playwright workflows, start runs, and inspect results in Playrunner Cloud.Remote · HTTPLive check: sign-in requiredplayrunner.cloud
Playwright Report MCPRun Playwright tests and surface structured results for AI agents doing test failure analysis.Local · stdionpm: playwright-report-mcp