Repro Capsule MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPRO_CAPSULE_ALLOWED_ROOTS | Yes | Allowed project roots. The server will refuse to access projects outside these paths. |
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 |
|---|---|
| start_caseA | Create a versioned case after constraining the project root and redacting the report. |
| list_casesA | List persisted reproduction cases without reading project files or running commands. |
| get_case | Return the case, latest profile, selected artifacts, analyses, and run evidence. |
| inspect_project | Dynamically discover project manifests, commands, environment names, and Git evidence. |
| analyze_caseB | Form evidence-cited hypotheses with host sampling, or return an explicit fallback. |
| add_artifactB | Add one reviewed project file as redacted text or a binary hash-only record. |
| plan_commandB | Create a non-shell execution plan and one-time approval token from project evidence. |
| execute_planA | Consume one approval token and record bounded, redacted command output. |
| compare_runsA | Compare exit status, expectation match, and redacted output hashes for two runs. |
| export_capsuleA | Create a ZIP containing only persisted case metadata and reviewed artifact contents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| reproduce_prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a distinct phase of the reproduction workflow: case creation, listing, analysis, artifact addition, command planning, execution, run comparison, and export. Even the closely related plan_command and execute_plan pair is clearly separated by planning versus consuming a token for execution.
All eight tool names follow a consistent verb_noun snake_case pattern such as start_case, add_artifact, execute_plan, and export_capsule. The action and target are predictable across the entire set.
Eight tools is a well-scoped size for a reproduction capsule server. Each tool provides a necessary capability in the lifecycle without redundancy or bloat.
The tool surface covers the core workflow end-to-end: create/list/analyze cases, add artifacts, plan and execute commands, compare runs, and export. Minor gaps exist around direct inspection or removal of individual artifacts/runs, but agents can work around these using the existing analysis and export tools.