mcp-protocol mobile app upload with multi-format support, paginated app inventory querying with filtering, app detail retrieval by shortcut identifier, mcp server lifecycle management with dual runtime support, pgyer api authentication and request abstraction, claude app and vscode mcp client integration configuration

PGYER

MCP ServerFree

** - MCP Server for [PGYER](https://www.pgyer.com/) platform, supports uploading, querying apps, etc.

Open Source

signed passport verify →

/ 100

6 capabilities

Best for: mcp-protocol mobile app upload with multi-format support, paginated app inventory querying with filtering, app detail retrieval by shortcut identifier
Type: MCP Server · Free
Score: 28/100
Best alternative: AWS MCP Servers
Agent-compatible: Yes — MCP protocol

Capabilities6 decomposed

mcp-protocol mobile app upload with multi-format support

Medium confidence

Enables uploading iOS IPA and Android APK files to PGYER through the Model Context Protocol via a PGYERAppUploader component that orchestrates multi-step file transmission. The implementation uses StdioServerTransport for process-based communication with MCP clients (Claude App, VSCode), abstracting PGYER's HTTP API behind a standardized tool interface that handles authentication via PGYER_API_KEY environment variable and manages file streaming to remote servers.

Solves for

I want to upload a compiled iOS or Android app binary to PGYER distribution without leaving my IDE or Claude conversationI need to automate app uploads as part of a CI/CD pipeline or development workflowI want to integrate app distribution into an AI agent that can manage releases programmatically

Best for

Mobile development teams using Claude or VSCode as their primary development environment

DevOps engineers building automated mobile app release pipelines

AI agent builders integrating app distribution into autonomous workflows

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable set in deployment context

MCP-compatible client (Claude App, VSCode with MCP extension, or compatible platform)

Limitations

Requires pre-compiled IPA/APK files — does not perform build compilation itself

File upload latency depends on network bandwidth and file size; no built-in resumable upload for large files

Single-threaded upload processing — concurrent uploads must be queued sequentially

What makes it unique

Implements MCP server pattern specifically for PGYER's upload workflow, using StdioServerTransport for bidirectional communication with IDE clients rather than REST webhooks, enabling real-time upload progress and error handling within Claude or VSCode without context switching

vs alternatives

Tighter IDE integration than PGYER's web dashboard or REST API clients because it operates as a native MCP tool within Claude/VSCode, reducing friction for developers who live in those environments

paginated app inventory querying with filtering

Medium confidence

Provides list-my-apps tool that queries the authenticated user's uploaded applications from PGYER with pagination support, implemented via makePGYERRequest helper that abstracts HTTP request construction and authentication. Returns structured app metadata (IDs, versions, upload dates, download counts) enabling developers to inspect their app distribution portfolio programmatically without accessing the PGYER web dashboard.

Solves for

I want to see all apps I've uploaded to PGYER and their current status from within Claude or VSCodeI need to programmatically fetch a list of my distributed apps to determine which version is latestI want to build a dashboard or monitoring tool that pulls my app inventory from PGYER

Best for

Mobile developers managing multiple app versions across iOS and Android

Release managers tracking which builds are currently distributed

AI agents that need to query app state before deciding on next distribution steps

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable

MCP-compatible client with tool-calling support

Limitations

Pagination is manual — requires explicit page number parameters; no automatic cursor-based iteration

Returns only basic app metadata — does not include detailed analytics or download statistics

No filtering by app type, version, or date range — returns all apps in chronological order only

What makes it unique

Exposes PGYER's app listing API as a stateless MCP tool with pagination parameters, using makePGYERRequest abstraction to handle authentication and response parsing, enabling Claude or VSCode to query app state without requiring users to manually construct HTTP requests

vs alternatives

More accessible than PGYER's web UI for programmatic queries because it returns structured JSON directly into Claude context, enabling AI agents to reason about app inventory and make distribution decisions autonomously

app detail retrieval by shortcut identifier

Medium confidence

Implements get-app-info-by-shortcut tool that fetches detailed metadata for a specific PGYER app using its shortcut identifier (a unique slug assigned by PGYER). Uses makePGYERRequest helper to construct authenticated API calls, returning comprehensive app information including download URL, QR code, version history, and distribution metrics without requiring knowledge of internal app IDs.

Solves for

I have a PGYER app shortcut URL and want to retrieve its full metadata programmaticallyI need to generate a QR code or download link for a specific distributed appI want to verify app details (version, size, platform) before sharing with testers

Best for

QA teams distributing test builds to stakeholders via shortcut links

Developers generating shareable app distribution links for beta testing

Automation scripts that need to resolve app shortcuts to full metadata

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable

MCP-compatible client

Limitations

Requires exact shortcut identifier — no fuzzy matching or search by app name

Does not return download statistics or user feedback — only static app metadata

Shortcut identifiers are immutable — cannot be customized or changed after app upload

What makes it unique

Provides shortcut-based app lookup (human-readable identifier) rather than requiring internal app IDs, making it easier for non-technical stakeholders to reference apps and enabling Claude to resolve app shortcuts mentioned in natural language into full metadata

vs alternatives

More user-friendly than PGYER's app ID-based API because shortcut identifiers are the same ones users share in URLs, reducing the need for ID translation and enabling Claude to work directly with user-provided shortcut links

mcp server lifecycle management with dual runtime support

Medium confidence

Manages the PGYER MCP server initialization, tool registration, and transport layer configuration supporting both Node.js direct execution and Docker containerized deployment. The server entry point at build/index.js initializes StdioServerTransport for stdio-based communication with MCP clients, registers the three core tools (upload-app, list-my-apps, get-app-info-by-shortcut), and handles authentication setup via environment variables, enabling seamless integration with Claude App and VSCode.

Solves for

I want to deploy the PGYER MCP server in my local development environment or production infrastructureI need to configure the server to work with Claude App or VSCode without manual HTTP endpoint managementI want to ensure the server starts correctly and handles tool registration automatically

Best for

DevOps engineers deploying MCP servers in containerized environments

Individual developers setting up local MCP server instances for IDE integration

Teams standardizing on MCP for tool integration across multiple platforms

Requires

Node.js 20+ (for direct execution) OR Docker (for containerized deployment)

PGYER_API_KEY environment variable set before server startup

MCP-compatible client configured to spawn the server process (Claude App or VSCode with MCP extension)

Limitations

Stdio transport is process-based — requires parent process to manage server lifecycle; no built-in process restart on crash

Single server instance per process — horizontal scaling requires multiple process instances with load balancing

No built-in logging or observability — errors are written to stderr; requires external log aggregation for production

What makes it unique

Implements MCP server pattern with dual deployment modes (Node.js and Docker) using StdioServerTransport for process-based communication, enabling tight integration with IDE clients without requiring HTTP server setup or port management, and supporting both development and production deployments with identical tool interfaces

vs alternatives

Simpler deployment than REST API servers because stdio transport eliminates port binding, firewall configuration, and HTTP routing complexity; Docker support enables production-grade containerization without custom server infrastructure

pgyer api authentication and request abstraction

Medium confidence

Provides makePGYERRequest helper function that abstracts PGYER API authentication and HTTP request construction, handling API key injection, request signing, and response parsing for all tool implementations. Centralizes authentication logic to ensure consistent credential handling across upload, query, and detail-retrieval operations, with environment variable-based API key management enabling secure credential injection without hardcoding.

Solves for

I want to ensure all API calls to PGYER are authenticated consistently without duplicating auth logicI need to handle PGYER API errors and responses uniformly across different tool implementationsI want to manage API credentials securely via environment variables rather than configuration files

Best for

MCP server developers integrating with PGYER or similar API-based services

Teams standardizing on environment variable-based credential management

Projects requiring consistent error handling and response parsing across multiple API endpoints

Requires

PGYER_API_KEY environment variable set in server process

Network connectivity to PGYER API endpoints

Valid PGYER account with API access enabled

Limitations

API key stored in environment variable — vulnerable to process memory inspection; no secrets vault integration

No request caching — every tool invocation triggers a fresh API call; no built-in response memoization

No retry logic — failed requests are not automatically retried; caller must implement retry strategy

What makes it unique

Centralizes PGYER API authentication in a single makePGYERRequest helper rather than duplicating auth logic across tools, using environment variable injection for API keys and providing consistent error handling and response parsing for all API interactions

vs alternatives

More maintainable than inline API calls because authentication logic is centralized, reducing the risk of credential leaks or inconsistent error handling across multiple tool implementations

claude app and vscode mcp client integration configuration

Medium confidence

Provides standardized configuration patterns for integrating the PGYER MCP server with Claude App and VSCode through their respective MCP server configuration mechanisms. Claude App uses mcpServers object in settings with Node.js or Docker execution modes, while VSCode uses mcp.servers configuration with input prompts for secure API key entry and workspace folder mounting. Both integration paths support environment variable injection and process spawning without requiring manual HTTP endpoint configuration.

Solves for

I want to add the PGYER MCP server to my Claude App so I can upload and manage apps in conversationsI need to configure VSCode to use the PGYER MCP server as a native tool within the editorI want to ensure the API key is securely provided without hardcoding it in configuration files

Best for

Claude App users who want native PGYER integration in conversations

VSCode users managing mobile apps and wanting IDE-native distribution tools

Teams standardizing on MCP for tool integration across development platforms

Requires

Claude App (latest version with MCP support) OR VSCode with MCP extension installed

PGYER_API_KEY available for secure entry (environment variable or manual input)

Node.js 20+ installed locally (for Node.js execution mode) OR Docker installed (for Docker mode)

Limitations

Claude App integration requires Claude App version with MCP support — not available in older versions

VSCode integration requires MCP extension installation — adds dependency on third-party extension

API key entry in VSCode is manual via input prompt — no automatic credential retrieval from system keychains

What makes it unique

Provides platform-specific integration patterns for Claude App (mcpServers) and VSCode (mcp.servers) with secure API key handling via input prompts, enabling users to add PGYER tools to their development environment without manual HTTP configuration or environment variable management in config files

vs alternatives

More secure and user-friendly than REST API integration because it uses input prompts for API key entry (avoiding hardcoding in config) and eliminates the need for port binding or HTTP endpoint management, making setup accessible to non-technical users

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with PGYER, ranked by overlap. Discovered automatically through the match graph.

MCP Server26

google-play-mcp

MCP server: google-play-mcp

app metadata enrichment and structured extractiongoogle play store app search and metadata retrievaldeveloper profile and app portfolio retrieval

3 shared capabilities

MCP Server36

@heroku/mcp-server

Heroku Platform MCP Server

application metadata and resource querying via mcp resourcesmulti-app batch operations via mcp tool composition

2 shared capabilities

MCP Server41

apktool-mcp-server

A MCP Server for APK Tool (Part of Android Reverse Engineering MCP Suites)

stdio-based mcp transport and client communicationmcp tool schema exposure and capability discovery

2 shared capabilities

MCP Server29

PulseMCP

** ([API](https://www.pulsemcp.com/api)) - Community hub & weekly newsletter for discovering MCP servers, clients, articles, and news by **[Tadas Antanavicius](https://github.com/tadasant)**, **[Mike Coughlin](https://github.com/macoughl)**, and **[Ravina Patel](https://github.com/ravinahp)**

rest api for programmatic mcp server discovery and metadata retrievalmcp server discovery and cataloging

2 shared capabilities

CLI Tool26

mcp-cli

** a cli inspector for MCP servers

multi-protocol mcp server connection with unified interfaceinteractive mcp primitive discovery and enumeration

2 shared capabilities

MCP Server38

example-remote-server

A hosted version of the Everything server - for demonstration and testing purposes, hosted at https://example-server.modelcontextprotocol.io/mcp

13 example mcp applications with interactive ui integration

1 shared capability

Best For

✓Mobile development teams using Claude or VSCode as their primary development environment
✓DevOps engineers building automated mobile app release pipelines
✓AI agent builders integrating app distribution into autonomous workflows
✓Mobile developers managing multiple app versions across iOS and Android
✓Release managers tracking which builds are currently distributed
✓AI agents that need to query app state before deciding on next distribution steps
✓QA teams distributing test builds to stakeholders via shortcut links
✓Developers generating shareable app distribution links for beta testing

Known Limitations

⚠Requires pre-compiled IPA/APK files — does not perform build compilation itself
⚠File upload latency depends on network bandwidth and file size; no built-in resumable upload for large files
⚠Single-threaded upload processing — concurrent uploads must be queued sequentially
⚠No local file validation before upload — relies on PGYER API to reject invalid formats
⚠Pagination is manual — requires explicit page number parameters; no automatic cursor-based iteration
⚠Returns only basic app metadata — does not include detailed analytics or download statistics

Requirements

Node.js 20+ or Docker runtimeValid PGYER_API_KEY environment variable set in deployment contextMCP-compatible client (Claude App, VSCode with MCP extension, or compatible platform)IPA file (iOS) or APK file (Android) already compiled and available locally or accessible via file pathValid PGYER_API_KEY environment variableMCP-compatible client with tool-calling supportAt least one app previously uploaded to PGYER accountMCP-compatible client

Input / Output

Accepts: file path (string pointing to local IPA or APK), optional metadata (app name, version, release notes as structured parameters), page number (integer, optional, defaults to 1), page size (integer, optional, defaults to PGYER API default), shortcut (string, required) — the unique PGYER app shortcut identifier, environment variables: PGYER_API_KEY (required), optional: server configuration parameters (if supported by MCP client), API endpoint path (string), request parameters (object with query or body fields), HTTP method (GET, POST, etc.), Claude App settings: mcpServers configuration object with command and args, VSCode settings: mcp.servers configuration with inputPrompts for API key

Produces: structured JSON response with upload status, app ID, download URL, QR code, error messages with PGYER API error codes if upload fails, JSON array of app objects with fields: appId, appName, appVersion, uploadTime, downloadCount, shortcutUrl, pagination metadata: currentPage, totalPages, totalApps, JSON object with app metadata: appName, appVersion, platform (iOS/Android), fileSize, downloadUrl, qrCodeUrl, uploadTime, downloadCount, error response if shortcut not found or access denied, stdio stream with MCP protocol messages, tool availability signals to MCP client, error messages to stderr if initialization fails, parsed JSON response from PGYER API, error object with PGYER error code and message if request fails, MCP server process spawned by client, tool availability signals in Claude or VSCode UI, error messages if server fails to start or authenticate

UnfragileRank

Adoption5%(25% weight)

Quality37%(25% weight)

Ecosystem40%(15% weight)

Match Graph25%(23% weight)

Freshness52%(12% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit PGYER→

Repository Details

About

** - MCP Server for [PGYER](https://www.pgyer.com/) platform, supports uploading, querying apps, etc.

Alternatives to PGYER

AWS MCP Servers59MCP Server

AWS Labs' official MCP suite — docs, CDK, Bedrock KB, cost, Lambda and more as agent tools.

Compare →

Zapier MCP62MCP Server

Zapier's hosted MCP — 8,000+ app integrations exposed as allowlisted agent tools.

Compare →

Hugging Face MCP Server61MCP Server

Official Hugging Face MCP — search models/datasets/Spaces/papers and call Spaces as tools.

Compare →

Atlassian Remote MCP Server61MCP Server

Atlassian's official hosted MCP — Jira + Confluence with OAuth, permission-bounded agent access.

Compare →

See all alternatives to PGYER→

Are you the builder of PGYER?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Continue with GitHub or claim by email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities6 decomposed

mcp-protocol mobile app upload with multi-format support

Medium confidence

Solves for

Best for

Mobile development teams using Claude or VSCode as their primary development environment

DevOps engineers building automated mobile app release pipelines

AI agent builders integrating app distribution into autonomous workflows

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable set in deployment context

MCP-compatible client (Claude App, VSCode with MCP extension, or compatible platform)

Limitations

Requires pre-compiled IPA/APK files — does not perform build compilation itself

File upload latency depends on network bandwidth and file size; no built-in resumable upload for large files

Single-threaded upload processing — concurrent uploads must be queued sequentially

What makes it unique

vs alternatives

Tighter IDE integration than PGYER's web dashboard or REST API clients because it operates as a native MCP tool within Claude/VSCode, reducing friction for developers who live in those environments

paginated app inventory querying with filtering

Medium confidence

Solves for

Best for

Mobile developers managing multiple app versions across iOS and Android

Release managers tracking which builds are currently distributed

AI agents that need to query app state before deciding on next distribution steps

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable

MCP-compatible client with tool-calling support

Limitations

Pagination is manual — requires explicit page number parameters; no automatic cursor-based iteration

Returns only basic app metadata — does not include detailed analytics or download statistics

No filtering by app type, version, or date range — returns all apps in chronological order only

What makes it unique

vs alternatives

app detail retrieval by shortcut identifier

Medium confidence

Solves for

Best for

QA teams distributing test builds to stakeholders via shortcut links

Developers generating shareable app distribution links for beta testing

Automation scripts that need to resolve app shortcuts to full metadata

Requires

Node.js 20+ or Docker runtime

Valid PGYER_API_KEY environment variable

MCP-compatible client

Limitations

Requires exact shortcut identifier — no fuzzy matching or search by app name

Does not return download statistics or user feedback — only static app metadata

Shortcut identifiers are immutable — cannot be customized or changed after app upload

What makes it unique

vs alternatives

mcp server lifecycle management with dual runtime support

Medium confidence

Solves for

Best for

DevOps engineers deploying MCP servers in containerized environments

Individual developers setting up local MCP server instances for IDE integration

Teams standardizing on MCP for tool integration across multiple platforms

Requires

Node.js 20+ (for direct execution) OR Docker (for containerized deployment)

PGYER_API_KEY environment variable set before server startup

MCP-compatible client configured to spawn the server process (Claude App or VSCode with MCP extension)

Limitations

Stdio transport is process-based — requires parent process to manage server lifecycle; no built-in process restart on crash

Single server instance per process — horizontal scaling requires multiple process instances with load balancing

No built-in logging or observability — errors are written to stderr; requires external log aggregation for production

What makes it unique

vs alternatives

pgyer api authentication and request abstraction

Medium confidence

Solves for

Best for

MCP server developers integrating with PGYER or similar API-based services

Teams standardizing on environment variable-based credential management

Projects requiring consistent error handling and response parsing across multiple API endpoints

Requires

PGYER_API_KEY environment variable set in server process

Network connectivity to PGYER API endpoints

Valid PGYER account with API access enabled

Limitations

API key stored in environment variable — vulnerable to process memory inspection; no secrets vault integration

No request caching — every tool invocation triggers a fresh API call; no built-in response memoization

No retry logic — failed requests are not automatically retried; caller must implement retry strategy

What makes it unique

vs alternatives

More maintainable than inline API calls because authentication logic is centralized, reducing the risk of credential leaks or inconsistent error handling across multiple tool implementations

claude app and vscode mcp client integration configuration

Medium confidence

Solves for

Best for

Claude App users who want native PGYER integration in conversations

VSCode users managing mobile apps and wanting IDE-native distribution tools

Teams standardizing on MCP for tool integration across development platforms

Requires

Claude App (latest version with MCP support) OR VSCode with MCP extension installed

PGYER_API_KEY available for secure entry (environment variable or manual input)

Node.js 20+ installed locally (for Node.js execution mode) OR Docker installed (for Docker mode)

Limitations

Claude App integration requires Claude App version with MCP support — not available in older versions

VSCode integration requires MCP extension installation — adds dependency on third-party extension

API key entry in VSCode is manual via input prompt — no automatic credential retrieval from system keychains

What makes it unique

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to PGYER

AWS MCP Servers59MCP Server

AWS Labs' official MCP suite — docs, CDK, Bedrock KB, cost, Lambda and more as agent tools.

Compare →

Zapier MCP62MCP Server

Zapier's hosted MCP — 8,000+ app integrations exposed as allowlisted agent tools.

Compare →

Hugging Face MCP Server61MCP Server

Official Hugging Face MCP — search models/datasets/Spaces/papers and call Spaces as tools.

Compare →

Atlassian Remote MCP Server61MCP Server

Atlassian's official hosted MCP — Jira + Confluence with OAuth, permission-bounded agent access.

Compare →

See all alternatives to PGYER→

PGYER

Capabilities6 decomposed

mcp-protocol mobile app upload with multi-format support

paginated app inventory querying with filtering

app detail retrieval by shortcut identifier

mcp server lifecycle management with dual runtime support

pgyer api authentication and request abstraction

claude app and vscode mcp client integration configuration

Related Artifactssharing capabilities

google-play-mcp

@heroku/mcp-server

apktool-mcp-server

PulseMCP

mcp-cli

example-remote-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

About

Categories

Alternatives to PGYER

Are you the builder of PGYER?

Get the weekly brief

Data Sources

PGYER

Capabilities6 decomposed

mcp-protocol mobile app upload with multi-format support

paginated app inventory querying with filtering

app detail retrieval by shortcut identifier

mcp server lifecycle management with dual runtime support

pgyer api authentication and request abstraction

claude app and vscode mcp client integration configuration

Related Artifactssharing capabilities

google-play-mcp

@heroku/mcp-server

apktool-mcp-server

PulseMCP

mcp-cli

example-remote-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Repository Details

About

Categories

Alternatives to PGYER

Are you the builder of PGYER?

Get the weekly brief

Data Sources