GitHub Releases MCP Server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_release_infoA | Get detailed information about a specific GitHub release version. Supports semantic versioning formats (v1.0.0, @1.0.0, 1.0.0) and returns comprehensive release details including tag name, release title, publication date, and full release notes. Perfect for understanding what changed in a specific version or for documentation purposes. |
| github_releases_compareA | Compare changes between two GitHub release versions. Ideal for understanding what changed between versions, generating changelogs, or migration guides. Returns a chronological list of all releases between the two versions with their full release notes, making it perfect for analyzing the evolution of features, bug fixes, and breaking changes. Supports semantic versioning formats (v1.0.0, @1.0.0, 1.0.0). |
| github_releases_listA | List all GitHub releases for a repository with rich formatting and comprehensive details. Returns releases in chronological order with emojis for better readability (🔖 for versions, 🗓️ for dates, 📝 for descriptions). Perfect for getting an overview of a project's release history, finding the latest version, or monitoring release frequency. Supports pagination and filtering of pre-releases. |
| github_org_packagesA | List all packages for a GitHub organization. Returns detailed information about each package including its name, type, visibility, and repository details. Perfect for discovering available packages and their metadata in an organization. |
| github_repo_readmeA | Fetch the README file for a GitHub repository and return its plain text content. Useful for discovering package names and documentation in monorepos. |
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 5 tools
The first three tools are clearly about GitHub releases, but the last two (github_org_packages and github_repo_readme) are for entirely different purposes, creating confusion about the server's scope. An agent could mistakenly use these unrelated tools when trying to perform release operations.
The release tools follow a consistent 'github_release_*' pattern, but the other two tools break this pattern with 'github_org_packages' and 'github_repo_readme', leading to inconsistency in the naming scheme.
With 5 tools, the count is reasonable, but the inclusion of two unrelated tools makes the set seem thin for a dedicated releases server. A releases-focused set would benefit from more release-specific operations.
The release tools cover info, compare, and list, but lack essential CRUD operations like create, update, or delete releases. Additionally, the org packages and README tools are unrelated and do not fill any obvious gaps in the release workflow.