What it does
Config-driven branch and release helpers for Git repositories
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 12/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 24/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Repo Release Tools. Follow https://mcp.popnx.com/i/anselmoo-repo-release-tools.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Repo Release Tools for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "repo-release-tools": { "command": "uvx", "args": [ "repo-release-tools" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Repo Release Tools tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "repo-release-tools": { "command": "uvx", "args": [ "repo-release-tools" ] } } }Quit Claude and open it again
Try it
Use Repo Release Tools and tell me what you can do for me, then show me one thing✓ If Claude says it is using Repo Release Tools or shows a Repo Release Tools tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Repo Release Tools yet
Repo Release Tools runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Repo Release Tools
- Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Repo Release Tools for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user repo-release-tools -- uvx repo-release-tools 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Repo Release Tools tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user repo-release-tools -- uvx repo-release-toolsType /mcp in Claude Code
You should see Repo Release Tools listed as connected
Try it
Use Repo Release Tools and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Repo Release Tools or shows a Repo Release Tools tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Repo Release Tools for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "repo-release-tools": { "command": "uvx", "args": [ "repo-release-tools" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Repo Release Tools tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in Cursor in Agent mode
Try it
Use Repo Release Tools and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Repo Release Tools or shows a Repo Release Tools tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Repo Release Tools for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "repo-release-tools": { "type": "stdio", "command": "uvx", "args": [ "repo-release-tools" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Repo Release Tools tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in VS Code in Agent mode
Try it
Use Repo Release Tools and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Repo Release Tools or shows a Repo Release Tools tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user repo-release-tools -- uvx repo-release-toolsClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"repo-release-tools": {
"command": "uvx",
"args": [
"repo-release-tools"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"repo-release-tools": {
"command": "uvx",
"args": [
"repo-release-tools"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"repo-release-tools": {
"type": "stdio",
"command": "uvx",
"args": [
"repo-release-tools"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Anselmoo, which owns the repo
- ✓ Pass
Still maintained
Code last changed 2 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for repo-release-tools@1.20.0
Checks only this package version, not every dependency · checked Nov 15, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/anselmoo-repo-release-tools)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 77% of the other 6083 servers in this category
- Published to the registry more recently than 84% of the other 6083 servers in this category
- Basic checks equal to or better than 99% of the other 6083 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Repo Release Tools safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 2 days ago, and the latest version (1.20.0) reached the registry 8 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Repo Release Tools | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
repo-release-tools
repo-release-tools keeps release policy boring in the best possible way.
Use it from GitHub Marketplace when you want CI to validate branch names, commit subjects, and changelog policy. Install it from PyPI when you want a local CLI, hook integration, version bumps, and release-branch automation.
- GitHub Marketplace action: https://github.com/marketplace/actions/repo-release-tools-policy-checks
- PyPI package: https://pypi.org/project/repo-release-tools/
- Choose your entry point
- Use the GitHub Action for CI policy checks
- Use the Python package for local workflow automation
- Changelog workflows
- What the project includes
- Get your AI agent to actually use rrt
- 1. Tell your agent, once, in its instruction file
- 2. Connect the MCP server (optional, but better for anything that writes)
- Prompt phrasings that work
- Agent instruction snippet
- Start with the doc that matches your task
- License
Choose your entry point
Use the GitHub Action for CI policy checks
Choose the action if you want pull requests and pushes to fail fast when a repo drifts from your release policy.
- validates branch names such as
feat/add-parser - validates Conventional Commit subjects
- validates changelog policy in CI
- optionally checks that the working tree stays clean
- can run
rrt doctoras a pre-release health gate
- uses: actions/checkout@v6
with: fetch-depth: 0
- uses: Anselmoo/repo-release-tools@v1.18.0 with: check-branch-name: "true" check-commit-subject: "true" check-changelog: "true"
See the full action guide: https://anselmoo.github.io/repo-release-tools/action/
See the full CLI and commands reference: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/commands/rrt-cli.md
Use the Python package for local workflow automation
Choose the package if you want the developer-side tools: branch helpers, version bumps, config inspection, pre-commit hooks, and release automation. The Python package is published on PyPI and has a CI counterpart in the GitHub Action guide.
pip install repo-release-tools
rrt init rrt branch new feat "add parser" rrt git commit "add parser" rrt git doctor rrt bump patch
Or run the CLI without installing it permanently:
uvx repo-release-tools branch new feat "add parser"
If rrt is already installed and you want the bundled agent skill for Copilot, Claude, or Codex, install it with:
rrt skill install --target copilot-local
rrt skill install --target claude-local --target codex-local rrt skill install --target codex-global --dry-run
For basic versioning, bump and ci-version can run without [tool.rrt] by auto-detecting repo-root pyproject.toml, package.json, Cargo.toml, .rrt.toml, or .config/rrt.toml. If multiple version files are found, they are updated together. Explicit config is for the nice extras: grouped releases, changelog paths, release branches, lock commands, generated files, and custom patterns.
Version targets also support common language/project files such as Python (pep621, python_version), Node/JS/TS (package_json), Go (go_version), Rust (cargo_toml), and .NET (csproj) so multi-language repositories can keep their release versions aligned. A mcp_server_json target keeps an MCP Registry server.json (top-level version, each package's version, and any oci package's image tag) in sync alongside a project's primary target.
Changelog workflows
Pick the style that matches how your repository lands changes.
`incremental` (default) — for teams that maintain changelog entries during development.
rrt-update-unreleasedandrrt-changeloghooks stay active.- The GitHub Action resolves
changelog-strategy: autotoper-commit. rrt bumpdefaults toauto.
`squash` — for repositories that squash many commits into one PR merge.
- Changelog write and check hooks skip enforcement.
- The GitHub Action resolves
changelog-strategy: autotorelease-only. rrt bumpdefaults togenerate.
Minimal config:
[tool.rrt]
release_branch = "release/v{version}" changelog_file = "CHANGELOG.md" changelog_workflow = "incremental" # or "squash"
[[tool.rrt.version_targets]] path = "pyproject.toml" kind = "pep621"
Native config is also supported in package.json ("rrt": { ... }) and Cargo.toml ([package.metadata.rrt] / [workspace.metadata.rrt]). Go repos should use .rrt.toml or .config/rrt.toml.
What the project includes
rrtCLI for branches, bumps, config inspection, and Git helpersrrt-hooksforpre-commit,lefthook,husky, and CI validation- a reusable GitHub Action in
action.yml - bundled agent skills for
uvxand installed-CLI workflows - docs for branch policy, hook setup, and release workflows
Get your AI agent to actually use rrt
If you use Claude Code, Copilot, Cursor, or Codex on a repository that has rrt configured, the agent will happily reimplement what rrt already does — hand-editing a version string in three files, inventing a branch name the pre-commit hook then rejects, or writing a changelog entry in the wrong section. Not because it lacks the tools, but because nothing told it these are the tools for this job.
Two things fix that. Do both.
1. Tell your agent, once, in its instruction file
Paste the block from Agent instruction snippet below into your repository's CLAUDE.md, AGENTS.md, or .github/copilot-instructions.md. This is the highest-leverage step by a wide margin: it is read on every session, before the agent has formed a plan, and it costs nothing at runtime.
2. Connect the MCP server (optional, but better for anything that writes)
uv add "repo-release-tools[mcp]"
Then add .mcp.json at the repository root — Claude Code picks it up on next start:
{
"mcpServers": { "rrt": { "type": "stdio", "command": "uv", "args": ["run", "rrt-mcp"] } } }
With the server connected, most tools give the agent typed JSON instead of terminal output it has to parse (the four lock readers and rrt_config return raw dicts instead), commit subjects and branch names are passed as arguments instead of through shell quoting, and mutating operations default to a dry-run preview. See the MCP Server guide for Claude Desktop, global install, and HTTP transport with bearer auth.
The MCP server does not cover everything. rrt docs map, rrt docs generate, rrt docs publish, rrt docs inject, rrt tree --check, rrt toc, rrt changelog lint, rrt changelog compare, rrt drift generate/check, rrt artifacts --check, every other --snapshot write, and every rrt-hooks subcommand are CLI-only — a mixed session is expected, not a fallback.
Prompt phrasings that work
These reliably route to rrt rather than to hand-editing:
- "Check with rrt whether this branch name will pass the hooks before you create it."
- "Use rrt to preview a minor bump — dry run — and show me every file it would touch."
- "Read the Unreleased changelog with rrt before adding an entry, so you don't duplicate one."
- "Run rrt doctor and tell me which hook integrations are missing."
- "Before you write that commit message, validate the subject with rrt."
- "What version is this repo at according to rrt?" — not "what's the version", which invites reading a random file.
- "Run rrt release check before you open the PR."
The pattern: name rrt explicitly, and name the *moment* ("before you create it", "before you open the PR"). Agents route on triggers, not on capabilities.
Agent instruction snippet
## Use `rrt` for release policy
This repo uses repo-release-tools (rrt) to enforce branch naming, Conventional Commits, changelog format, and version consistency. Do not hand-roll any of it.
Before you act, use rrt:
| When you are about to… | Use |
|---|---|
| create a branch | rrt branch new " " — or validate the name first with rrt-hooks check-branch-name --branch |
| write a commit message | rrt git commit --type " ", which builds and validates the subject before committing |
| change a version number anywhere | rrt bump --dry-run first — never edit version strings by hand; pins and the changelog move with it |
| add a changelog entry | read the existing [Unreleased] first; it is hook-managed |
| open a PR | rrt release check and rrt doctor |
Rules:
- Every mutating
rrtcommand takes--dry-run. Use it first, show the user the preview, and only apply after they confirm. - Never edit a version string by hand in more than one file — that is what
rrt bumpis for. - Never hand-edit the
[Unreleased]changelog section while the rrt hooks are active. - If
rrtis connected over MCP, prefer themcp__rrt__*tools over shelling out: typed responses for most tools, no shell quoting of commit subjects, and dry-run is the default. Shell out for anything with no MCP tool (rrt docs map,rrt docs generate,rrt docs publish,rrt docs inject,rrt tree --check,rrt toc,rrt changelog lint,rrt changelog compare,rrt drift generate/check,rrt artifacts --check, other--snapshotwrites,rrt-hooks *). rrt --helplists every command. Check it before concluding rrt cannot d