Skip to main content
Glama
Repository Manager

Repository Manager

Repository Manager

CLI or API | MCP | Agent

PyPI - Version MCP Server PyPI - Downloads GitHub Repo stars GitHub forks GitHub contributors PyPI - License GitHub GitHub last commit (by committer) GitHub pull requests GitHub closed pull requests GitHub issues GitHub top language GitHub language count GitHub repo size GitHub repo file count (file type) PyPI - Wheel PyPI - Implementation

Version: 3.5.6

Documentation — Installation, deployment, usage across the CLI, API, MCP, and agent interfaces, and the fleet dependency rollout workflow are maintained in the official documentation.


Related MCP server: gitlab-api

Overview

Repository Manager is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with Manage the operator's git projects.


Key Features

  • Consolidated Action-Routed MCP Tools: Minimizes token overhead and eliminates tool bloat in LLM contexts by grouping methods into optimized, togglable tool modules.

  • Enterprise-Grade Security: Complete support for Eunomia policies, OIDC token delegation, and granular execution context tracking.

  • Integrated Graph Agent: Built-in Pydantic AI agent supporting the Agent Control Protocol (ACP) and standard Web interfaces (AG-UI).

  • Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.


CLI or API

This agent wraps the Manage the operator's git projects API. The operator can interact with it programmatically or via its integrated execution entrypoints.

Detailed instructions on how to use the underlying API wrappers, extended schema bindings, and developer SDK references are maintained in docs/index.md.


MCP

This server use dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Available MCP Tools

This table is auto-generated from the live server — do not edit by hand.

Condensed action-routed tools (MCP_TOOL_MODE=condensed)

MCP Tool

Toggle Env Var

Description

repository_ingest_repositories

MISCTOOL

Natively ingest git repositories into epistemic-graph as typed :GitRepository nodes.

rm_build_*

PROJECT_MANAGEMENTTOOL

Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

rm_concepts_*

DEVELOPMENT_SURFACESTOOL

Concept-id claim coordination against RMDD-16's central authority.

rm_docs_readiness_*

PROJECT_MANAGEMENTTOOL

Preview/apply/verify artifacts after per-repository readiness setup.

rm_gates_*

PROJECT_MANAGEMENTTOOL

Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

rm_git_*

GIT_OPERATIONSTOOL

Typed bulk Git operations; arbitrary host commands are prohibited.

rm_lane_*

PROJECT_MANAGEMENTTOOL

The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

rm_merge_queue_*

PROJECT_MANAGEMENTTOOL

Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

rm_projects_*

PROJECT_MANAGEMENTTOOL

Bulk install, build, and validate Python projects.

rm_remote_workers_*

DEVELOPMENT_SURFACESTOOL

Remote worker registry, immutable source staging, and artifact transport.

rm_workspace_*

WORKSPACE_MANAGEMENTTOOL

Core workspace organization, configuration, and maintenance.

rm_worktree_*

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)

MCP Tool

Toggle Env Var

Description

repository_manager_add_project

GITTOOL

Stage all changes (git add -A) for a single Git project.

repository_manager_add_projects

GITTOOL

Stage all changes for multiple projects in parallel.

repository_manager_build_projects

GITTOOL

Build projects serially so compilation cannot exhaust the workstation.

repository_manager_bulk_bump

GITTOOL

Bumps the version for all projects in the workspace in parallel.

repository_manager_bump_version

GITTOOL

Bump the version of the project using bump2version.

repository_manager_cleanup_artifacts

GITTOOL

Removes test artifacts and temporary files from the specified directory.

repository_manager_clone_projects

GITTOOL

Clone all specified Git projects in parallel using multiple threads.

repository_manager_clone_repository

GITTOOL

Clone a single Git repository to a specific target path.

repository_manager_commit_code_project

GITTOOL

Stage ALL changes (git add -A), optionally gate on pre-commit, then commit.

repository_manager_commit_code_projects

GITTOOL

Concurrently stage + pre-commit + commit feature code across projects.

repository_manager_commit_project

GITTOOL

Commit staged changes (git commit -m "{message}") for a single Git project.

repository_manager_commit_projects

GITTOOL

Commit staged changes for multiple projects in parallel.

repository_manager_create_project

GITTOOL

Create a new project directory and initialize it as a git repository.

repository_manager_discover_projects

GITTOOL

Scan self.path for immediate subdirectories containing a .git folder.

repository_manager_generate_markdown_summary

GITTOOL

Generates a beautiful markdown summary of bulk operation results.

repository_manager_generate_workspace_template

GITTOOL

Generates a workspace.yml template at the specified path.

repository_manager_get_consolidated_skill_paths

GITTOOL

Returns absolute paths to the 15 specific building and documentation skills.

repository_manager_get_project_map

GITTOOL

Returns the mapping of repository URLs to their local project paths.

repository_manager_get_readme

GITTOOL

Get the content and path of the README.md file in the specified path.

repository_manager_get_workspace_projects

GITTOOL

Returns a list of project basenames (e.g. 'genius-agent') defined in the workspace.

repository_manager_git_action

GITTOOL

Execute a Git command in the specified directory.

repository_manager_install_project

GITTOOL

Install a Python project using pip install -e .[extra].

repository_manager_install_projects

GITTOOL

Bulk installs Python and Node projects in the workspace.

repository_manager_list_branches

GITTOOL

Returns a dictionary mapping project basenames to their current active git branch.

repository_manager_load_projects_from_yaml

GITTOOL

Loads repository URLs from a YAML workspace file using Pydantic models.

rm_rollout

ROLLOUTTOOL

Roll a dependency floor across the fleet: plan, apply, status, release.

repository_manager_pre_commit

GITTOOL

Execute pre-commit commands in the specified path.

repository_manager_pre_commit_projects

GITTOOL

Execute pre-commit commands for all projects in parallel.

repository_manager_pull_project

GITTOOL

Pull updates for a single Git project and optionally checkout the default branch.

repository_manager_pull_projects

GITTOOL

Pull updates for multiple projects in parallel.

repository_manager_push_project

GITTOOL

Atomically publish a clean checkout's exact current branch and release tag.

repository_manager_push_projects

GITTOOL

Push updates for multiple projects in parallel.

repository_manager_save_workspace_config

GITTOOL

Saves the current or provided WorkspaceConfig to a YAML file.

repository_manager_set_threads

GITTOOL

Set the number of threads for parallel processing.

repository_manager_setup_from_yaml

GITTOOL

Sets up the workspace structure from a YAML file.

repository_manager_test_projects

GITTOOL

Execute pytests for the specified projects in parallel.

repository_manager_update_dependency

GITTOOL

Update a package's pinned version in a deps file (pyproject OR requirements).

repository_manager_validate_and_release

GITTOOL

Validate projects in parallel, optionally triggering a release if successful.

repository_manager_validate_single_project

GITTOOL

Validates a single repository by running its FAST-tier gates.

repository_manager_worktree_hygiene

GITTOOL

Audit (and optionally prune) session worktrees as a release-flow step.

rm_worktree__add

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__audit

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__bulk_add

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__list

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__merge

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__prune

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__remove

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__reset_branch

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

rm_worktree__sync

PROJECT_MANAGEMENTTOOL

Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

12 action-routed tool(s) · 51 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (intent default — the six verb-tools, granular set loaded on demand · condensed action-routed · verbose 1:1 · both). Auto-generated — do not edit.

Detailed tool schemas, parameter shapes, and validation constraints are preserved in docs/usage.md.

Dynamic Tool Selection & Visibility

This MCP server supports dynamic toolset selection and visibility filtering at runtime. This allows the operator to restrict the set of exposed tools to prevent blowing up the LLM's context window.

