Container Manager Mcp
CLI or API | MCP
Documentation — Installation, deployment, usage across the API, CLI, MCP, and
A2A agent interfaces, and the multi-host control plane are maintained in the
official documentation.
Overview
Container Manager Mcp is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with Container Manager - manage Docker, Docker Swarm, Podman, and Kubernetes containers and workloads. MCP+A2A Servers By default!.
Full coverage across all three engines: Docker (incl. Swarm/service/stack/config/secret/node
operations via cm_docker_swarm), Podman (incl. pod/kube operations, generate/play kube, checkpoint/restore
via cm_podman), and a complete Kubernetes surface (RKE2 / k3s / vanilla) spanning workloads,
config, networking, storage, RBAC, cluster admin, governance, and observability through 8 themed cm_k8s_*
tools built on the official kubernetes Python client. A cm_multi_context tool lets an agent fan out
operations across multiple Docker/Podman/Swarm/Kubernetes contexts in parallel, and cm_ingest_inventory feeds
Docker, Swarm, and Kubernetes resources into the ontology-driven Knowledge Graph as typed nodes.
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.
- Full Docker + Swarm + Podman + Kubernetes Coverage: First-class support for Docker (incl. Swarm/service/stack/config/secret/node ops), rootless Podman (incl. pods,
generate/play kube, checkpoint/restore), and a full Kubernetes surface (RKE2 / k3s / vanilla) across workloads, config, networking, storage, RBAC, cluster admin, governance, and observability. See Kubernetes below.
- Multi-Context Parallel Operation:
cm_multi_context fans operations out across multiple Docker, Podman, Swarm, and/or Kubernetes contexts at once (ThreadPoolExecutor-backed), with health checks and lazy reconnect.
- 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).
- Ontology-Driven KG Ingestion:
cm_ingest_inventory maps live Docker/Swarm/Kubernetes inventory (containers, images, volumes, networks, services, nodes, pods, deployments, namespaces, native k8s Services) into typed OWL/RDF nodes for cross-source reasoning.
- Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.
Multi-Host & Zero-Script Remote Docker Orchestration
container-manager-mcp allows a single master instance of the MCP server on the operator's controller to route container and volume operations securely to remote hosts over SSH standard tunneling.
- Unified Inventory: Connection endpoints are loaded dynamically from the XDG shared inventory at
~/.config/scion-sdk/inventory.yml (.yml preferred; a legacy inventory.yaml is still read when no .yml exists).
- Zero TCP Socket Exposure: Operations route directly over the standard SSH channel securely, removing the must expose Docker socket TCP ports.
Shared inventory: the cm_* host aliases the operator pass as host come from the same
inventory.yml used by tunnel-manager — define the operator's fleet once. Create and validate
it with tunnel-manager inventory init / tunnel-manager inventory doctor. See
tunnel-manager's Inventory guide
for the full schema, template, and override options.
To configure and use the multi-host remote routing, see the detailed Multi-Host Architecture Guide.
CLI or API
This agent wraps the Container Manager - manage Docker, Docker Swarm, and Podman containers. MCP+A2A Servers By default! API. The operator can interact with it programmatically or via its integrated execution entrypoints.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
