Repo Release Tools MCP server

Read from the package source without running it. The installed server may list more.

• _default_help

  Print help and exit with 1 when no subcommand was given.

• rrt_artifacts

  Return the artifact integrity map from .rrt/artifacts.lock.toml.

• rrt_branch_new

  Derive a compliant branch name from a type + description.

• rrt_bump

  Preview or apply a version bump — use instead of editing version strings by hand.

• rrt_changelog

  Read the changelog.

• rrt_config

  Read the repo's resolved [tool.rrt] policy.

• rrt_docs_check

  Check whether .rrt/docs.lock.toml is current against source-owned docs.

• rrt_doctor

  Check whether hooks, workflows, and the artifact-protection lens are wired correctly.

• rrt_doctor_dashboard

  Doctor check results: pass-rate Ring, per-check Metrics, status cards, and detail table.

• rrt_drift

  Return source drift state from .rrt/drift.lock.toml (file hashes and symbols).

• rrt_eol

  Check the host runtime and project minimum versions against EOL policy.

• rrt_folder_check

  Check the repo layout against [tool.rrt.folders] policy or named built-in templates.

• rrt_health

  Return the health check results from .rrt/health.lock.toml.

• rrt_health_dashboard

  Health overview: Metric summary, health Ring, per-lock status chart, check cards, and detail table.

• rrt_init

  Form to initialize rrt configuration — pick target format, preview, then apply.

• rrt_init_runwrite action

  Run rrt init with the given target format. Defaults to dry_run=True for safety.

• rrt_locks_overview

  All lock files at a glance: status donut chart, Carousel of lock summaries, and full detail table.

• rrt_publish_snapshotwrite action

  Force-push a single-commit snapshot of tracked content to a secondary remote.

• rrt_release_check

  Verify every version target, pin target, and changelog file resolves and agrees, per version group.

• rrt_sync_check

  List upstream package versions newer than the current project version.

• rrt_tree

  Return the repository tree snapshot from .rrt/tree.lock.toml.

• rrt_tree_dashboard

  Repository tree: snapshot Metric cards, per-directory bar chart, and clean file table.

• rrt_validate_branch

  Check a branch name against this repo's configured type allow-list before you create it.

• rrt_validate_commit

  Check a commit subject against Conventional Commits as this repo enforces it, before you commit.

• rrt_version

  Read the current version of every configured version group from its primary target.

• rrt_version_overview

  Version target map: each configured file, kind, and current version.

• Code scan127 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 3 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

92/100

higher than 90% of 1,119 Developer tools servers

Tools

26

the typical Developer tools server has 7

Tools that change things

8%

typical: 5%. Fewer write tools means less an agent can break

GitHub stars

1

more than 50% of 856 Developer tools servers

Downloads a week

578

more than 87% of 442 Developer tools servers with a package

Repo Release Tools: common questions

Is Repo Release Tools MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Repo Release Tools safety report

How do I install Repo Release Tools?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Repo Release Tools need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Repo Release Tools maintained?

The last commit was 10 days ago (2026-10-26). The latest release is v1.18.0.

What can I use instead of Repo Release Tools?

Servers from other publishers that do the same job: git-into-gsoc MCP server, Emfirge MCP server and Pare Git MCP server. Compare all Repo Release Tools alternatives.

How does Repo Release Tools compare with other Developer tools MCP servers?

safety score 92/100 (higher than 90% of 1,119 Developer tools servers); tools 26 (the typical Developer tools server has 7); tools that change things 8% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.