The operator can configure tool filtering via multiple input channels:

  • CLI Arguments: Pass --tools or --toolsets (or their disabled counterparts --disabled-tools and --disabled-toolsets) during startup.

  • Environment Variables: Define standard environment variables:

    • MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS

    • MCP_ENABLED_TAGS / MCP_DISABLED_TAGS

  • HTTP SSE Request Headers: Pass custom headers during transport initialization:

    • x-mcp-enabled-tools / x-mcp-disabled-tools

    • x-mcp-enabled-tags / x-mcp-disabled-tags

  • HTTP SSE Request Query Parameters: Append query parameters directly to the operator's transport connection URL:

    • ?tools=tool1,tool2

    • ?tags=tag1

When query strings or parameters are provided, an LLM-free Knowledge Graph resolution layer (using DynamicToolOrchestrator) matches query intents against known tool tags, names, or descriptions, with safe fallback and automated 24-hour background cache refreshing.


MCP Configuration Examples

Install the connector-focused [mcp] extra. Examples use repository-manager[mcp] to add FastMCP / FastAPI through scion-sdk; the required Scion SDK core still carries epistemic-graph[full]. The [agent-runtime] extra additionally enables model orchestration.

stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)

{
  "mcpServers": {
    "repository-manager-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "repository-manager[mcp]",
        "repository-manager-mcp"
      ],
      "env": {
        "MCP_TOOL_MODE": "intent",
        "BUILDTOOL": "True",
        "CONCEPTSTOOL": "True",
        "DEVELOPMENT_SURFACESTOOL": "True",
        "DOCS_READINESSTOOL": "True",
        "GATESTOOL": "True",
        "ROLLOUTTOOL": "True",
        "GH_TOKEN": "your_github_token_here",
        "GITHUB_TOKEN": "your_github_token_here",
        "GITLAB_HOST": "https://gitlab.com",
        "GITLAB_PRIVATE_TOKEN": "your_gitlab_token_here",
        "GITLAB_TOKEN": "your_gitlab_token_here",
        "GITLAB_URL": "https://gitlab.com",
        "GIT_OPERATIONSTOOL": "True",
        "LANETOOL": "True",
        "MERGE_QUEUETOOL": "True",
        "MERGE_QUEUE_DRAIN_DEADLINE_SECONDS": "180",
        "MERGE_QUEUE_GLOBAL_DEADLINE_SECONDS": "3600",
        "MERGE_QUEUE_HEAVY_DEADLINE_SECONDS": "18000",
        "MERGE_QUEUE_LEASE_TTL_SECONDS": "14400",
        "MERGE_QUEUE_MAX_AGE_SECONDS": "86400",
        "MISCTOOL": "True",
        "PROJECTTOOL": "True",
        "PROJECT_MANAGEMENTTOOL": "True",
        "REMOTE_WORKERSTOOL": "True",
        "REPOSITORY_MANAGER_DEFAULT_BRANCH": "main",
        "REPOSITORY_MANAGER_THREADS": "12",
        "RM_CPU_FRACTION": "0.20",
        "RM_GATE_BEFORE_PUSH": "true",
        "RM_GATE_TIMEOUT_SECONDS": "1800",
        "RM_JOB_STALE_SECONDS": "1800",
        "RM_MAX_WORKERS": "8",
        "RM_RAM_FRACTION": "0.20",
        "RM_WORKER_MEM_GB": "1.5",
        "WORKSPACE_MANAGEMENTTOOL": "True",
        "WORKSPACE_YML": "workspace.yml",
        "WORKTREETOOL": "True"
      }
    }
  }
}

Runtime references require an alias-aware launcher such as Arbora. Other launchers must omit those entries and inject the resolved values through their own runtime secret boundary.

Streamable-HTTP Transport (networked / production)

{
  "mcpServers": {
    "repository-manager-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "repository-manager[mcp]",
        "repository-manager-mcp",
        "--transport",
        "streamable-http",
        "--port",
        "8000"
      ],
      "env": {
        "TRANSPORT": "streamable-http",
        "HOST": "127.0.0.1",
        "PORT": "8000",
        "MCP_TOOL_MODE": "intent",
        "BUILDTOOL": "True",
        "CONCEPTSTOOL": "True",
        "DEVELOPMENT_SURFACESTOOL": "True",
        "DOCS_READINESSTOOL": "True",
        "GATESTOOL": "True",
        "ROLLOUTTOOL": "True",
        "GH_TOKEN": "your_github_token_here",
        "GITHUB_TOKEN": "your_github_token_here",
        "GITLAB_HOST": "https://gitlab.com",
        "GITLAB_PRIVATE_TOKEN": "your_gitlab_token_here",
        "GITLAB_TOKEN": "your_gitlab_token_here",
        "GITLAB_URL": "https://gitlab.com",
        "GIT_OPERATIONSTOOL": "True",
        "LANETOOL": "True",
        "MERGE_QUEUETOOL": "True",
        "MERGE_QUEUE_DRAIN_DEADLINE_SECONDS": "180",
        "MERGE_QUEUE_GLOBAL_DEADLINE_SECONDS": "3600",
        "MERGE_QUEUE_HEAVY_DEADLINE_SECONDS": "18000",
        "MERGE_QUEUE_LEASE_TTL_SECONDS": "14400",
        "MERGE_QUEUE_MAX_AGE_SECONDS": "86400",
        "MISCTOOL": "True",
        "PROJECTTOOL": "True",
        "PROJECT_MANAGEMENTTOOL": "True",
        "REMOTE_WORKERSTOOL": "True",
        "REPOSITORY_MANAGER_DEFAULT_BRANCH": "main",
        "REPOSITORY_MANAGER_THREADS": "12",
        "RM_CPU_FRACTION": "0.20",
        "RM_GATE_BEFORE_PUSH": "true",
        "RM_GATE_TIMEOUT_SECONDS": "1800",
        "RM_JOB_STALE_SECONDS": "1800",
        "RM_MAX_WORKERS": "8",
        "RM_RAM_FRACTION": "0.20",
        "RM_WORKER_MEM_GB": "1.5",
        "WORKSPACE_MANAGEMENTTOOL": "True",
        "WORKSPACE_YML": "workspace.yml",
        "WORKTREETOOL": "True"
      }
    }
  }
}

Alternatively, connect to a pre-deployed Streamable-HTTP instance by url:

{
  "mcpServers": {
    "repository-manager-mcp": {
      "url": "http://localhost:8000/repository-manager-mcp/mcp"
    }
  }
}

Run a reviewed container image as a least-privilege stdio child (no listener or published port):

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  -e MCP_TOOL_MODE=intent \
  -e BUILDTOOL=True \
  -e CONCEPTSTOOL=True \
  -e DEVELOPMENT_SURFACESTOOL=True \
  -e DOCS_READINESSTOOL=True \
  -e GATESTOOL=True \
  -e ROLLOUTTOOL=True \
  -e GH_TOKEN=your_github_token_here \
  -e GITHUB_TOKEN=your_github_token_here \
  -e GITLAB_HOST=https://gitlab.com \
  -e GITLAB_PRIVATE_TOKEN=your_gitlab_token_here \
  -e GITLAB_TOKEN=your_gitlab_token_here \
  -e GITLAB_URL=https://gitlab.com \
  -e GIT_OPERATIONSTOOL=True \
  -e LANETOOL=True \
  -e MERGE_QUEUETOOL=True \
  -e MERGE_QUEUE_DRAIN_DEADLINE_SECONDS=180 \
  -e MERGE_QUEUE_GLOBAL_DEADLINE_SECONDS=3600 \
  -e MERGE_QUEUE_HEAVY_DEADLINE_SECONDS=18000 \
  -e MERGE_QUEUE_LEASE_TTL_SECONDS=14400 \
  -e MERGE_QUEUE_MAX_AGE_SECONDS=86400 \
  -e MISCTOOL=True \
  -e PROJECTTOOL=True \
  -e PROJECT_MANAGEMENTTOOL=True \
  -e REMOTE_WORKERSTOOL=True \
  -e REPOSITORY_MANAGER_DEFAULT_BRANCH=main \
  -e REPOSITORY_MANAGER_THREADS=12 \
  -e RM_CPU_FRACTION=0.20 \
  -e RM_GATE_BEFORE_PUSH=true \
  -e RM_GATE_TIMEOUT_SECONDS=1800 \
  -e RM_JOB_STALE_SECONDS=1800 \
  -e RM_MAX_WORKERS=8 \
  -e RM_RAM_FRACTION=0.20 \
  -e RM_WORKER_MEM_GB=1.5 \
  -e WORKSPACE_MANAGEMENTTOOL=True \
  -e WORKSPACE_YML=workspace.yml \
  -e WORKTREETOOL=True \
  registry.example.invalid/repository-manager@sha256:<digest> repository-manager-mcp

