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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/efficjump/repro-capsule-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server