Labsco
MCP SERVER · OFFICIAL PROJECT

PGYER

by PGYER

Upload an app build to PGYER and read back what is already on the account.

Mobile & App Store ReleaseOfficial source
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