get-app-info-by-shortcut
Get app info by app shortcut on PGYER
LABSCO SUMMARY
The build goes out without leaving the agent.
What it takes off you is the last step after a build: the package that just came out goes up, the app list confirms it landed, and a shortcut link someone sends back resolves to the details you would otherwise open the dashboard for.
What it is
A three-call server for PGYER, the app-distribution service: put a build up, list the apps on the account, and look one up from the short link it hands out.
What you get
- An app package uploaded from a local path
- The apps on your account, a page at a time
- One app's details resolved from its build shortcut URL
Requirements
npx on your PATH, and a PGYER API key in the environment — the server reads it when a tool runs, so the key has to be in place before the first call, not at install time.
Setup effort
One command plus a key — npx -y pgyer-mcp-server, then supply credentials
USE CASES
01
Getting a build out to testers
Hand it the package that just came out of the build and it goes up to PGYER; the app list afterwards confirms it landed rather than leaving you to check the dashboard.
02
Checking what is already up there
Page through the apps on the account to see what has been published and what has not, before uploading another build on top of one.
03
Resolving a share link someone sent you
Turn a PGYER shortcut URL into the app's details, so a link pasted into a chat becomes something you can act on without opening it.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
list-my-apps
List my apps on PGYER
upload-app
Upload app to PGYER
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
- npx on PATH
- PGYER_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y pgyer-mcp-serverMCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"pgyer": {
"command": "npx",
"args": [
"-y",
"pgyer-mcp-server"
],
"env": {
"PGYER_API_KEY": "<YOUR_PGYER_API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport stdio pgyer --env PGYER_API_KEY=<YOUR_PGYER_API_KEY> -- npx -y pgyer-mcp-serverCodex
CODEX · TERMINAL
codex mcp add pgyer --env PGYER_API_KEY=<YOUR_PGYER_API_KEY> -- npx -y pgyer-mcp-server
