rrt-user-mcp-server
User problem statement
I want to use rrt's capabilities (config inspection, version bumping, health
checks, changelog reading, branch/commit validation) directly inside my AI
assistant without leaving the editor.
Quick start commands
# Install the MCP extra
uv add "repo-release-tools[mcp]"
# Verify the server starts
uv run rrt-mcp --help
# Add .mcp.json at the repo root (Claude Code auto-detects this)
cat .mcp.json
# Should contain:
# {
# "mcpServers": {
# "rrt": { "type": "stdio", "command": "uv", "args": ["run", "rrt-mcp"] }
# }
# }
When to use
- Connecting the rrt MCP server to Claude Code, Claude Desktop, or Cursor
- Choosing between local (per-repo) and global MCP wiring
- Using interactive dashboards (
rrt_health_dashboard, rrt_tree_dashboard, rrt_locks_overview, etc.)
- Calling
rrt_bump, rrt_changelog, or rrt_validate_branch from within
an AI assistant conversation
- Initializing rrt config via the
rrt_init form app
Do not use for
- Debugging rrt CLI commands (use
rrt doctor instead)
- Writing custom MCP servers based on rrt internals
- Publishing or packaging the rrt release itself
Install surfaces
Claude Code — local (per-repo, auto-detected)
Create .mcp.json at the repository root:
{
"mcpServers": {
"rrt": {
"type": "stdio",
"command": "uv",
"args": ["run", "rrt-mcp"]
}
}
}
Claude Code picks this up automatically on next start.
Claude Code — global
claude mcp add rrt -- uv run --with "repo-release-tools[mcp]" rrt-mcp
Or manually add to ~/.claude/mcp.json:
{
"mcpServers": {
"rrt": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]
}
}
}
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"rrt": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]
}
}
}
Restart Claude Desktop after editing.
Published package (no local install)
{
"mcpServers": {
"rrt": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]
}
}
}
Available tools
| Tool |
Tags |
Notes |
rrt_config |
config, inspection |
Resolved rrt config as JSON |
rrt_doctor |
config, inspection |
Pre-commit / lefthook / workflow checks |
rrt_health |
locks, inspection |
.rrt/health.lock.toml |
rrt_drift |
locks, inspection |
.rrt/drift.lock.toml |
rrt_tree |
locks, inspection |
.rrt/tree.lock.toml |
rrt_artifacts |
locks, inspection |
.rrt/artifacts.lock.toml |
rrt_version |
versioning |
Current version per group |
rrt_bump |
versioning |
Bump version (destructive when dry_run=False) |
rrt_validate_branch |
validation |
Conventional branch naming |
rrt_validate_commit |
validation |
Conventional commit subject |
rrt_changelog |
changelog |
Unreleased entries or full content |
rrt_health_dashboard |
ui, dashboard |
Metric row, health Ring, per-lock BarChart, check Cards, detail table (app tool) |
rrt_version_overview |
ui, dashboard, versioning |
Version target map with Metric header (app tool) |
rrt_doctor_dashboard |
ui, dashboard, inspection |
Pass-rate Ring, per-check Metrics, status Cards, detail table (app tool) |
rrt_tree_dashboard |
ui, dashboard, inspection |
Metric summary, per-directory BarChart, clean file table (app tool) |
rrt_init |
ui, init, config |
Init form — target, dry_run, force (app tool, submits to rrt_init_run) |
rrt_init_run |
init, config |
Executes rrt init; dry_run=True by default (destructive) |
rrt_locks_overview |
ui, dashboard, locks |
Status donut PieChart, Carousel of lock summaries, detail table (app tool) |
Available resources
| URI |
Description |
rrt://version |
Installed package version |
rrt://config |
Config as JSON |
rrt://changelog |
Full CHANGELOG.md |
rrt://locks/{name} |
Any lock file by name (drift/health/tree/artifacts) |
Generative UI
The server registers FastMCP's GenerativeUI provider, adding
generate_prefab_ui and search_prefab_components tools. The LLM can write
custom Prefab code executed in a Pyodide sandbox — useful for custom
visualizations of rrt://locks/{name} data.
Full reference
See docs/mcp-server.md in the repository (or /mcp-server/ on the docs site)
for the complete tool, resource, and prompt reference.
Expected outcome / success criteria
rrt_config returns the project's resolved rrt config without error
rrt_health_dashboard renders Metric cards, a health Ring, and a BarChart in Claude's UI
rrt_tree_dashboard shows a BarChart of file counts per directory with no empty columns in the table
rrt_locks_overview shows a donut PieChart and a Carousel cycling through lock summaries
rrt_bump patch --dry-run previews a version change without writing files
- The user can complete a full release workflow from inside the AI assistant
Source: Anselmoo/repo-release-tools — distributed by TomeVault.
1---2name: anselmoo-repo-release-tools-rrt-user-mcp-server3description: rrt-user-mcp-server4---56# rrt-user-mcp-server78## User problem statement910I want to use rrt's capabilities (config inspection, version bumping, health11checks, changelog reading, branch/commit validation) directly inside my AI12assistant without leaving the editor.1314## Quick start commands1516```bash17# Install the MCP extra18uv add "repo-release-tools[mcp]"1920# Verify the server starts21uv run rrt-mcp --help2223# Add .mcp.json at the repo root (Claude Code auto-detects this)24cat .mcp.json25# Should contain:26# {27# "mcpServers": {28# "rrt": { "type": "stdio", "command": "uv", "args": ["run", "rrt-mcp"] }29# }30# }31```3233## When to use3435- Connecting the rrt MCP server to Claude Code, Claude Desktop, or Cursor36- Choosing between local (per-repo) and global MCP wiring37- Using interactive dashboards (`rrt_health_dashboard`, `rrt_tree_dashboard`, `rrt_locks_overview`, etc.)38- Calling `rrt_bump`, `rrt_changelog`, or `rrt_validate_branch` from within39 an AI assistant conversation40- Initializing rrt config via the `rrt_init` form app4142## Do not use for4344- Debugging rrt CLI commands (use `rrt doctor` instead)45- Writing custom MCP servers based on rrt internals46- Publishing or packaging the rrt release itself4748## Install surfaces4950### Claude Code — local (per-repo, auto-detected)5152Create `.mcp.json` at the repository root:5354```json55{56 "mcpServers": {57 "rrt": {58 "type": "stdio",59 "command": "uv",60 "args": ["run", "rrt-mcp"]61 }62 }63}64```6566Claude Code picks this up automatically on next start.6768### Claude Code — global6970```bash71claude mcp add rrt -- uv run --with "repo-release-tools[mcp]" rrt-mcp72```7374Or manually add to `~/.claude/mcp.json`:7576```json77{78 "mcpServers": {79 "rrt": {80 "type": "stdio",81 "command": "uvx",82 "args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]83 }84 }85}86```8788### Claude Desktop8990Add to `~/Library/Application Support/Claude/claude_desktop_config.json`91(macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):9293```json94{95 "mcpServers": {96 "rrt": {97 "type": "stdio",98 "command": "uvx",99 "args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]100 }101 }102}103```104105Restart Claude Desktop after editing.106107### Published package (no local install)108109```json110{111 "mcpServers": {112 "rrt": {113 "type": "stdio",114 "command": "uvx",115 "args": ["--from", "repo-release-tools[mcp]", "rrt-mcp"]116 }117 }118}119```120121## Available tools122123| Tool | Tags | Notes |124|---|---|---|125| `rrt_config` | config, inspection | Resolved rrt config as JSON |126| `rrt_doctor` | config, inspection | Pre-commit / lefthook / workflow checks |127| `rrt_health` | locks, inspection | `.rrt/health.lock.toml` |128| `rrt_drift` | locks, inspection | `.rrt/drift.lock.toml` |129| `rrt_tree` | locks, inspection | `.rrt/tree.lock.toml` |130| `rrt_artifacts` | locks, inspection | `.rrt/artifacts.lock.toml` |131| `rrt_version` | versioning | Current version per group |132| `rrt_bump` | versioning | Bump version (destructive when dry_run=False) |133| `rrt_validate_branch` | validation | Conventional branch naming |134| `rrt_validate_commit` | validation | Conventional commit subject |135| `rrt_changelog` | changelog | Unreleased entries or full content |136| `rrt_health_dashboard` | ui, dashboard | Metric row, health Ring, per-lock BarChart, check Cards, detail table (app tool) |137| `rrt_version_overview` | ui, dashboard, versioning | Version target map with Metric header (app tool) |138| `rrt_doctor_dashboard` | ui, dashboard, inspection | Pass-rate Ring, per-check Metrics, status Cards, detail table (app tool) |139| `rrt_tree_dashboard` | ui, dashboard, inspection | Metric summary, per-directory BarChart, clean file table (app tool) |140| `rrt_init` | ui, init, config | Init form — target, dry_run, force (app tool, submits to rrt_init_run) |141| `rrt_init_run` | init, config | Executes rrt init; dry_run=True by default (destructive) |142| `rrt_locks_overview` | ui, dashboard, locks | Status donut PieChart, Carousel of lock summaries, detail table (app tool) |143144## Available resources145146| URI | Description |147|---|---|148| `rrt://version` | Installed package version |149| `rrt://config` | Config as JSON |150| `rrt://changelog` | Full CHANGELOG.md |151| `rrt://locks/{name}` | Any lock file by name (drift/health/tree/artifacts) |152153## Generative UI154155The server registers FastMCP's `GenerativeUI` provider, adding156`generate_prefab_ui` and `search_prefab_components` tools. The LLM can write157custom Prefab code executed in a Pyodide sandbox — useful for custom158visualizations of `rrt://locks/{name}` data.159160## Full reference161162See `docs/mcp-server.md` in the repository (or `/mcp-server/` on the docs site)163for the complete tool, resource, and prompt reference.164165## Expected outcome / success criteria166167- `rrt_config` returns the project's resolved rrt config without error168- `rrt_health_dashboard` renders Metric cards, a health Ring, and a BarChart in Claude's UI169- `rrt_tree_dashboard` shows a BarChart of file counts per directory with no empty columns in the table170- `rrt_locks_overview` shows a donut PieChart and a Carousel cycling through lock summaries171- `rrt_bump patch --dry-run` previews a version change without writing files172- The user can complete a full release workflow from inside the AI assistant173174---175> Source: [Anselmoo/repo-release-tools](https://github.com/Anselmoo/repo-release-tools) — distributed by [TomeVault](https://tomevault.io).176<!-- tomevault:4.0:skill_md:2026-06-16 -->