mcp-release-guardian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_repo_hygieneA | Validate that a repo contains the minimum release hygiene artifacts. Runs seven file/directory presence checks as defined in docs/V1_CONTRACT.md. No network access. Fail-closed. |
| check_version_alignmentA | Check that pyproject.toml [project].version matches an optional expected tag. No network access. Fail-closed when version cannot be detected. |
| generate_release_checklistA | Deterministically generate a release checklist based on local repo state. No network access. Reads pyproject.toml version, CI workflow presence, and bug template presence to tailor the checklist. |
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 3 tools
Each tool has a clear, distinct purpose: checking hygiene, version alignment, and generating a checklist. No overlap.
All tools follow a consistent verb_noun pattern with underscores (check_repo_hygiene, check_version_alignment, generate_release_checklist).
Three tools is fitting for a focused release guardian server, though the low count suggests a narrow scope.
The tools cover validation and checklist generation for releases, but lack a tool for applying fixes or executing the release itself.