PGYER

io.github.PGYERPublished by GitHub account PGYERv2.0.0Updated Oct 29, 2026

Upload Android, iOS and HarmonyOS apps to PGYER and manage their apps and versions.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Uploads Android, iOS and HarmonyOS test builds to PGYER and lets an assistant list apps and versions, fetch download pages and QR codes, and adjust app…

What you can do
  • Upload local .apk, .ipa or .hap packages to PGYER and get back the download page and QR code URL
  • Check the processing status of an upload by build key, optionally waiting for it
  • List the account's apps and an app's historical versions, and read app details by app key or shortcut
  • Mark or unmark a build as the latest version
  • Change download page and installation settings, with a dry run option
When to use it
Useful when you build mobile or HarmonyOS apps locally and want an assistant to publish test builds to PGYER and hand testers a download link or QR code, or to look up existing apps and versions without opening the web console.
Requirements
Runs locally over stdio via npx (Node.js 20.19 or newer). Needs a PGYER API key, read from the PGYER_API_KEY environment variable or from credentials saved by the PGYER CLI login. Network access to PGYER is required.
Before you install
The API key is a credential: keep it out of shared config files where possible. Uploading publishes a build and returns a public download page, so check what is being shared. set_latest_version and update_app_settings change existing app state; the server itself advises confirming with the user first. No delete tools exist and install passwords are not returned.

Installation

In SourceWeft

  1. Open PGYER in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

PGYER MCP Server

English | 中文

蒲公英(PGYER)的 MCP(Model Context Protocol)服务器。在 Claude、Cursor、VS Code、Codex 等 AI 客户端里直接上传 Android(.apk)、iOS(.ipa)和鸿蒙(.hap)安装包,查询应用与历史版本,修改应用设置。

[Claude Screenshot]

从 2.0 开始,本包只是一个启动器:服务器本身由蒲公英命令行工具 @pgyer/cli(pgyer mcp)提供,两者的工具和行为完全相同。原有的 npx -y pgyer-mcp-server 配置无需修改。

准备

服务器优先读取环境变量 PGYER_API_KEY;没有设置时,使用 pgyer auth login 保存在本机的凭证。

配置

Claude Code

bash
claude mcp add pgyer --env PGYER_API_KEY=<your_pgyer_api_key> -- npx -y pgyer-mcp-server

Claude Desktop

编辑 claude_desktop_config.json(设置 → 开发者 → 编辑配置):

json
{  "mcpServers": {    "pgyer": {      "command": "npx",      "args": ["-y", "pgyer-mcp-server"],      "env": { "PGYER_API_KEY": "<your_pgyer_api_key>" }    }  }}

Cursor

在 ~/.cursor/mcp.json(全局)或项目内的 .cursor/mcp.json 中添加:

json
{  "mcpServers": {    "pgyer": {      "command": "npx",      "args": ["-y", "pgyer-mcp-server"],      "env": { "PGYER_API_KEY": "<your_pgyer_api_key>" }    }  }}

VS Code

一键添加:

bash
code --add-mcp '{"name":"pgyer","command":"npx","args":["-y","pgyer-mcp-server"],"env":{"PGYER_API_KEY":"<your_pgyer_api_key>"}}'

或在项目的 .vscode/mcp.json 中添加(启动时提示输入 API Key,不会写进文件):

json
{  "inputs": [    { "type": "promptString", "id": "pgyer-api-key", "description": "PGYER API Key", "password": true }  ],  "servers": {    "pgyer": {      "type": "stdio",      "command": "npx",      "args": ["-y", "pgyer-mcp-server"],      "env": { "PGYER_API_KEY": "${input:pgyer-api-key}" }    }  }}

Codex

bash
codex mcp add pgyer --env PGYER_API_KEY=<your_pgyer_api_key> -- npx -y pgyer-mcp-server

或编辑 ~/.codex/config.toml。Codex 默认的工具超时是 60 秒,上传较大的安装包时请调大:

toml
[mcp_servers.pgyer]command = "npx"args = ["-y", "pgyer-mcp-server"]env = { PGYER_API_KEY = "<your_pgyer_api_key>" }tool_timeout_sec = 900

已全局安装 @pgyer/cli 并执行过 pgyer auth login 时,也可以把命令换成 pgyer mcp,并省略 PGYER_API_KEY。

工具