For containerized network HTTP, supply an authenticated TLS ingress (or direct server TLS), exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy through the operator-owned deployment profile. The generator does not emit an unauthenticated non-loopback listener.

Auto-generated from the code-read env surface (MCP_TOOL_MODE + package vars) — do not edit.

Additional Deployment Options

repository-manager can run as a local stdio process or container, or behind a remote network boundary. The Deployment guide carries the detailed transport contract.

  • Local container — launch a reviewed immutable image as a least-privilege stdio child with no listener or published port.

  • Remote URL — connect through an operator-supplied authenticated HTTPS ingress. Keep its URL, outbound identity references, trust profile, and exact MCP_ALLOWED_HOSTS in AgentConfig.

Environment Variables

Package environment variables

Variable

Example

Description

HOST

0.0.0.0

PORT

8000

TRANSPORT

stdio

options: stdio, streamable-http, sse

ENABLE_OTEL

True

OTEL_EXPORTER_OTLP_ENDPOINT

http://localhost:8080/api/public/otel

OTEL_EXPORTER_OTLP_PUBLIC_KEY_REF

secret://observability/otlp-public-key

OTEL_EXPORTER_OTLP_SECRET_KEY_REF

secret://observability/otlp-secret-key

OTEL_EXPORTER_OTLP_PROTOCOL

http/protobuf

EUNOMIA_TYPE

none

options: none, embedded, remote

EUNOMIA_POLICY_FILE

mcp_policies.json

EUNOMIA_REMOTE_URL

http://eunomia-server:8000

CONNECTOR_CONFIG_DIR

—

override of ~/.config/scion-sdk for the capacity-seed inventory.yaml lookup

REPOSITORY_MANAGER_WORKSPACE_ROOT

—

runtime-injected root; never persist a machine path

REPOSITORY_MANAGER_WORKSPACE

—

optional override of REPOSITORY_MANAGER_WORKSPACE_ROOT

WORKSPACE_PATH

—

compatibility workspace-root override

WORKSPACE_YML

workspace.yml

prefer the XDG scion-sdk copy at runtime

WORKSPACE_REPORTS

—

optional report directory; defaults beneath the workspace root

REPOSITORY_MANAGER_WORKTREE_ROOT

—

optional worktree root; injected at runtime

REPOSITORY_MANAGER_DEFAULT_BRANCH

main

default branch name for git operations

REPOSITORY_MANAGER_THREADS

12

parallel threads for git operations

RM_MAX_WORKERS

8

explicit worker-count override (skips auto-sizing from CPU count)

RM_JOB_STALE_SECONDS

1800

seconds before an in-flight job is treated as stale by the watchdog

RM_GATE_BEFORE_PUSH

true

run the pre-commit gate before pushing (set false to bypass)

RM_TASK_LEDGER_FLEET

—

optional: caller identity (claude/codex/human/vllm) recorded against a task_queue reservation

RM_TASK_LEDGER_SESSION

—

optional: caller's lane/session id recorded against a task_queue reservation

RM_DEPENDENCY_READINESS_OVERRIDE_REASON

—

optional: non-empty human reason bypasses the dependency-readiness gate

UV_INDEX_URL

—

optional: package index consulted by the dependency-readiness artifact-availability check

UV_EXTRA_INDEX_URL

—

optional: space-separated extra package indexes for the dependency-readiness check

PIP_INDEX_URL

—

optional: pip fallback index consulted by the dependency-readiness artifact-availability check

PIP_EXTRA_INDEX_URL

—

optional: space-separated pip fallback extra indexes for the dependency-readiness check

REPOSITORY_MANAGER_CLONE_FILTER

—

optional git clone filter: blob:none or tree:0

CODE_ENHANCER_SCRIPTS_DIR

—

optional code-enhancer helper scripts directory

COMMIT_IDENTITY_ALLOWLIST

—

