Penny
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PENNY_MODEL | Yes | Model identifier accepted by the endpoint | |
| PENNY_API_KEY | No | x-api-key credential | |
| PENNY_BASE_URL | Yes | Endpoint root before /v1/messages | |
| PENNY_ENV_FILE | No | Override settings-file location | |
| PENNY_AUTH_TYPE | No | bearer or api-key | bearer |
| PENNY_MAX_TURNS | No | Maximum Claude Code worker turns | 30 |
| PENNY_AUTH_TOKEN | No | Bearer token | |
| PENNY_CLAUDE_BIN | No | Claude Code executable | claude |
| PENNY_AGENT_TIMEOUT | No | Worker timeout in seconds | 1800 |
| PENNY_MCP_STATE_DIR | No | MCP submission registry | ~/.penny |
| PENNY_CUSTOM_HEADERS | No | Optional additional headers | |
| PENNY_MCP_ALLOWED_ROOTS | Yes | Path-separated MCP repository roots |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctorB | Check that the local execution environment is ready for a repository. |
| validate_planA | Validate a YAML execution manifest without starting any work. |
| submit_planA | Validate a manifest and queue a run. Returns immediately with a run_id. |
| get_runB | Return the current state of a submitted run. |
| cancel_runB | Request cancellation of an active run. |
| get_reportB | Return the execution report for a run. |
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 6 tools
Each tool addresses a distinct step in the execution workflow: environment readiness, plan validation, submission, status retrieval, cancellation, and reporting. There is no overlap or ambiguity between tool purposes.
Most tools follow a clear verb_noun pattern (validate_plan, submit_plan, get_run, cancel_run, get_report). The exception is 'doctor', which is a single verb, but its purpose is clear and the deviation is minor.
Six tools provide a focused yet complete coverage of the run lifecycle without unnecessary redundancy. The count feels well-scoped for the server's stated purpose.
The toolset covers environment setup, plan validation, run submission, status monitoring, cancellation, and report retrieval—all essential operations for executing and managing repo runs. No critical gaps are apparent.