GitHub Releases MCP Server
Related Servers
Alternatives to GitHub Releases MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceGenerates comprehensive and formatted release notes from GitHub repositories, efficiently organizing commits by type and including detailed statistics using smart API usage.33-
- AlicenseAqualityAmaintenanceGenerates multi-platform release announcements (X, Reddit, GitHub profile, awesome-list, MCP directory) and a publish-readiness checklist for any public GitHub repository.3MIT
- AlicenseAqualityBmaintenanceEnables building structured release evidence by comparing two Git refs and correlating commits, merged pull requests, linked issues, labels, changed files, and contributors.356 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only tools to search public GitHub repositories, retrieve repository details, READMEs, contributors, and commit activity, and compare up to 10 repositories side by side.MIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to access GitHub repository and user statistics, including repo info, user profiles, contributors, issues, and repository search.MIT
- AlicenseAqualityDmaintenanceEnables querying GitHub repositories for pull requests, commits, and comparisons to understand code changes.59 npmApache 2.0
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.