"semantic-release" matching MCP servers:

A read-only Model Context Protocol server that converts local Git changes and JUnit XML reports into traceable release evidence, risk findings, and a rollback checklist.

Combines GitHub releases from multiple repositories into a single product release note, with context sources for LLM synthesis.

Generates multi-platform release announcements (X, Reddit, GitHub profile, awesome-list, MCP directory) and a publish-readiness checklist for any public GitHub repository.

repo-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.

An MCP server that generates release intelligence from GitHub repository data, correlating commits, pull requests, issues, and contributors between two git refs to produce structured context for release notes, changelogs, and summaries.

Enables agents to list and download GitHub release assets using multi-mirror parallel ranged downloads with sha256 verification, using only the Python standard library. Works over stdio and is suited to restricted networks.

Generates comprehensive and formatted release notes from GitHub repositories, efficiently organizing commits by type and including detailed statistics using smart API usage.

Finds version and image tag from latest successful GitHub Actions workflow run and creates a Confluence release page documenting that information.

An MCP server that provides GitHub release information through the Model Context Protocol. It features a tool to retrieve the latest stable release version of any specified GitHub repository.

Enables automated semantic release notes, PR tagging, and changelog verification by integrating GitHub, GitLab, and Jira MCP servers.

Provides MCP tools to get a single-call snapshot of git and GitHub Actions CI status across all repositories in a folder, flag missing or stale architecture docs, write doc files, and detect release drift between source and release repositories.

Semantic git queries via MCP. Beyond git log — answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.

Generates commit messages, PR titles and descriptions, and release notes from git changes, with automatic domain detection for appropriate PR templates.

Enables generating conventional-commit–grouped release notes and CHANGELOG.md drafts from a local repository's git log between tags or commits, plus grouping commits by type. Reads only local git history via an MCP client such as Cursor or Claude Desktop.

Acts as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.

Enables AI assistants to turn local git history into answers about recent activity, file hotspots, change coupling, stale or already-merged branches, contributors, ref comparisons, and drafted release notes. It runs locally over stdio with a git subcommand allowlist, so it is read-only, works offline and without shell access, and is safe to auto-approve.

Enables AI agents to analyze public GitHub repositories directly through tools for repo health scoring, recent commit summaries, good first issue discovery, and semantic Q&A over docs and issues.

MCP server that detects semantic (non-textual) merge conflicts between Git branches using AST-level analysis. Catches incompatible changes that Git merges cleanly — signature changes, removed exports, parameter changes, interface breaks, and cross-file dependency conflicts.

Analyzes codebases from local directories, GitHub, and Azure DevOps, providing intelligent context to AI coding assistants through repository structure, critical files, and semantic maps.

Enables building structured release evidence by comparing two Git refs and correlating commits, merged pull requests, linked issues, labels, changed files, and contributors.