Repo Release Tools
Config-driven branch and release helpers for Git repositories
Connector by Anselmoo · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/anselmoo-repo-release-tools
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 23 read · 0 write · 6 delete
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Python package
Tools by what they do 29
Read from the source code; the running server may list different tools.
Read 23 · Look things up without changing anything.
rrt_artifactsrrt_changelogrrt_configrrt_docs_checkrrt_doctorrrt_doctor_dashboardrrt_driftrrt_eolrrt_folder_checkrrt_git_commits_sincerrt_git_dirty_treerrt_health
Show 11 more tools
rrt_health_dashboardrrt_initrrt_locks_overviewrrt_release_checkrrt_sync_checkrrt_treerrt_tree_dashboardrrt_validate_branchrrt_validate_commitrrt_versionrrt_version_overview
Delete 6 · Delete, drop, revoke or wipe things.
rrt_branch_newrrt_bumprrt_gate_runrrt_git_landrrt_init_runrrt_publish_snapshot
Network hosts it talks to 23
about.gitlab.com· found in codeanselmoo.github.io· found in codeapi.nuget.org· found in codeatlassian.com· found in codecodeberg.org· found in codecontext7.com· found in codeendoflife.date· found in codefonts.google.com· found in codefonts.googleapis.com· found in codefonts.gstatic.com· found in codegitea.io· found in codegithub.com· found in codegofastmcp.com· found in codehub.docker.com· found in codemicrosoft.com· found in codenuget.org· found in codepackagist.org· found in codepre-commit.ci· found in codeprefab.prefect.io· found in coderaw.githubusercontent.com· found in coderubygems.org· found in codesearch.maven.org· found in codesimpleicons.org· found in code
Files it touches
%APPDATA%\\Claude\\claude_desktop_config.json~/.claude/Library/Fonts/DejaVuSansMono.ttf/Library/Fonts/NotoSansMono-Regular.ttf- Your home directory (~)
~/.cargo/bin~/.codex~/.copilot~/.copilot/agents~/.copilot/hooks~/.copilot/skills~/.gemini~/.local/bin
Tools (29)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
rrt_artifactsLast recorded artifact-integrity snapshotread-onlyReturn the artifact integrity map from .rrt/artifacts.lock.toml. Reflects the last `rrt artifacts --snapshot`, not current state; run the CLI check to compare against the working tree. If your client can read files directly, `Read .rrt/artifacts.lock.toml` is equivalent.
rrt_branch_newCreate a policy-compliant branch for this taskcan change or delete dataDerive a compliant branch name from a type + description. When dry_run=False, checks it out. Use instead of `git checkout -b` with a hand-written name — it also returns a matching Conventional Commit title to use for the first commit, though nothing enforces that the caller actually uses it. commit_type: feat|fix|chore|docs|refactor|test|ci|perf|style|build. dry_run=True by default.
rrt_bumpPreview or apply a release version bumpcan change or delete dataPreview or apply a version bump — use instead of editing version strings by hand. This is the same pipeline as `rrt bump` (version targets, pins, changelog promotion, lockfile and generated-asset refresh, release branch + commit), so a partial hand-edit will diverge. dry_run=True previews everything and writes nothing. Each result's `changed_paths` lists every file the bump touched (or would touch under dry_run), relative to the repo root. level: major | minor | patch | alpha | beta | rc. dry_run=True by default. group: restrict the bump to one ``[tool.rrt]`` version group; omit to bump ever…
rrt_changelogWhat is already in the Unreleased changelog?read-onlyRead the changelog. Use before adding an entry, so you do not duplicate one that is already there, and before a bump, to see what will be promoted. section='unreleased' (default) returns parsed pending entries; section='full' returns the raw file. Read-only — writing an entry needs the CLI or hook workflow (`rrt-hooks update-unreleased`); do not hand-edit the `[Unreleased]` section while that hook is active.
rrt_configWhat release policy does this repo enforce?read-onlyRead the repo's resolved [tool.rrt] policy. Version targets, pin targets, changelog file, release branch pattern, folder rules. Call this before proposing any release-related change so you act on configured policy rather than assumptions. This returns the resolved config as structured data — a config-load error comes back as a typed ConfigError rather than a nonzero exit — but it does NOT run the per-target checks `rrt config --validate` does (target/pin/docs/folder `.validate()`); use rrt_release_check, rrt_folder_check, or rrt_docs_check for those.
rrt_docs_checkIs the docs lockfile stale?read-onlyCheck whether .rrt/docs.lock.toml is current against source-owned docs. Use after editing any source docstring that feeds generated documentation, before opening a PR — CI fails on this drift. Read-only — never regenerates or writes files. If stale, run `rrt docs generate --format toml` to refresh. Covers .rrt/docs.lock.toml only; `rrt docs map --check` has no tool here — use the CLI. Also reports published-docstring skeleton violations in `skeleton_issues` when the project configures `[tool.rrt.docs.skeleton]`.
rrt_doctorIs this repo's release automation actually wired up?read-onlyCheck whether hooks, workflows, and the artifact-protection lens are wired correctly. Covers pre-commit, lefthook, husky, GitHub Actions workflows, and CI artifact-protection. Use before recommending a hook or workflow change, and when a hook did not fire as expected. Returns one CheckResult per component with ok + severity — no output parsing.
rrt_doctor_dashboardRRT Doctor Dashboardread-onlyDoctor check results: pass-rate Ring, per-check Metrics, status cards, and detail table. Renders a UI widget for a human to look at — if you need the values to reason over, call rrt_doctor instead.
rrt_driftLast recorded source-drift snapshotread-onlyReturn source drift state from .rrt/drift.lock.toml (file hashes and symbols). Reflects the last `rrt drift generate`, not current state; run `rrt drift check` to compare against the working tree. If your client can read files directly, `Read .rrt/drift.lock.toml` is equivalent.
rrt_eolIs a runtime this repo supports going end-of-life?read-onlyCheck the host runtime and project minimum versions against EOL policy. Use before raising or lowering a minimum supported version, and when deciding whether to drop a version from a CI matrix. Read-only — never writes to .rrt/health.lock.toml. Set fetch_live=True to refresh EOL data from endoflife.date instead of the bundled snapshot.
rrt_folder_checkDoes this repo's layout violate its own folder policy?read-onlyCheck the repo layout against [tool.rrt.folders] policy or named built-in templates. Use before creating a new top-level directory or moving a module, so you place it where policy expects. Read-only — never scaffolds files.
rrt_gate_runRun the declared check lines against their expected exitscan change or delete dataRun [[tool.rrt.gates]] lines; every line runs and is judged against `expect`. Each line returns `exit`, `expected_exit` and `ok`, so a deliberately-red check that fails as designed reads as ok, and an unexpected failure does not. Use instead of chaining checks with `&&`, which stops at the first expected red line. dry_run=True by default, because the lines are repository-declared commands.
rrt_git_commits_sinceHow many commits since a ref, ignoring generated files?read-onlyList commits in <ref>..HEAD, leaving out commits that only touch *exclude* paths. A file that records HEAD can exclude itself, making "one commit behind" its resting state. Patterns are root-anchored git globs. exclude_generated adds every [tool.rrt.git].generated pattern. An unknown ref returns `error`, never count 0.
rrt_git_dirty_treeWhich paths are dirty, and which of them are generated?read-onlyList every uncommitted path, each marked when it matches [tool.rrt.git].generated. Use instead of `git status` before landing or committing. A regenerated manifest or handoff file shows as `generated: true`, so you can decide rather than guess. With ignore_generated=True, `clean` ignores generated entries. Read-only.
rrt_git_landLand a finished branch: fast-forward, remove worktree, delete branchcan change or delete dataFast-forward *onto* to *branch*, remove the branch's worktree, and delete it. One call, one process: three separate git calls cannot do this safely, because a hook can re-dirty the worktree between them. All checks run before any change. Local only — never pushes. Re-running after a failure skips finished steps. restore_generated discards [tool.rrt.git].generated changes in the worktree first. dry_run=True by default.
Show 14 more tools
rrt_healthLast recorded repo-health snapshotread-onlyReturn the health check results from .rrt/health.lock.toml. Reflects the last snapshot-writing run, not current state; run the CLI check to compare against the working tree. If your client can read files directly, `Read .rrt/health.lock.toml` is equivalent. This lock can hold results from three separate commands — `rrt doctor --snapshot` (pre-commit/lefthook/husky/ workflows), `rrt eol --snapshot`, and `rrt folder --snapshot` — so prefer rrt_doctor, rrt_eol, or rrt_folder_check for a live check of the part you actually need, not rrt_doctor alone.
rrt_health_dashboardRRT Health Dashboardread-onlyHealth overview: Metric summary, health Ring, per-lock status chart, check cards, and detail table. Renders a UI widget for a human to look at — if you need the values to reason over, call rrt_health / rrt_doctor instead.
rrt_initSet up rrt in this repo (interactive form)read-onlyForm to initialize rrt configuration — pick target format, preview, then apply. Renders a UI widget for a human to fill in — if you are an agent working from a shell, run `rrt init` directly instead.
rrt_init_runApply rrt init (submitted by the init form)can change or delete dataRun rrt init with the given target format. Defaults to dry_run=True for safety. This is the submit target of the rrt_init form — it shells out to `python -m repo_release_tools.cli init` and returns the captured output. If you are an agent working from a shell, run `rrt init` directly instead; you gain nothing by going through this tool.
rrt_locks_overviewRRT Locks Overviewread-onlyAll lock files at a glance: status donut chart, Carousel of lock summaries, and full detail table. Renders a UI widget for a human to look at — if you need the values to reason over, call rrt_health / rrt_tree / rrt_artifacts / rrt_drift instead.
rrt_publish_snapshotForce-push a squashed snapshot to a mirror remote (destructive)can change or delete dataForce-push a single-commit snapshot of tracked content to a secondary remote. dry_run=True by default. The force-push requires BOTH ``dry_run=False`` AND ``confirm=True`` -- mirroring the CLI's ``rrt git publish-snapshot``, which requires an explicit ``--yes-i-know-this-overwrites-remote-history`` flag in addition to not passing ``--dry-run`` (two independent signals for one destructive, history-rewriting operation). If ``confirm`` is omitted or False, the call is always treated as a dry-run preview, regardless of ``dry_run``.
rrt_release_checkAre version, pin, and changelog targets consistent for release?read-onlyVerify every version target, pin target, and changelog file resolves and agrees, per version group. Use as the pre-release gate and after any edit that touches a version string in docs or config — pin drift is silent otherwise. Read-only — never modifies files.
rrt_sync_checkHas upstream released a newer version than we track?read-onlyList upstream package versions newer than the current project version. Reads the group's [tool.rrt.upstream] package config and queries the configured registry (PyPI/npm/NuGet/crates.io/Packagist). Read-only — never applies a bump. Requires network access to the registry.
rrt_treeLast recorded file-tree snapshot (NOT a live check)read-onlyReturn the repository tree snapshot from .rrt/tree.lock.toml. Reflects the last `rrt tree --snapshot`, not current state — this tool does NOT run `rrt tree --check` and cannot tell you whether the working tree still matches it. There is no MCP tool for that check; use the CLI. If your client can read files directly, `Read .rrt/tree.lock.toml` is equivalent.
rrt_tree_dashboardRRT Tree Dashboardread-onlyRepository tree: snapshot Metric cards, per-directory bar chart, and clean file table. Renders a UI widget for a human to look at — if you need the values to reason over, call rrt_tree instead (it is still a snapshot, not a live check).
rrt_validate_branchWill this branch name pass the repo's hooks?read-onlyCheck a branch name against this repo's configured type allow-list before you create it. Cheaper than creating it and having the pre-commit hook reject it. Honors extra_branch_types from config, which a hardcoded regex would miss.
rrt_validate_commitWill this commit subject pass the repo's hooks?read-onlyCheck a commit subject against Conventional Commits as this repo enforces it, before you commit. Prefer this over `rrt-hooks commit-msg` in a shell: the subject is passed as a string argument, so backticks, quotes, `!`, and `$` in the message cannot be mangled by shell quoting.
rrt_versionWhat version is this repo at right now?read-onlyRead the current version of every configured version group from its primary target. Use whenever a version number is about to appear in a commit message, changelog heading, docs string, or release note — this is the authoritative value, not whatever a file happened to say. Read-only.
rrt_version_overviewRRT Version Overviewread-onlyVersion target map: each configured file, kind, and current version. Renders a UI widget for a human to look at — if you need the primary-target values to reason over, call rrt_version instead. Unlike this dashboard, which reads every configured target, rrt_version returns only each group's primary target; for secondary/pin target consistency use rrt_release_check.
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 4
- Weekly downloads
- 532
- Last commit
- Oct 20, 2026 (8 days ago)
- Last release
- Sep 21, 2026 (1 month ago)
- Last package publish
- Sep 21, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.Anselmoo/repo-release-tools- Version
- 1.18.0
- Auth
- No auth
- Packages
- pypi repo-release-toolsoci
ghcr.io/anselmoo/repo-release-tools:1.18.0 - License
- MIT
- Repository
- github.com/Anselmoo/repo-release-tools
- First seen
- Oct 24, 2026
- Last checked
- Oct 25, 2026
More from Anselmoo
- 0.531score
MCP Ooxml Ledger
Anselmoo
Edit Office documents and prove no edit went unrecorded
ConnectorAFreshness: ALocal↓ 55/wkClaude Code +5 - 0.521score
MCP Server Analyzer
Anselmoo
MCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome
ConnectorBFreshness: BLocalRead-only★ 11↓ 97/wkClaude Code +5
Cite this page
Repo Release Tools MCP server. Agent Mart. https://agentmart.dev/connectors/anselmoo-repo-release-tools (last updated 2026-10-25)