release-announcer-mcp
Related Servers
Alternatives to release-announcer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables an agent to take a public GitHub repository for an MCP server and get it listed across every MCP directory, by reading the repo to draft a listing, publishing to the official registry, opening pull requests on awesome lists and catalogs from the user's own account, and preparing web forms. It also checks existing listings and re-syncs or flags them when a new version ships.MIT
- AlicenseBqualityDmaintenanceProvides tools for accessing, comparing, and analyzing GitHub repository releases with rich formatting and detailed information.512 npm3ISC
- 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 gradedqualityBmaintenanceEnables MCP-compatible clients to audit public GitHub repositories and receive structured launch-readiness reports with evidence-backed findings, reproducible scoring, and ready-to-paste launch copy.1,019 npm3MIT
- AlicenseAqualityAmaintenancerepo-release-tools mcp-server automates the software release process by managing version bumps, changelog generation, and releases. It streamlines repository maintenance by handling repetitive release tasks directly through your AI assistant.27326 PyPI1MIT
TDQS
Scored across 3 tools
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.
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.
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.
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.