Container Manager Mcp

CLI or API | MCP | Agent

Version: 2.3.0

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 Out of the Box!.

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 several 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 several Docker, Podman, Swarm, and/or Kubernetes contexts at once (ThreadPoolExecutor-backed), with health checks and lazy reconnect.
• Enterprise-Grade Security: Comprehensive 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 your 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/agent-utilities/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 need to expose Docker socket TCP ports.

Shared inventory: the cm_* host aliases you pass as host come from the same inventory.yml used by tunnel-manager — define your 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 utilize 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 Out of the Box! API. You 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.

Environment doctor

Not sure your environment is wired up? Run the guided doctor first. It probes every surface with real checks — python client libs + CLIs, CONTAINER_MANAGER_TYPE / toggles / K8S_CONTEXTS parsing, the tunnel-manager SSH inventory (and per-host reachability), the docker / podman daemons, and each kubernetes context — and prints concrete remediation for anything that is not OK, so you are walked through connecting to your environments. Available as the container-manager-doctor CLI and the cm_doctor MCP tool.

container-manager-doctor                       # diagnose everything (exit 1 if any FAIL)
container-manager-doctor --guided              # + probe every inventory host
container-manager-doctor --backend inventory --host <alias>
container-manager-doctor --backend kubernetes --context <ctx>
container-manager-doctor --backend docker --host <alias>
container-manager-doctor --json                # machine-readable report

The cm_doctor MCP tool mirrors it: action=run for a full sweep, or a focused check_backends / check_inventory / check_docker / check_podman / check_kubernetes. Each check returns {name, category, status: ok|warn|fail, detail, remediation} plus a summary. Start here, then follow the container-manager-config-walkthrough skill.

MCP

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

Available MCP Tools

Auto-generated — do not edit (synced by the mcp-readme-table pre-commit hook).

Condensed action-routed tools (default — MCP_TOOL_MODE=condensed)

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