工具作用只读覆盖已有状态
upload_app上传 .apk/.ipa/.hap 并等待蒲公英处理完成,返回下载页地址、二维码、版本号等;支持安装方式、安装密码、更新说明、应用介绍、安装有效期、渠道短链接、海外/国内上传和处理超时;客户端提供 progressToken 时发送上传和处理进度否否
get_upload_status按 buildKey 查询上传的处理结果(upload_app 处理超时后使用),可设置等待时间是否
list_apps分页列出账号下的应用及其最新版本是否
get_app按 appKey 或短链接(也可以是完整的下载页地址)查询应用详情,可指定历史版本是否
list_versions按 appKey 或短链接分页列出历史版本是否
set_latest_version设置或取消某个版本的「最新版本」标记否是
update_app_settings修改短链接、安装方式与密码、安装有效期、下载页语言、版本号来源、自动同步和版权显示;未指定的设置保持不变,支持 dryRun否是
  • 上传只发送你指定的设置,未指定的设置保持应用当前的值
  • 不提供删除应用或版本的工具,也不会返回安装密码
  • 主域名 www.pgyer.com 无法访问时,自动改用 www.xcxwo.com、www.pgyerapp.com
  • API Key 只在 HTTPS 请求正文中发送,不会出现在 URL 里

从 1.x 升级

2.0 的工具名称改为 snake_case 并增加了新工具。如果你的提示词或客户端的工具白名单写了旧名称,请相应修改:

1.x2.0
upload-appupload_app(新增全部上传设置与进度通知)
list-my-appslist_apps
get-app-info-by-shortcutget_app(参数 shortcut)

工具的返回结果也改为整理后的结构化数据,不再原样返回 API 响应。1.x 把 API Key 放在查询上传结果的 URL 中,2.0 已修复。

Docker

bash
docker build -t pgyer-mcp-server .docker run -i --rm -e PGYER_API_KEY=<your_pgyer_api_key> pgyer-mcp-server

开发与发布

服务器代码在 PGYER/pgyer-cli 的 src/mcp/ 中,问题与改进请提交到该仓库。本仓库只包含启动器、MCP Registry 元数据(server.json)和文档。发布步骤见 RELEASING.md。

许可证

MIT

Source: README.md at commit 7ac4f8a

Tools

7

upload_app

Upload app to PGYER

Upload an Android (.apk), iOS (.ipa) or HarmonyOS (.hap) package from this machine to PGYER and wait until PGYER has processed it. Returns the published build with its download page URL (share it with testers) and QR code image URL. PGYER matches the package to an existing app by its package identifier, or creates the app on the first upload. Only the settings you pass are changed; the app keeps its current values for the rest. Large files can take several minutes. If PGYER is still processing when processingTimeoutSeconds ends, the result has status "processing" and a buildKey: call get_upload_status with it later instead of uploading again.

ParametersoverseafilePathrequiredpassworddescriptioninstallTypeinstallEndDatechannelShortcutinstallStartDateupdateDescriptionprocessingTimeoutSeconds

get_upload_status

Get upload status

Check whether PGYER has finished processing an upload, by the buildKey that upload_app returned with status "processing". Returns the published build with its download page URL once it is ready. Set waitSeconds to keep checking for up to that long.

ParametersbuildKeyrequiredwaitSeconds

list_apps

List apps

List the apps in the PGYER account, 20 per page, with each app's latest version and download page. Use page to see more; pageCount tells how many pages there are.

Parameterspage

get_app

Get app details

Get an app's details by appKey or by shortcut (or a full https://www.pgyer.com/<shortcut> URL): latest version, download page, QR code, install type, install period and download page settings. Pass buildKey together with appKey to get one specific historical build. The install password is never returned.

ParametersappKeybuildKeyshortcut

list_versions

List app versions

List the uploaded versions (builds) of an app, newest first, by appKey or shortcut. isLatest shows which build carries PGYER's latest-version mark. Use page to see older builds.

ParameterspageappKeyshortcut

set_latest_version

Set latest version

Mark a build as the latest version of its app (latest: true, the default), or remove the latest-version mark from it (latest: false). Get build keys from list_versions. Ask the user before changing which build is marked latest.

ParameterslatestbuildKeyrequired

update_app_settings

Update app settings

Change an app's download page and installation settings. Only the settings you pass change; the rest keep their current values. Use dryRun to see which settings would change without saving.

ParametersappKeyrequireddryRunautoSynclanguagepasswordshortcutinstallTypeversionSourceinstallEndDateinstallStartDateshowPgyerCopyrightremoveInstallPeriod

Version history

1
  1. v2.0.0LatestOct 21, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts