Skip to main content
Glama
469,673 tools. Updated 2026-08-21 04:27

"semantic-release" matching MCP tools:

  • Check release readiness before publishing: verify release metadata, Trusted Publisher wiring, and required manual prep commands. Read-only, safe to run anytime.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Turn unreleased changelog fragments into a single release record. Moves fragment files into the release directory to finalize the changelog.
    MIT
  • Run a bounded release readiness check by verifying the release gate without publishing, pushing, tagging, or creating GitHub releases. Local stages use guarded commands; remote stages are read-only.
    MIT
  • List all releases from newest to oldest with progress summaries. Use to discover release coordinates when none are specified, such as checking what's in flight or the last release.
    MIT
  • Retrieve a release from a FOSSA release group with its license, obligation, revision, scan, and issue-count rollups. Choose sections to minimize API requests.
    Apache 2.0
  • Create a single GitHub release pinned to an exact target commit SHA after ensuring no tag or release exists. Performs one verified creation request with no retries.
    MIT
  • Create a FOSSA release group and its initial release in one call, bundling specified projects under a group title for organized tracking.
    Apache 2.0
  • Deletes a release label from the workspace palette, detaching it from all releases. To remove it from a single release without deleting, use the detach action instead.
    MIT