Google Play Console MCP vs Sceneview MCP

In-depth architectural comparison of the Google Play Console MCP and Sceneview MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Google Play Console MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: list_tracks, get_track_info, create_release.

Explore Google Play Console MCP Details

Choose Sceneview MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Sceneview MCP Details

Feature & Specification Comparison

Specification	Google Play Console MCP Browser Automation	Sceneview MCP Browser Automation
Summary	Google Play release lifecycle: tracks, testers, rollout, and Android Vitals.	3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "google-play-console-mcp": {
      "command": "uvx",
      "args": [
        "google-play-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-204": {
      "command": "npx",
      "args": [
        "-y",
        "sceneview-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons