PubShip

io.github.pubship由 GitHub 账号 pubship 发布v0.24.2更新于 Oct 24, 2026

Google Play reads and explicitly opted-in operations using your own local Google access.

发布方自己的服务:ship.page

已验证STDIO仅桌面开发者工具商业与电商

概览

AI 生成的概览

本地 MCP 服务器,让助手使用你自己的服务账号读取 Google Play 控制台信息,并在明确授权后准备变更。

可以做什么
  • 读取发布版本、评价、Android vitals 和限定范围的批量报告
  • 查看目录、订阅、商品和账号资源,敏感数据需单独授权
  • 在明确的应用与方法权限下准备和审阅写入操作,且执行仅限一次
  • 处理有大小限制的本地文件传输,并将发布与编辑暂存分开
适用场景
适合希望让助手查看自己应用在 Play 控制台的发布、评价与报告,并在本机内暂存经谨慎授权变更的 Android 开发者。
运行要求
通过 uvx 从 PyPI 包 pubship 以 stdio 在本地运行。需要一个对你有权限的应用具备 Play 控制台权限的 Google 服务账号,将私钥 JSON 路径设为 GOOGLE_APPLICATION_CREDENTIALS,并在 GOOGLE_PLAY_PACKAGES 中填写包名。可用 --check 参数做无需凭据的安装检查。
安装前请注意
服务账号密钥属于敏感凭据:请妥善保管 JSON 文件,只提供其路径,切勿把内容粘贴到助手对话中。写入和敏感读取默认关闭,需显式配置;提交的变更不一定已发布。仅用于你或你所在组织拥有的应用与账号,并注意提供方文本被视为不可信数据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 PubShip,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

PubShip

Google Play developer workflows, from your own computer. Inspect releases, understand reviews and reports, and prepare explicitly authorized changes from your MCP client.

[CI] [Release] [AGPL-3.0-only] [PubShip MCP server – quality and maintenance score on Glama]

Start locally

Use your own service account with permissions for your apps in Play Console. Keep its private JSON outside this repository. Grant only the permissions needed for your intended operations. Never paste credentials into an assistant conversation.

sh
export GOOGLE_APPLICATION_CREDENTIALS=/absolute/private/path/service-account.jsonexport GOOGLE_PLAY_PACKAGES=com.example.appuvx pubship

This starts the stdio server, which waits for an MCP client. For a credential-free installation check:

sh
uvx pubship --check

The commands above install the published PyPI package. A source checkout may contain changes that are not yet published; after uv sync, use uv run pubship --check to check the local version.

Connect an assistant

Claude Code

sh
claude mcp add --transport stdio pubship -- uvx pubship

Set the environment variables above in the shell launching your client. Restart the client after changing its environment.

Codex

sh
codex mcp add pubship -- uvx pubship

Cursor and Gemini CLI

Client manifests in this repository declare the local service-account key path and package names. See client setup for configuration and the Gemini CLI installation command. For agent-assisted installation, read llms-install.md. Provide only the key file path, never its contents.

Generic MCP harness

Configure a stdio server with executable uvx, argument pubship, and your local environment. For clients that require explicit configuration:

json
{  "mcpServers": {    "pubship": {      "command": "uvx",      "args": ["pubship"],      "env": {        "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/private/path/service-account.json",        "GOOGLE_PLAY_PACKAGES": "com.example.app"      }    }  }}

Client configuration stays on your computer. Consult setup for alternate authentication modes, enabled APIs, reports and permission boundaries.

What can it do?

[Local API coverage]

The pinned inventory contains 172 method definitions. 170 have implementations, one subscription-archive method is unsupported by Google, and voided-purchases access is deliberately disabled by project policy. Disabled operations cannot be called through local or self-host tools.

  • Read releases, reviews, Android vitals and scoped bulk reports.
  • Inspect catalog, subscription, product and account resources with separate sensitive-data grants.
  • Prepare and review writes with explicit app/method permissions and single-use execution.
  • Keep local file transfers bounded and separate publication from edit staging.

Reads are the default. Optional writes and sensitive reads require explicit configuration. Provider text is untrusted data. Missing data is not zero; a submitted change is not necessarily published. No operation count is a claim of live Google verification.

Explore the contracts and boundaries

Self-hosting for your own accounts

pubship-server retains the HTTP implementation for infrastructure you control. It refuses to start without PUBSHIP_SERVER_ALLOWED_EMAILS. Sign-in requires a signed Google ID token, a verified exact email match and nonce binding before any Google credentials are persisted. Removing an account from the allowlist invalidates its stored grants on next use. Legacy grants without verified identity must reconnect. Enrollment stays closed until the operator explicitly enables it.

There is no project-run Google-connected service. See the local-first decision and self-host setup.

Release notes

PubShip 0.24.2 improves tool descriptions and approval hints, and checks the same definitions across source and packaged installs. See the changelog for earlier versions. Source versions can precede package publication.

Development

Tool definition quality documents the TDQS 1.2 offline checks, reviewed heuristic findings and MCP contract regression coverage. Offline lint is not a model-scored grade.

sh
env -u GOOGLE_APPLICATION_CREDENTIALS uv sync --frozen --all-extras --group browser --group tdqsenv -u GOOGLE_APPLICATION_CREDENTIALS uv run --frozen --all-extras --group browser --group tdqs pytestenv -u GOOGLE_APPLICATION_CREDENTIALS uv run ruff check .env -u GOOGLE_APPLICATION_CREDENTIALS uv run ruff format --check .env -u GOOGLE_APPLICATION_CREDENTIALS uv run python scripts/generate_catalog.py --checkenv -u GOOGLE_APPLICATION_CREDENTIALS uv run python scripts/generate_verification.py --checkenv -u GOOGLE_APPLICATION_CREDENTIALS uv run python scripts/distribution_metadata.py --checkenv -u GOOGLE_APPLICATION_CREDENTIALS uv buildenv -u GOOGLE_APPLICATION_CREDENTIALS uv run python scripts/check_artifacts.py

Tests use fake providers. Browser tests require installed Playwright engines; backup integration tests require age. Record unavailable platform checks honestly. See contribution policy, release process, and security reporting.

Intended use

PubShip helps developers automate their own Google Play distribution work. It runs on your computer or on infrastructure you control, with your own Google credentials and Play Console permissions. The PubShip project does not run a hosted service and never receives your credentials. Use it only for apps and developer accounts that you or your organization own, and follow Google's Play Developer API Terms. Hosted PubShip instances run by others are not provided or endorsed by the PubShip project.

PubShip is an independent open-source project and is not affiliated with, endorsed by, or sponsored by Google. Google, Google Play and Android are trademarks of Google LLC.

License

PubShip is free software under the GNU Affero General Public License v3.0 only (AGPL-3.0-only). Copyright (C) 2026 Denys Vorobyov. For other license terms, contact [email protected].

Trademarks · Third-party notices · Website

来源:README.md,提交 25430e5

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

3
  1. v0.24.2最新Oct 12, 2026
  2. v0.24.1Oct 7, 2026
  3. v0.24.0Oct 7, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Ship 集成