mcp-release-guardian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
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/curtis-d-williams/mcp-release-guardian'
If you have feedback or need assistance with the MCP directory API, please join our Discord server