A
licenseB
qualityD
maintenanceProvides tools for accessing, comparing, and analyzing GitHub repository releases with rich formatting and detailed information.
5
10 npm
3
ISC
release-announcer-mcp
Related Servers
Alternatives to release-announcer-mcp
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-
- FlicenseNot gradedqualityCmaintenanceEnables automated semantic release notes, PR tagging, and changelog verification by integrating GitHub, GitLab, and Jira MCP servers.-
- AlicenseNot gradedqualityBmaintenanceScans repositories to produce a readiness score and actionable fixes across positioning, tryability, community, MCP, and monetization, plus generates launch assets and sponsor-tier ideas.10 npmMIT
- AlicenseAqualityDmaintenanceAnalyzes GitHub repositories using Gemini AI and generates comprehensive documentation including overviews, architecture guides, and file insights. Works with any MCP-compatible client.3MIT
- FlicenseAqualityAmaintenanceCombines GitHub releases from multiple repositories into a single product release note, with context sources for LLM synthesis.7-
TDQS
A4.1/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: fetch_repo_info retrieves raw repo data, check_publish_readiness runs a checklist, and build_announcement_brief creates a writing brief. There is no overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (e.g., fetch_repo_info, check_publish_readiness, build_announcement_brief). The naming is predictable and uniform.
Tool Count3/5
With only 3 tools, the server is at the lower bound of the typical 3-15 range. While the domain is specific, the tool set feels slightly thin for a release announcer, missing tools for actual posting or scheduling.
Completeness2/5
The tools cover fetching, readiness checking, and brief creation, but lack tools for final draft generation or posting. Important lifecycle steps like creating releases or publishing announcements are absent, leading to significant gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues