Developer · Local MCP server

Repo Release Tools

Config-driven branch and release helpers for Git repositories.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.Anselmoo/repo-release-tools
Version
1.18.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
PyPI, OCI image (Docker)
Published
2026-09-21
Updated
2026-09-21
Publisher
Anselmoo (GitHub) · 3 servers with pages here
Repository
github.com/Anselmoo/repo-release-tools
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
PyPIruntime: uvxrepo-release-tools1.18.0stdioNone declared
OCI image (Docker)runtime: dockerghcr.io/anselmoo/repo-release-tools:1.18.0—stdioNone declared

How to connect Repo Release Tools

Repo Release Tools runs locally from a Python package published to PyPI: repo-release-tools version 1.18.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx repo-release-tools.

Repo Release Tools runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/anselmoo/repo-release-tools:1.18.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm ghcr.io/anselmoo/repo-release-tools:1.18.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "repo-release-tools": {
      "command": "uvx",
      "args": [
        "repo-release-tools"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More from Anselmoo (GitHub)

ServerRunsEndpoint or package
MCP Ooxml LedgerEdit Office documents and prove no edit went unrecorded.Local · stdioPyPI: mcp-ooxml-ledger
MCP Server AnalyzerMCP server for Python, JavaScript, and TypeScript code analysis with Ruff, ty, Vulture, and Biome.Local · stdioPyPI: mcp-server-analyzer

More developer servers

All 6,250 →
ServerRunsEndpoint or package
ReplicateRun AI models, create deployments, and manage predictions via cloud API.Local · stdioPyPI: mcparmory-replicate
Replit SSHRead, write, list, and check files on Replit projects over SSH/SFTP, plus SSH key setup.Local · stdionpm: @mindstone/mcp-server-replit-ssh
Repo Forensics MCPLocal read-only MCP tools for Git repository archaeology, churn, hotspots, and hygiene. Tools...Local · stdionpm: repo-forensics-mcp
Repo MemoryShared, git-tracked working memory for AI agents on the same codebase.Local · stdioPyPI: repo-memory-mcp
Repo Security Scanner — Malicious Code & Supply ChainAudit GitHub repos for malicious and supply-chain code before you depend on them.Remote · HTTPmcp.apify.com
repo-memory-mcpPersistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.Local · stdioPyPI: repo-memory-mcp-ai
RepoContextRead-only, commit-pinned repository context for coding agents.Local · stdionpm: @shmindmaster/repocontext
repoctxLocal-first code context, impact analysis, and merge-readiness verdicts for AI agents.Local · stdionpm: @nugehs/repoctx