Deployment¶

Deployment Options¶

repository-manager supports local stdio, a loopback-only development listener, a least-privilege stdio container, and a remote authenticated HTTPS boundary. Provider endpoint, credential, selector, identity, and trust material are supplied at runtime through AgentConfig; none is stored in this repository.

Installed stdio process¶

{
  "mcpServers": {
    "repository-manager": {
      "command": "repository-manager-mcp",
      "args": [],
      "env": {"MCP_TOOL_MODE": "intent"}
    }
  }
}

Loopback development listener¶

repository-manager-mcp --transport streamable-http --host 127.0.0.1 --port 8000

Do not expose this listener beyond loopback. Network deployments require direct TLS or an explicitly trusted TLS-terminating ingress, configured authentication, exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy.

Least-privilege local container¶

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 \
  registry.example.invalid/repository-manager@sha256:<digest> repository-manager-mcp

The operator projects the selected AgentConfig profile into the process at runtime; the image remains immutable and contains no environment connection profile.

Remote authenticated HTTPS endpoint¶

{
  "mcpServers": {
    "repository-manager": {"url": "https://service.example.invalid/mcp"}
  }
}

Store the real remote URL, outbound identity reference, and TLS-profile reference in AgentConfig, not in MCP client JSON or documentation.

This page covers running repository-manager as a long-lived server: the transports, a Docker Compose stack, the companion agent server, putting it behind a Caddy reverse proxy, and giving it a DNS name with Technitium.

repository-manager ships both an MCP server (console script repository-manager-mcp) and an A2A agent server (console script repository-manager-agent). The MCP server is a typed, deterministic tool surface a policy router / agent calls; the agent server wraps a Pydantic-AI graph orchestrator exposed over ACP and the Agent Web UI.

Run the MCP server¶

The transport is selected with --transport (or the TRANSPORT env var):

stdio (default)streamable-httpsse

repository-manager-mcp

For IDE / desktop MCP clients that launch the server as a subprocess.

repository-manager-mcp --transport streamable-http --host 0.0.0.0 --port 8000

A network server with a /health endpoint and /mcp route.

repository-manager-mcp --transport sse --host 0.0.0.0 --port 8000

Health check (HTTP transports):

curl -s http://localhost:8000/health        # {"status":"OK"}

Configuration (environment)¶

repository-manager is configured entirely from the environment. The required set:

Var	Default	Meaning
`REPOSITORY_MANAGER_WORKSPACE`	deployment-provided	Root directory containing the managed Git repositories
`REPO_MANAGER_URL`	`http://localhost:8000`	Base URL of the running service
`REPO_MANAGER_USERNAME`	`admin`	Service identity
`REPO_MANAGER_PASSWORD`	(unset)	Service credential / token
`HOST`	`0.0.0.0`	Bind address (HTTP transports)
`PORT`	`8000`	Bind port (HTTP transports)
`TRANSPORT`	`stdio`	`stdio`, `streamable-http`, or `sse`
`MISCTOOL`	`True`	Register the miscellaneous tool set
`GIT_OPERATIONSTOOL`	`True`	Register the bulk Git tool set
`WORKSPACE_MANAGEMENTTOOL`	`True`	Register the workspace-management tool set
`PROJECT_MANAGEMENT_TOOL`	`True`	Register the project-management tool set

The graph agent additionally reads LLM_ROUTER_MODEL, LLM_AGENT_MODEL, GRAPH_ROUTER_TIMEOUT, and GRAPH_VERIFIER_TIMEOUT. Telemetry (ENABLE_OTEL, OTEL_EXPORTER_OTLP_*) and access governance (EUNOMIA_TYPE, EUNOMIA_POLICY_FILE, EUNOMIA_REMOTE_URL) are optional. The full set, with required-vs-optional separation, is documented in .env.example. Copy it to .env and populate only what you use.

Docker Compose¶

The repo ships docker/mcp.compose.yml. It reads a sibling .env and publishes the HTTP server on :8000:

services:
  repository-manager-mcp:
    image: example/repository-manager@sha256:<digest>
    container_name: repository-manager-mcp
    hostname: repository-manager-mcp
    restart: always
    env_file:
      - ../.env
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports:
      - "8000:8000"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/health')"]
      interval: 30s
      timeout: 10s
      retries: 3

cp .env.example .env          # then edit REPOSITORY_MANAGER_WORKSPACE etc.
docker compose -f docker/mcp.compose.yml up -d
docker compose -f docker/mcp.compose.yml logs -f

Agent server¶

repository-manager ships a second console script, repository-manager-agent, that runs the integrated Pydantic-AI graph agent over the Agent Control Protocol (ACP) and the Agent Web UI (AG-UI). It connects to the MCP server it orchestrates via MCP_URL and listens on port 9047 by default.

export MCP_URL=http://localhost:8000/mcp
export PROVIDER=openai
export MODEL_ID=gpt-4o
repository-manager-agent

The repo ships docker/agent.compose.yml, which provisions the MCP server and the agent server together — the agent reaches the MCP server by container name:

services:
  repository-manager-mcp:
    image: example/repository-manager@sha256:<digest>
    hostname: repository-manager-mcp
    env_file: [../.env]
    environment:
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports: ["8000:8000"]

  repository-manager-agent:
    image: example/repository-manager@sha256:<digest>
    depends_on: [repository-manager-mcp]
    command: ["repository-manager-agent"]
    env_file: [../.env]
    environment:
      - HOST=0.0.0.0
      - PORT=9047
      - MCP_URL=http://repository-manager-mcp:8000/mcp
      - PROVIDER=${PROVIDER:-openai}
      - MODEL_ID=${MODEL_ID:-gpt-4o}
      - ENABLE_WEB_UI=True
      - ENABLE_OTEL=True
    ports: ["9047:9047"]

docker compose -f docker/agent.compose.yml up -d

Behind a Caddy reverse proxy¶

Expose the HTTP server on a hostname with automatic TLS. Add to your Caddyfile:

# Internal (self-signed) — homelab .example.invalid zone
repository-manager.example.invalid {
    tls internal
    reverse_proxy repository-manager-mcp:8000
}

# Public — automatic Let's Encrypt
repository-manager.example.com {
    reverse_proxy repository-manager-mcp:8000
}

Reload Caddy:

docker compose -f services/caddy/compose.yml exec caddy caddy reload --config /etc/caddy/Caddyfile

DNS with Technitium¶

Point the hostname at the host running Caddy. Via the Technitium API:

curl -s "http://technitium.example.invalid:5380/api/zones/records/add" \
  --data-urlencode "token=$TECHNITIUM_DNS_TOKEN" \
  --data-urlencode "domain=repository-manager.example.invalid" \
  --data-urlencode "zone=arpa" \
  --data-urlencode "type=A" \
  --data-urlencode "ipAddress=192.0.2.10" \
  --data-urlencode "ttl=3600"

…or add an A record repository-manager.example.invalid → <caddy-host-ip> in the Technitium web console (http://technitium.example.invalid:5380). The ecosystem technitium-dns-mcp automates this as a tool.

Register with an MCP client¶

Add to your client's mcp_config.json (multiplexer nickname rep):

{
  "mcpServers": {
    "repository-manager": {
      "command": "uv",
      "args": ["run", "repository-manager-mcp"],
      "env": {
        "REPOSITORY_MANAGER_WORKSPACE": "<WORKSPACE_ROOT>"
      }
    }
  }
}

For a remote HTTP server, point the client at http://repository-manager.example.invalid/mcp instead.