path to the fleet commit-identity allowlist JSON (shared with pipelines_hooks' commit gate); read by repository-manager-governance history-identity

GITLAB_URL

https://gitlab.com

GitLab base URL (alias: GITLAB_HOST)

GITLAB_HOST

https://gitlab.com

legacy alias for GITLAB_URL

GITLAB_TOKEN

secret-injected

GitLab access token (alias: GITLAB_PRIVATE_TOKEN)

GITLAB_PRIVATE_TOKEN

secret-injected

legacy alias for GITLAB_TOKEN

GITHUB_TOKEN

secret-injected

GitHub access token (alias: GH_TOKEN)

GH_TOKEN

secret-injected

legacy alias for GITHUB_TOKEN

GIT_OPERATIONSTOOL

True

These names match the authoritative "Toggle Env Var" column in the README MCP tools table (condensed action-routed surface).

PROJECT_MANAGEMENTTOOL

True

WORKSPACE_MANAGEMENTTOOL

True

MISCTOOL

True

DEVELOPMENT_SURFACESTOOL

True

LANETOOL

True

WORKTREETOOL

True

MERGE_QUEUETOOL

True

BUILDTOOL

True

PROJECTTOOL

True

GATESTOOL

True

ROLLOUTTOOL

True

Enables rm_rollout (dependency floor rollout).

CONCEPTSTOOL

True

REMOTE_WORKERSTOOL

True

AUTH_TYPE

bearer

authentication type (e.g. bearer, none)

MCP_URL

http://localhost:8000

DOCS_READINESSTOOL

True

RM_GATE_TIMEOUT_SECONDS

1800

Wall-clock ceiling, in seconds, for one pre-commit gate stage (repository_manager/gates.py). Unset uses the per-stage built-in default.

MERGE_QUEUE_DRAIN_DEADLINE_SECONDS

180

per-repository fast queue drain wall-clock deadline

MERGE_QUEUE_GLOBAL_DEADLINE_SECONDS

3600

whole fast queue invocation wall-clock deadline

MERGE_QUEUE_MAX_AGE_SECONDS

86400

queued-record age limit before fail-closed omission

MERGE_QUEUE_LEASE_TTL_SECONDS

14400

repo-scoped queue lease; must exceed the drain deadline

RM_CPU_FRACTION

0.20

fraction of logical cores budgeted for validation workers

RM_RAM_FRACTION

0.20

fraction of host RAM budgeted for validation workers

RM_WORKER_MEM_GB

1.5

assumed RAM per validation worker for auto-sizing

REPOSITORY_MANAGER_COMMAND

—

optional executable used by the queue runner

REPOSITORY_MANAGER_MCP_IMAGE

—

Set to an image@sha256:.

AGENT_UTILITIES_HOST_INVENTORY

—

Canonical host identities and capability roles for cross-host lane/concept scoping, as a JSON document; unset uses no inventory (every host treated as unknown). See repository_manager/governance/lanes.py's _host_inventory().

AU_LANE_TEMP_ROOT

—

Absolute override for the per-lane temp root (pytest basetemp / TMPDIR / pre-commit store / cargo target dir); unset uses the default $HOME/.al/ root. See lanes.py's _configured_lane_temp_root().

CARGO_TARGET_DIR

—

Cargo's own target-dir override. lane_guard.py's cargo-target-override check reads this to refuse a shared/global CARGO_TARGET_DIR that would both serialize and corrupt concurrent lane builds; it is not set by this package.

Inherited scion-sdk variables (apply to every connector)

Variable

Example

Description

MCP_TOOL_MODE

intent

Tool surface: intent | condensed | verbose | both

MCP_ENABLED_TOOLS

—

Comma-separated tool allow-list

MCP_DISABLED_TOOLS

—

Comma-separated tool deny-list

MCP_ENABLED_TAGS

—

Comma-separated tag allow-list

MCP_DISABLED_TAGS

—

Comma-separated tag deny-list

MCP_CLIENT_AUTH

—

Outbound MCP child auth: oidc-client-credentials | basic | none

OIDC_CLIENT_ID

—

OIDC client id (service-account auth)

OIDC_CLIENT_SECRET_REF

secret://identity/oidc-client-secret

Runtime secret reference for the OIDC service account

MCP_BASIC_AUTH_USERNAME

—

HTTP Basic username (MCP_CLIENT_AUTH=basic)

MCP_BASIC_AUTH_PASSWORD_REF

secret://identity/mcp-basic-password

Runtime secret reference for HTTP Basic auth (MCP_CLIENT_AUTH=basic)

DEBUG

False

Verbose logging

PYTHONUNBUFFERED

1

Unbuffered stdout (recommended in containers)

PROVIDER

—

Operator-configured LLM provider for the agent

MODEL_ID

—

Operator-configured model id for the agent

ENABLE_WEB_UI

True

Serve the AG-UI web interface

69 package + 15 inherited variable(s). Auto-generated from .env.example + the shared scion-sdk set — do not edit.

Every variable the server and agent read, sourced from .env.example.

MCP server / transport

Variable

Description

Default

TRANSPORT

stdio, streamable-http, or sse

stdio

HOST

Bind host (HTTP transports)

0.0.0.0

PORT

Bind port (HTTP transports)

8000

MCP_TOOL_MODE

Tool surface: condensed, verbose, or both

condensed

MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS

Comma-separated tool allow/deny list

—

MCP_ENABLED_TAGS / MCP_DISABLED_TAGS

Comma-separated tag allow/deny list

—

PYTHONUNBUFFERED

Unbuffered stdout (recommended in containers)

1

Workspace & repository management

Variable

Description

Default

REPOSITORY_MANAGER_WORKSPACE

Root directory of the git workspace to manage

deployment-provided

WORKSPACE_PATH

Fallback workspace root when REPOSITORY_MANAGER_WORKSPACE is unset

deployment-provided

WORKSPACE_YML

Workspace manifest filename (resolved under the workspace root)

workspace.yml

WORKSPACE_REPORTS

Directory where generated reports are written

—

REPOSITORY_MANAGER_WORKTREE_ROOT

Root directory for managed git worktrees

deployment-provided

REPOSITORY_MANAGER_DEFAULT_BRANCH

Default branch name for git operations

main

REPOSITORY_MANAGER_THREADS

Parallel threads for git operations

12

Operations & gating

Variable

Description

Default

RM_MAX_WORKERS

Explicit worker-count override (skips auto-sizing from CPU count)

—

RM_JOB_STALE_SECONDS

Seconds before an in-flight job is treated as stale by the watchdog

1800

RM_GATE_BEFORE_PUSH

Run the pre-commit gate before pushing (set false to bypass)

true

Version-control provider credentials

Variable

Description

Default

GITLAB_URL

GitLab base URL (alias: GITLAB_HOST)

—

GITLAB_TOKEN

GitLab access token (alias: GITLAB_PRIVATE_TOKEN)

—

GITHUB_TOKEN

GitHub access token (alias: GH_TOKEN)

—

Tool toggles

Each action-routed tool can be disabled individually via its toggle env var (set to false). The full list is in the Available MCP Tools table above.

Variable

Description

Default

GIT_OPERATIONSTOOL

Enable bulk Git operations (rm_git)

True

PROJECT_MANAGEMENTTOOL

Enable project + worktree management (rm_projects / rm_worktree)

True

WORKSPACE_MANAGEMENTTOOL

Enable workspace organization (rm_workspace)

True

Telemetry & governance

Variable

Description

Default

ENABLE_OTEL

Enable OpenTelemetry export

True

OTEL_EXPORTER_OTLP_ENDPOINT

OTLP collector endpoint

—

OTEL_EXPORTER_OTLP_PUBLIC_KEY / OTEL_EXPORTER_OTLP_SECRET_KEY

OTLP auth keys

—

OTEL_EXPORTER_OTLP_PROTOCOL

OTLP protocol (e.g. http/protobuf)

—

EUNOMIA_TYPE

Authorization mode: none, embedded, remote

none

EUNOMIA_POLICY_FILE

Embedded policy file

mcp_policies.json

EUNOMIA_REMOTE_URL

Remote Eunomia server URL

—

----------|-------------|---------| | MCP_URL | URL of the MCP server the agent connects to | http://localhost:8000/mcp | | PROVIDER | LLM provider (e.g. openai) | openai | | MODEL_ID | Model id (e.g. gpt-4o) | gpt-4o | | ENABLE_WEB_UI | Serve the AG-UI web interface | True |


Security & Governance

Built directly upon the enterprise-ready Scion SDK core, standard security parameters are fully supported:

Access Control & Policy Enforcement

  • Eunomia Policies: Fine-grained, policy-driven tool authorization. Supports none, local embedded (mcp_policies.json), or centralized remote modes.

  • OIDC Token Delegation: Compliant with RFC 8693 token exchange for flowing authenticating user credentials from Web UI / ACP → Agent → MCP.

  • Scoped Credentials: Execution context runs restricted to the specific caller identity.

Runtime Security Grid

Feature

Feature

Enablement

Tool Guard

Sensitivity inspection with human-in-the-loop validation

Enabled by default

Prompt Injection Defense

Input scanning, repetition monitoring, and recursive loop blocks

Enabled by default

Context Safety Guard

Stuck-loop detectors and contextual overflow preemptive alerts

Enabled by default


Installation

Pick the extra that matches what the operator want to run:

Extra

Installs

Use when

repository-manager[mcp]

Connector-focused MCP server (scion-sdk — FastMCP/FastAPI + epistemic-graph[full])

The operator only run the MCP server (smallest install / image)

repository-manager[all]

mcp plus pre-commit / bump2version

Development

# Connector-focused MCP server (includes the shared graph engine)
uv pip install "repository-manager[mcp]"

# Everything (development)
uv pip install "repository-manager[all]"      # or: python -m pip install "repository-manager[all]"

Container image (:mcp)

docker/Dockerfile builds the MCP-server image (--target mcp):

Image tag

Build target

Contents

Entrypoint

example/repository-manager:mcp

--target mcp

repository-manager[mcp] — connector-focused, includes epistemic-graph[full]; no model-orchestration stack

repository-manager-mcp

docker build --target mcp   -t example/repository-manager:mcp    docker/   # connector-focused MCP server

docker/mcp.compose.yml runs the connector-focused :mcp server.

Knowledge-graph database (epistemic-graph)

The [mcp] extra carries the epistemic-graph engine through the required Scion SDK core dependency (epistemic-graph[full]). The [mcp] extra keeps the server connector-focused. Local deployments can use the bundled engine. For production or shared state, run epistemic-graph as a dedicated database service and configure the runtime to use it. Deployment recipes (single-node + Raft HA), connection configuration, and architecture diagrams are documented in the epistemic-graph deployment guide.


Repository Owners

GitHub followers GitHub User's stars


Documentation

The complete documentation is published as the official documentation site and is the recommended reference for installation, deployment, and day-to-day operation.

Page

Contents

Installation

pip, source, extras, prebuilt Docker image

Deployment

run the MCP and agent servers, Compose, Caddy + Technitium, env config

Usage

the MCP tools, the Git client, the CLI

Overview

ecosystem role, enterprise readiness, architecture

Dependency rollout

roll a dependency floor across the fleet through PRs

Concepts

concept registry (CONCEPT:RM-*)

AGENTS.md is the canonical contributor/agent guidance.


Contribute

Contributions are welcome! Please ensure code quality by running local checks before submitting pull requests:

  • Format code using ruff format .

  • Lint code using ruff check .

  • Validate type-safety with mypy .

  • Ran test suites using pytest

Governed capability contract

This package ships a compact canonical skill surface with specialist procedures kept as referenced workflows. The current MCP tools, skill metadata, connector_manifest.yml, ontology, mappings, shapes, fixtures, migrations, tool-schema fingerprints, and certification metadata form one versioned capability contract. Validate them together; do not rely on stale tool names or historical per-task skill wrappers.

Runtime endpoints, credentials, certificate trust, tenant identity, retention, and observability policy are deployment inputs and are never packaged values. See Configuration, trust, and privacy before enabling a network transport, connector ingestion, Arbora delegation, or trace export.

Available Tools

120 tools
repository_ingest_repositoriesRepository Ingest RepositoriesB

Natively ingest git repositories into epistemic-graph as typed :GitRepository nodes.

Enumerates repositories across a GitLab instance / GitHub org via the real VCS enumerator and pushes them (typed :GitRepository nodes with vcs/clone_url/web_url/ default_branch provenance) into the knowledge graph via the fast engine client. Best-effort: returns {"ingested": None} when no engine is reachable. CONCEPT:MERISTEM-KG.ingest.enterprise-source-extractor.

Inputs: vcs, scopes, max_repos. Returns: object

repository_manager_add_projectAdd projectB

Stage all changes (git add -A) for a single Git project.

Inputs: path.

repository_manager_add_projectsAdd projectsC

Stage all changes for multiple projects in parallel.

Inputs: project_dirs.

repository_manager_build_projectsBuild projectsB

Build projects serially so compilation cannot exhaust the workstation.

Inputs: threads.

repository_manager_bulk_bumpBulk bumpB

Bumps the version for all projects in the workspace in parallel.

Inputs: part (required), dry_run, exclude, verbose.

repository_manager_bump_versionBump versionA

Bump the version of the project using bump2version.

Args: part (str): The part of the version to bump (major, minor, patch). allow_dirty (bool): Whether to allow dirty working directory. path (str): The path to the project directory. dry_run (bool): Whether to perform a dry run. verbose (bool): Whether to use verbose output (for dry-run visibility). force (bool): If the target version's tag already exists locally (an orphan tag from a prior partial bump that left the version file un-updated), delete that local tag and re-bump instead of silently skipping. The orphan tag must NOT be on the remote.

Returns: GitResult: Result of the operation.

Inputs: part (required), path, force, dry_run, +2 more.

repository_manager_cleanup_artifactsCleanup artifactsC

Removes test artifacts and temporary files from the specified directory.

Inputs: target_dir (required).

repository_manager_clone_projectsClone projectsC

Clone all specified Git projects in parallel using multiple threads.

Returns: List[GitResult]: A list of GitResult objects, one for each clone operation.

Inputs: projects.

repository_manager_clone_repositoryClone repositoryB

Clone a single Git repository to a specific target path.

Args: url (str): The repository URL to clone. target_path (str): The absolute path where the repository should be cloned.

Returns: GitResult: The result of the Git clone command.

Inputs: url (required), target_path (required).

repository_manager_commit_code_projectCommit code projectA

Stage ALL changes (git add -A), optionally gate on pre-commit, then commit.

This is the per-repo "commit our feature code" step the release pipeline runs BEFORE bumping versions. Unlike :meth:commit_project it stages untracked files too (git add -A) and runs the project's pre-commit hooks (auto-formatters land in the same commit), so feature code is never left behind for an implicit push-time commit.

If pre-commit fails for real (not just auto-format), the failure is surfaced and nothing is committed.

Inputs: message (required), path, run_precommit.

repository_manager_commit_code_projectsCommit code projectsB

Concurrently stage + pre-commit + commit feature code across projects.

The "add all our code, pre-commit, then commit" release-prep step, throttled by self.threads (the 20% CPU/RAM cap). Scales to thousands of repositories.

Inputs: message (required), project_dirs, run_precommit.

repository_manager_commit_projectCommit projectB

Commit staged changes (git commit -m "{message}") for a single Git project.

Inputs: message (required), path.

repository_manager_commit_projectsCommit projectsC

Commit staged changes for multiple projects in parallel.

Inputs: message (required), project_dirs.

repository_manager_create_projectCreate projectB

Create a new project directory and initialize it as a git repository.

Args: path (str): The path of the project directory to create.

Returns: GitResult: Result of the operation.

Inputs: path (required).

repository_manager_discover_projectsDiscover projectsA

Scan self.path for immediate subdirectories containing a .git folder. Populates and returns self.project_map.

Inputs: no named parameters. Returns: object

repository_manager_generate_markdown_summaryGenerate markdown summaryC

Generates a beautiful markdown summary of bulk operation results.

Inputs: results (required), operation (required).

repository_manager_generate_workspace_templateGenerate workspace templateC

Generates a workspace.yml template at the specified path.

Inputs: target_path (required), use_default.

repository_manager_get_consolidated_skill_pathsGet consolidated skill pathsA
Read-onlyIdempotent

Returns absolute paths to the 15 specific building and documentation skills.

Inputs: no named parameters. Returns: result

repository_manager_get_project_mapGet project mapA
Read-onlyIdempotent

Returns the mapping of repository URLs to their local project paths. Ensures paths are absolute and expanded.

Inputs: no named parameters. Returns: object

repository_manager_get_readmeGet readmeA
Read-onlyIdempotent

Get the content and path of the README.md file in the specified path.

Args: path (str, optional): The directory path. Defaults to self.path.

Returns: ReadmeResult: Object containing 'content' and 'path' of the README.md file.

Inputs: path.

repository_manager_get_workspace_projectsGet workspace projectsA
Read-onlyIdempotent

Returns a list of project basenames (e.g. 'genius-agent') defined in the workspace.

Inputs: no named parameters. Returns: result

repository_manager_git_actionGit actionC

Execute a Git command in the specified directory.

The operation is admitted through descriptor-pinned helpers before any subprocess is started.

Inputs: command (required), env, path, quiet, +2 more.

repository_manager_install_projectInstall projectC

Install a Python project using pip install -e .[extra].

Inputs: path, extra.

repository_manager_install_projectsInstall projectsC

Bulk installs Python and Node projects in the workspace.

Inputs: extra, report, threads.

repository_manager_list_branchesList branchesA
Read-onlyIdempotent

Returns a dictionary mapping project basenames to their current active git branch.

Inputs: no named parameters. Returns: object

repository_manager_load_projects_from_yamlLoad projects from yamlC

Loads repository URLs from a YAML workspace file using Pydantic models. Strictly determines self.path relative to the configuration file.

Inputs: yaml_path (required).

repository_manager_pre_commitPre commitB

Execute pre-commit commands in the specified path.

Args: run (bool): Whether to run 'pre-commit run --all-files'. Default True. autoupdate (bool): Whether to run 'pre-commit autoupdate'. Default False. path (str, optional): Path to run in. Defaults to self.path.

Inputs: run, path, autoupdate.

repository_manager_pre_commit_projectsPre commit projectsC

Execute pre-commit commands for all projects in parallel.

Returns: List[GitResult]: A list of GitResult objects.

Inputs: run, projects, autoupdate.

repository_manager_pull_projectPull projectA

Pull updates for a single Git project and optionally checkout the default branch.

Args: path (str): The path to the project to pull. Defaults to self.path.

Returns: GitResult: The result of the pull operation.

Inputs: path.

repository_manager_pull_projectsPull projectsB

Pull updates for multiple projects in parallel.

Inputs: project_dirs.

repository_manager_push_projectPush projectA

Atomically publish a clean checkout's exact current branch and release tag.

Publication runs from a sealed private admin repository, uses only the authorized direct destination, and reads every remote ref back before reporting success. Dirty state, gate failure, identity/config drift, non-fast-forward updates, tag collisions, and partial atomic updates all refuse publication; GitHub push protection returns an actionable error.

Inputs: path.

repository_manager_push_projectsPush projectsC

Push updates for multiple projects in parallel.

Inputs: project_dirs.

repository_manager_save_workspace_configSave workspace configC

Saves the current or provided WorkspaceConfig to a YAML file.

Inputs: yaml_path (required), config.

repository_manager_set_threadsSet threadsC

Set the number of threads for parallel processing.

Args: threads (int): The number of threads.

Notes: If the input is invalid, defaults 6

Inputs: threads (required).

repository_manager_setup_from_yamlSetup from yamlA

Sets up the workspace structure from a YAML file.

install=True extends clone/pull with the fresh-machine bootstrap gap this closes (CONCEPT:RM-BOOTSTRAP): after every repository is cloned or pulled, materialize the .uv-workspace-siblings/ symlinks and run uv sync for scion-sdk and every cloned project that declares a path dependency on it, dependency-ordered (scion-sdk first). See :meth:install_projects for the mechanism and its documented limits. Install failures are reported, never masked -- setup_from_yaml returns status="error" if any project failed to install, even though every repository was still cloned/pulled.

Inputs: yaml_path (required), install.

repository_manager_test_projectsTest projectsC

Execute pytests for the specified projects in parallel.

Args: progress_phase: Phase name for live progress updates. progress_dict: Shared mutable dict for live progress reporting.

Inputs: targets (required), progress_dict, progress_phase.

repository_manager_update_dependencyUpdate dependencyC

Update a package's pinned version in a deps file (pyproject or requirements).

Inputs: file_path (required), new_version (required), package_name (required), dry_run.

repository_manager_validate_and_releaseValidate and releaseC

Validate projects in parallel and report whether all passed.

Inputs: threads. Returns: object

repository_manager_validate_single_projectValidate single projectA

Validates a single repository by running its FAST-tier gates.

Delegates to :func:repository_manager.gates.run_gate_stage (the same engine rm_gates uses) with stage="fast" (--hook-stage pre-commit). Under the two-tier gate model a repo's HEAVY hooks (pytest, cargo, uv lock --check, ...) are declared stages: [pre-push, manual] and are therefore correctly excluded here -- use rm_gates action=run stage=heavy for those.

Inputs: repo_path (required).

repository_manager_worktree_hygieneWorktree hygieneA

Audit (and optionally prune) session worktrees as a release-flow step.

Wraps :meth:WorktreeManager.audit. Read-only by default — it returns the safe_to_prune/do_not_disturb classification so a release run can report what could be cleaned without touching anything. With prune=True it removes only merged worktrees (and dangling admin pointers), never active/stale work or orphaned directories. This is the audit-aware cleanup the release pipeline runs instead of a blind reaper. (CONCEPT:RM-WORKTREE-AUDIT)

Inputs: base, prune, stale_days. Returns: object

rm_build_artifactsArtifactsC

Artifacts (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

Keyed by (repo, tree-sha, feature-set, toolchain-fingerprint, target-triple). The DEDUP is the value: N lanes asking for the same build today each pay for a full cargo/pnpm build into their own target-isolated/node_modules — measured at 21.7 GB across 4 duplicate directories after pruning. This tool publishes named artifacts to a shared, checksummed cache instead.

Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted.

Co-location: this tool always passes colocated=True to the underlying reservation, because being inside this pinned MCP server process IS the proof of same-node execution that a bare CLI invocation cannot provide — fcntl leases do not arbitrate across nodes, and the lease files live under an NFS-exported path. Route build requests through this tool rather than a bare local invocation when you are not certain you are on the pinned node.

Arbitration is advisory (D-CP-8): an agent running cargo build directly bypasses this broker entirely.

Inputs: key, host, spec, repo_path, +3 more. Returns: object

rm_build_explainExplainC

Explain (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

Keyed by (repo, tree-sha, feature-set, toolchain-fingerprint, target-triple). The DEDUP is the value: N lanes asking for the same build today each pay for a full cargo/pnpm build into their own target-isolated/node_modules — measured at 21.7 GB across 4 duplicate directories after pruning. This tool publishes named artifacts to a shared, checksummed cache instead.

Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted.

Co-location: this tool always passes colocated=True to the underlying reservation, because being inside this pinned MCP server process IS the proof of same-node execution that a bare CLI invocation cannot provide — fcntl leases do not arbitrate across nodes, and the lease files live under an NFS-exported path. Route build requests through this tool rather than a bare local invocation when you are not certain you are on the pinned node.

Arbitration is advisory (D-CP-8): an agent running cargo build directly bypasses this broker entirely.

Inputs: key, host, spec, repo_path, +3 more. Returns: object

rm_build_gcGcC

Gc (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

Keyed by (repo, tree-sha, feature-set, toolchain-fingerprint, target-triple). The DEDUP is the value: N lanes asking for the same build today each pay for a full cargo/pnpm build into their own target-isolated/node_modules — measured at 21.7 GB across 4 duplicate directories after pruning. This tool publishes named artifacts to a shared, checksummed cache instead.

Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted.

Co-location: this tool always passes colocated=True to the underlying reservation, because being inside this pinned MCP server process IS the proof of same-node execution that a bare CLI invocation cannot provide — fcntl leases do not arbitrate across nodes, and the lease files live under an NFS-exported path. Route build requests through this tool rather than a bare local invocation when you are not certain you are on the pinned node.

Arbitration is advisory (D-CP-8): an agent running cargo build directly bypasses this broker entirely.

Inputs: key, host, spec, repo_path, +3 more. Returns: object

rm_build_requestRequestB

Request (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

Keyed by (repo, tree-sha, feature-set, toolchain-fingerprint, target-triple). The DEDUP is the value: N lanes asking for the same build today each pay for a full cargo/pnpm build into their own target-isolated/node_modules — measured at 21.7 GB across 4 duplicate directories after pruning. This tool publishes named artifacts to a shared, checksummed cache instead.

Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted.

Co-location: this tool always passes colocated=True to the underlying reservation, because being inside this pinned MCP server process IS the proof of same-node execution that a bare CLI invocation cannot provide — fcntl leases do not arbitrate across nodes, and the lease files live under an NFS-exported path. Route build requests through this tool rather than a bare local invocation when you are not certain you are on the pinned node.

Arbitration is advisory (D-CP-8): an agent running cargo build directly bypasses this broker entirely.

Inputs: key, host, spec, repo_path, +3 more. Returns: object

rm_build_statusStatusC
Read-onlyIdempotent

Status (rm_build). Content-addressed build broker for ANY repository (CONCEPT:RM-TASK-LEDGER).

Keyed by (repo, tree-sha, feature-set, toolchain-fingerprint, target-triple). The DEDUP is the value: N lanes asking for the same build today each pay for a full cargo/pnpm build into their own target-isolated/node_modules — measured at 21.7 GB across 4 duplicate directories after pruning. This tool publishes named artifacts to a shared, checksummed cache instead.

Honest degradation: a dirty tree or an unfingerprintable toolchain BUILDS — it never serves a possibly-stale artifact and never silently skips the cache as though it were consulted.

Co-location: this tool always passes colocated=True to the underlying reservation, because being inside this pinned MCP server process IS the proof of same-node execution that a bare CLI invocation cannot provide — fcntl leases do not arbitrate across nodes, and the lease files live under an NFS-exported path. Route build requests through this tool rather than a bare local invocation when you are not certain you are on the pinned node.

Arbitration is advisory (D-CP-8): an agent running cargo build directly bypasses this broker entirely.

Inputs: key, host, spec, repo_path, +3 more. Returns: object

rm_concepts_getGetC
Read-onlyIdempotent

Get (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_listListC
Read-onlyIdempotent

List (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_materializeMaterializeC

Materialize (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_reconcileReconcileB

Reconcile (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_releaseReleaseC

Release (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_reserveReserveB

Reserve (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_verify_candidateVerify CandidateC
Read-onlyIdempotent

Verify candidate (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_concepts_verify_generationVerify GenerationC
Read-onlyIdempotent

Verify generation (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

Inputs: lane_ref (required), repo_root (required), tenant_ref (required), limit, +22 more. Returns: object

rm_docs_readiness_applyApplyC

Apply (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup.

Inputs: confirm, manifest, workspace, repository. Returns: object

rm_docs_readiness_previewPreviewC
Read-onlyIdempotent

Preview (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup.

Inputs: confirm, manifest, workspace, repository. Returns: object

rm_docs_readiness_verifyVerifyC
Read-onlyIdempotent

Verify (rm_docs_readiness). Preview/apply/verify artifacts after per-repository readiness setup.

Inputs: confirm, manifest, workspace, repository. Returns: object

rm_gates_audit_fail_fastAudit Fail FastB
Read-onlyIdempotent

Audit fail fast (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_explainExplainC

Explain (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_phase_directionPhase DirectionB

Phase direction (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_phase_direction_herePhase Direction HereC

Phase direction here (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_profileProfileC

Profile (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_reposReposC

Repos (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_retestRetestB

Retest (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_runRunB

Run (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_statusStatusC
Read-onlyIdempotent

Status (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_xdist_applyXdist ApplyC

Xdist apply (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_gates_xdist_planXdist PlanC

Xdist plan (rm_gates). Run and inspect the two-tier (fast/heavy) pre-commit gate across repos.

The single tool that can actually drive both tiers of the two-tier gate model: stage="fast" exercises a repo's pre-commit-stage hooks, stage="heavy" exercises its pre-push-stage hooks (pytest, cargo, uv lock --check, ...) via pre-commit run --hook-stage <stage>.

Inputs: repo, fleet, repos, stage, +8 more. Returns: object

rm_git_addAddC

Add (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_cancelCancelC
DestructiveIdempotent

Cancel (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_cloneCloneC

Clone (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_commitCommitC

Commit (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_commit_codeCommit CodeB

Commit code (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_enumerateEnumerateC

Enumerate (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_pre_commitPre CommitC

Pre commit (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_pullPullC

Pull (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_pushPushC

Push (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_rawRawC

Raw (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_git_statusStatusC
Read-onlyIdempotent

Status (rm_git). Typed bulk Git operations; arbitrary host commands are prohibited.

Inputs: path, job_id, command, message, +4 more. Returns: result

rm_lane_doctorDoctorB

Doctor (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

Every check behind this tool exists because a specific collision destroyed real work while the rule that would have prevented it was written down, in prose, in front of the actor who broke it: editing a canonical checkout a background git reset then discarded; a git stash into the ONE refs/stash shared by ~54 worktrees; a shared CARGO_TARGET_DIR that corrupts rather than merely serializes; an unset PRE_COMMIT_HOME whose shared store swallows unstaged work; a foreign or stale worktree-local .venv worth ~167 phantom failures; and measuring a branch TIP that will never be the tree that lands. The exact all-extras environment managed by scripts/uv_workspace.py is accepted because it is lane-partitioned and synchronized before execution.

doctor is the one to reach for when something behaves impossibly — a test failing that cannot fail, a build that will not go green, a merge that keeps being refused. It answers in under a second and mutates nothing.

Inputs: env, base, path, repo, +2 more. Returns: object

rm_lane_envEnvC

Env (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

Every check behind this tool exists because a specific collision destroyed real work while the rule that would have prevented it was written down, in prose, in front of the actor who broke it: editing a canonical checkout a background git reset then discarded; a git stash into the ONE refs/stash shared by ~54 worktrees; a shared CARGO_TARGET_DIR that corrupts rather than merely serializes; an unset PRE_COMMIT_HOME whose shared store swallows unstaged work; a foreign or stale worktree-local .venv worth ~167 phantom failures; and measuring a branch TIP that will never be the tree that lands. The exact all-extras environment managed by scripts/uv_workspace.py is accepted because it is lane-partitioned and synchronized before execution.

doctor is the one to reach for when something behaves impossibly — a test failing that cannot fail, a build that will not go green, a merge that keeps being refused. It answers in under a second and mutates nothing.

Inputs: env, base, path, repo, +2 more. Returns: object

rm_lane_finishFinishC

Finish (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

Every check behind this tool exists because a specific collision destroyed real work while the rule that would have prevented it was written down, in prose, in front of the actor who broke it: editing a canonical checkout a background git reset then discarded; a git stash into the ONE refs/stash shared by ~54 worktrees; a shared CARGO_TARGET_DIR that corrupts rather than merely serializes; an unset PRE_COMMIT_HOME whose shared store swallows unstaged work; a foreign or stale worktree-local .venv worth ~167 phantom failures; and measuring a branch TIP that will never be the tree that lands. The exact all-extras environment managed by scripts/uv_workspace.py is accepted because it is lane-partitioned and synchronized before execution.

doctor is the one to reach for when something behaves impossibly — a test failing that cannot fail, a build that will not go green, a merge that keeps being refused. It answers in under a second and mutates nothing.

Inputs: env, base, path, repo, +2 more. Returns: object

rm_lane_healHealC

Heal (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

Every check behind this tool exists because a specific collision destroyed real work while the rule that would have prevented it was written down, in prose, in front of the actor who broke it: editing a canonical checkout a background git reset then discarded; a git stash into the ONE refs/stash shared by ~54 worktrees; a shared CARGO_TARGET_DIR that corrupts rather than merely serializes; an unset PRE_COMMIT_HOME whose shared store swallows unstaged work; a foreign or stale worktree-local .venv worth ~167 phantom failures; and measuring a branch TIP that will never be the tree that lands. The exact all-extras environment managed by scripts/uv_workspace.py is accepted because it is lane-partitioned and synchronized before execution.

doctor is the one to reach for when something behaves impossibly — a test failing that cannot fail, a build that will not go green, a merge that keeps being refused. It answers in under a second and mutates nothing.

Inputs: env, base, path, repo, +2 more. Returns: object

rm_lane_startStartC

Start (rm_lane). The lane lifecycle for concurrent agents and humans (CONCEPT:RM-LANE-DOCTOR).

Every check behind this tool exists because a specific collision destroyed real work while the rule that would have prevented it was written down, in prose, in front of the actor who broke it: editing a canonical checkout a background git reset then discarded; a git stash into the ONE refs/stash shared by ~54 worktrees; a shared CARGO_TARGET_DIR that corrupts rather than merely serializes; an unset PRE_COMMIT_HOME whose shared store swallows unstaged work; a foreign or stale worktree-local .venv worth ~167 phantom failures; and measuring a branch TIP that will never be the tree that lands. The exact all-extras environment managed by scripts/uv_workspace.py is accepted because it is lane-partitioned and synchronized before execution.

doctor is the one to reach for when something behaves impossibly — a test failing that cannot fail, a build that will not go green, a merge that keeps being refused. It answers in under a second and mutates nothing.

Inputs: env, base, path, repo, +2 more. Returns: object

rm_merge_queue_configConfigC

Config (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

Inputs: base, push, prune, branch, +3 more. Returns: object

rm_merge_queue_enqueueEnqueueA

Enqueue (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

Inputs: base, push, prune, branch, +3 more. Returns: object

rm_merge_queue_runRunA

Run (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

Inputs: base, push, prune, branch, +3 more. Returns: object

rm_merge_queue_statusStatusC
Read-onlyIdempotent

Status (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

Inputs: base, push, prune, branch, +3 more. Returns: object

rm_merge_queue_withdrawWithdrawC

Withdraw (rm_merge_queue). Serialized merge queue for ANY git repository (CONCEPT:RM-MERGE-QUEUE).

The canonical driver of parallel development: lanes take worktrees, work, then hand branches here, and the queue gates them as merged, fast-forwards the base, and prunes the worktree and branch. Set push false when a scheduler must leave publication to a separate push.

The queue does not know what a gate is. Gates are declared in the target repository's own .mergequeue.yaml — a command, a tier, a timeout, and how to compare its result against the base ref. scion-sdk declares pytest + ruff + its contract scripts; epistemic-graph declares cargo check --all-features + clippy; a docs repo could declare only a link check. A repository with no declaration is REFUSED rather than defaulted, because "declared no gates" and "has no queue configured" must not be the same value.

Gating is differential: only a failure the base ref does not already produce blocks a candidate — the base is legitimately red here, and an absolute gate once deadlocked a queue and stranded 19 branches. A baseline that cannot be produced REFUSES the candidate; it never degrades to allow-all.

run holds that repository's reconciliation-merge LEASE. If another runner holds it the call returns deferred: true with the holder — defer, do not retry in a loop.

landed vs pushed (D-W3WPS-3). Each outcome carries both, separately: landed means the declared base ref fast-forwarded in the LOCAL canonical checkout (proven by re-reading it); when push is true, pushed means that commit also reached the configured remote via the repo's own gated push path (_gate_before_push + push_project — the same pre-commit gates and GH013/divergent-remote handling a manual push gets). With push false, publication is deliberately deferred to a separate push. A push failure never fails the landing — landed: true, pushed: false is a legitimate, visible intermediate state; check push_error on the outcome for why. The queue's own run summary also reports pushed/landed_unpushed counts.

Inputs: base, push, prune, branch, +3 more. Returns: object

rm_projects_buildBuildA

Build (rm_projects). Bulk install, build, and validate Python projects.

The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete.

Inputs: extra, job_id, summary, threads, +7 more. Returns: result

rm_projects_installInstallB

Install (rm_projects). Bulk install, build, and validate Python projects.

The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete.

Inputs: extra, job_id, summary, threads, +7 more. Returns: result

rm_projects_validateValidateA

Validate (rm_projects). Bulk install, build, and validate Python projects.

The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete.

Inputs: extra, job_id, summary, threads, +7 more. Returns: result

rm_projects_validate_statusValidate StatusB

Validate status (rm_projects). Bulk install, build, and validate Python projects.

The 'validate' action submits validation as a background job and returns a job_id immediately. Use 'validate_status' with that job_id to poll progress and retrieve results once complete.

Inputs: extra, job_id, summary, threads, +7 more. Returns: result

rm_remote_workers_dispatch_buildDispatch BuildC

Dispatch build (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_host_loss_reconcileHost Loss ReconcileB

Host loss reconcile (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_profileProfileC

Profile (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_receive_artifactReceive ArtifactC

Receive artifact (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_recheckRecheckC

Recheck (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_register_workerRegister WorkerC

Register worker (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_seed_from_inventorySeed From InventoryC

Seed from inventory (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_stage_sourceStage SourceC

Stage source (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_remote_workers_verify_sourceVerify SourceC
Read-onlyIdempotent

Verify source (rm_remote_workers). Remote worker registry, immutable source staging, and artifact transport.

Composes RMDD-15's repository_manager.remote_execution package with the RMDD-08 CapacityInventory resource ledger. The optional tunnel-manager dependency is never required to import this tool: recheck/live remote dispatch refuse with a named, cause-preserving error when it is absent instead of raising an ImportError. host_loss_reconcile always refuses today: no live WorkItem-authoritative ResourceScheduler is wired into any repository-manager entrypoint yet, and this tool never substitutes a local in-memory reservation ledger for that authority.

Inputs: kind, path, root, actor, +31 more. Returns: object

rm_rollout_applyApplyD

Apply (rm_rollout).

Inputs: floor (required), dependency (required), jobs, only, +4 more. Returns: object

rm_rollout_planPlanC

Plan (rm_rollout).

Inputs: floor (required), dependency (required), jobs, only, +4 more. Returns: object

rm_rollout_releaseReleaseD

Release (rm_rollout).

Inputs: floor (required), dependency (required), jobs, only, +4 more. Returns: object

rm_rollout_statusStatusD
Read-onlyIdempotent

Status (rm_rollout).

Inputs: floor (required), dependency (required), jobs, only, +4 more. Returns: object

rm_workspace_fleet_evidence_checkFleet Evidence CheckC

Fleet evidence check (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_workspace_listListC
Read-onlyIdempotent

List (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_workspace_list_branchesList BranchesC
Read-onlyIdempotent

List branches (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_workspace_saveSaveC

Save (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_workspace_setupSetupC

Setup (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_workspace_templateTemplateC

Template (rm_workspace). Core workspace organization and configuration.

Inputs: install, yml_path, config_dict, use_default, +1 more. Returns: result

rm_worktree_addAddC

Add (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_auditAuditC
Read-onlyIdempotent

Audit (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_bulk_addBulk AddC

Bulk add (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_listListC
Read-onlyIdempotent

List (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_mergeMergeC

Merge (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_prunePruneC

Prune (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_removeRemoveC
DestructiveIdempotent

Remove (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_reset_branchReset BranchC
DestructiveIdempotent

Reset branch (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

rm_worktree_syncSyncC

Sync (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Inputs: base, into, path, repo, +8 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.1/5.0

    Scored across 120 tools

    Disambiguation1/5

    There is massive overlap across families: repository_manager_add_project vs rm_git_add, pull_project vs rm_git_pull, commit_project vs rm_git_commit, and many rm_gates_* tools share nearly identical descriptions. Several families (rm_lane, rm_merge_queue, rm_build, rm_worktree, rm_concepts, rm_remote_workers) repeat the same description for every action, so an agent cannot reliably infer which tool to use.

    Naming Consistency2/5

    Names are snake_case throughout, but the surface mixes long repository_manager_* prefixes with shorter rm_* families, and some tools use vague or internal action suffixes such as rm_gates_phase_direction_here and rm_gates_explain/profile. The repeated family prefixes help somewhat, but the inconsistent dual naming scheme and duplicated action vocabulary make it feel ad hoc.

    Tool Count1/5

    At 120 tools, the server is far beyond a reasonable tool surface for repository management. Many tools are near-duplicates, internal workflow phases, or thin wrappers around the same Git operations, so the count is an extreme mismatch rather than a well-scoped set.

    Completeness3/5

    The surface broadly covers cloning, pulling, pushing, committing, building, testing, validation, worktrees, merge queues, and workspace setup, so core repository workflows are present. However, there are notable gaps and placeholder-like areas such as empty rm_rollout descriptions, no clear project deletion/removal path, and no obvious branch creation/checkout/diff/log lifecycle outside a generic git action.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-oriented MCP server for coding agents that enables multi-project management through secure file operations, Git integration, and safe command execution. It supports project discovery across multiple root directories and provides robust audit logging with both STDIO and HTTP transport options.
      2
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.
      27
      MIT