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 整合