Komodo MCP Server

🦎 Komodo MCP Server

Model Context Protocol Server for [Komodo](https://github.com/moghtech/komodo)

Manage your Docker or Podman deployments through Komodo with AI assistants and automation tools.

Komodo MCP Server enables seamless interaction between AI assistants (like Claude, GitHub Copilot) and Komodo (Container Management Platform) for efficient container management, server orchestration, and deployment operations. The MCP-Server gives you the ability to control your Komodo-managed infrastructure by using natural language or automated workflows.

Features • Quick Start • Authentication • Documentation

Features

🛠️ Complete Infrastructure Control

• 88 Tools, 20 Categories — Full lifecycle management for containers, stacks, deployments, servers, builds, repos, procedures, actions, alerters, Docker Swarms (Komodo v2), variables, resource syncs, update history, Docker image/network/volume introspection, builders, tags and TOML export — from listing and inspecting to deploying, building, scaling and destroying.
• Remote Terminal Access — Execute commands on servers, containers, deployments, and stack services with real-time output streaming, exit codes, and progress reporting.
• Log Search & Analysis — Pattern-based log search across containers with configurable tail limits and match counting.

🔌 Deploy Anywhere

• Multi-Transport — Streamable HTTP (stateful), HTTPS with TLS, legacy SSE, and stdio. Same server, any client.
• Multi-Platform Docker — Production-ready images for amd64, arm64, arm/v7, and arm/v6 (Raspberry Pi). Non-root, multi-stage builds with tini init.
• Works with Any MCP Client — Claude Desktop, VS Code / GitHub Copilot, or any MCP-compatible tool. Runs via Docker, npx, or native Node.js.

🔐 Security & Authentication

• Three Auth Methods — API Key/Secret (recommended), username/password, or JWT token. All support Docker secrets via *_FILE variants.
• Auth Enabled by Default — Per-user local login in HTTP mode unless explicitly disabled. The global [komodo] connection is configured once at startup (or via env vars) and used only for stdio or auth-disabled deployments.
• Confirmation for Destructive Actions — Deletes, destroys, prunes, and shell execution ask the human operator for explicit approval first (MCP elicitation with a confirm checkbox). Fail-closed on clients that can't prompt; tunable via MCP_CONFIRM_DESTRUCTIVE / MCP_CONFIRM_FALLBACK.
• Hardened by Default — Input validation (Zod), rate limiting, DNS rebinding protection, security headers via Helmet, and central fail-closed secret redaction: every tool result (including exec output and retrieved logs) passes the framework's scrub boundary before it reaches the client transcript — see Secret Redaction.

⚡ Reliability & Operations

• Live Progress & Cancellation — Long-running operations (deploy, start, stop) report real-time progress. Cancel any operation mid-flight via AbortSignal.
• Auto-Reconnection — Connection monitoring with automatic recovery and exponential backoff. Auth failures stop retries immediately.
• Health & Readiness — Kubernetes-ready /health and /ready endpoints. komodo_health_check reports server version, connectivity, and auth status.

*Built on mcp-server-framework — a production-ready TypeScript MCP server framework with structured logging, OpenTelemetry, and session management.*

Available Tools (69)

Tip: Every tool carries _meta.category (one of config, container, server, stack, deployment, build, repo, procedure, action, alerter, swarm, resource_sync, variable, update, terminal, user, docker, builder, tag, toml) and a requiredScopes array (komodo:read / komodo:operate / komodo:admin), so MCP clients and gateways can filter or gate tools by category and three-tier RBAC.

Limit the tool surface (server-side). To keep a client's tool list - and its token cost - small, prune what the server registers with three optional env vars: MCP_TOOLS_ALLOWED_CATEGORIES (category allowlist; unset -> all), MCP_TOOLS_EXCLUDED_CATEGORIES (drop whole categories), and MCP_TOOLS_EXCLUDED_TOOLS (drop tools by name, e.g. komodo_exec). Use the exact category strings above. Pruned tools are absent from tools/list and not callable. This is purely subtractive - it never exposes more and never bypasses authentication or the read-only-when-open behavior.

List/info/logs tools support cursor pagination via { cursor, page_size } (1–100, default 25) and emit _meta.page.next_cursor when more items are available. inspect, info, logs, and search_logs responses also include a session-scoped ephemeral://... resource link so large payloads can be fetched out-of-band via resources/read; pass inline_full: true to force inlining.

Quick Start

Docker Compose (Recommended for HTTP)

Deploy as a persistent HTTP server — connect from any MCP client.

mkdir komodo-mcp && cd komodo-mcp

curl -O https://raw.githubusercontent.com/MP-Tool/komodo-mcp-server/main/docker/compose.yaml curl -O https://raw.githubusercontent.com/MP-Tool/komodo-mcp-server/main/docker/docker.env cp docker.env .env # Edit with your credentials docker compose up -d

-> [Full Docker Guide](docker/README.md)

Claude Desktop

Add to your claude_desktop_config.json (Settings -> Developer -> Edit Config):

"komodo-mcp-server": {

"command": "docker", "args": [ "run", "-i", "--rm", "-e", "KOMODO_URL=https://komodo.example.com:9120", "-e", "KOMODO_API_KEY=api-key", "-e", "KOMODO_API_SECRET=api-secret", "ghcr.io/mp-tool/komodo-mcp-server:latest" ] }

-> [Full Claude Guide](examples/claude/README.md)

VS Code / GitHub Copilot

Add to .vscode/mcp.json in your workspace:

{

"servers": { "Komodo MCP Server": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "KOMODO_URL=https://komodo.example.com:9120", "-e", "KOMODO_API_KEY=api-key", "-e", "KOMODO_API_SECRET=api-secret", "ghcr.io/mp-tool/komodo-mcp-server:latest" ] } } }

-> [Full VS Code Guide](examples/vscode/README.md) · [Node.js / npx (no Docker)](examples/node/README.md) · [All Integrations](examples/README.md)

Use

Once connected, ask Claude, Copilot, or any MCP-compatible assistant in plain language — it picks the tools. The tool each prompt drives is shown on the right:

| "Show containers on production-server" | `kom