PRG MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Alternative port for HTTP transport | |
| MCP_PORT | No | Port for HTTP transport | |
| MCP_DATA_DIR | No | Data directory for MCP | |
| MCP_LOG_LEVEL | No | Log level for MCP | |
| MCP_TRANSPORT | No | Transport mode: stdio or http (default: stdio) | |
| MCP_CONFIG_DIR | No | Configuration directory for MCP | |
| PRG_SYNC_CONCURRENCY | No | Number of parallel downloads (default: 2, max: 8) | |
| PRG_SOURCE_TIMEOUT_MS | No | Timeout for single source request in milliseconds (default: 30000) | |
| PRG_MAX_DOWNLOAD_BYTES | No | Hard limit for download size in bytes (default: 4 GiB) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_statusA | Returns basic server health. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion with other tools.
With a single tool, there is no inconsistency to evaluate; the name 'health_status' is clear and follows snake_case convention.
The server has only one tool. While it serves a specific purpose, this is on the low end of the scale and may feel thin if the server is intended for broader use.
For a health check server, a single tool that returns server health is complete and covers the domain.