MCP servers · anselmoo

repo-release-tools MCP server for rrt release policy

MCP server that exposes most commands of the rrt CLI, which checks branch names, commit subjects and changelog policy in Git repositories and handles version bumps.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

repo-release-tools (rrt) is a config-driven set of branch and release helpers for Git repositories. Its CLI validates branch names, Conventional Commit subjects and changelog policy, and performs version bumps across one or more version files, including Python, Node, Go, Rust and .NET projects. The MCP server exposes most of these tools to an AI agent as typed JSON rather than terminal output. Commit subjects and branch names are passed as arguments, and mutating operations default to a dry-run preview. The lock readers and rrt_config return raw dictionaries.

It suits repositories where an agent such as Claude Code, Copilot, Cursor or Codex would otherwise edit version strings, branch names or changelog entries by hand. Using rrt keeps those changes within the repository's configured release policy.

To use it, add the agent instruction snippet from the publisher's guide to CLAUDE.md, AGENTS.md or .github/copilot-instructions.md, so the agent knows which tools to use. Then add a .mcp.json file at the repository root, which Claude Code reads on its next start. The repository must have rrt configured.

Limitations and requirements

The MCP server does not cover every rrt command. The docs, changelog lint and compare, drift, artifacts check, other --snapshot writes and all rrt-hooks subcommands are available only through the CLI, so agents need both. Grouped releases, changelog paths, release branches, lock commands, generated files and custom patterns require explicit configuration. The repository must have rrt configured.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Anselmoo/repo-release-tools

    Config-driven branch and release helpers for Git repositories

    v1.20.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026
repo-release-tools MCP server for rrt release policy | AI Gate Discover