An MCP server that connects AI assistants to Komodo so they can manage Docker or Podman infrastructure, including containers, stacks, deployments, servers, and remote terminal commands. It supports multiple transports and authentication methods for controlling Komodo-managed environments.
From the registry: MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
Please install the `komodo-mcp-server` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Komodo instance and API credentials** — Running Komodo container-management instance plus API key and secret (or username/password) to connect. (https://github.com/moghtech/komodo)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","komodo-mcp-server"]
- required environment variables:
- `KOMODO_URL`: Komodo server base URL. (example: `https://komodo.example.com:9120`)
- `KOMODO_API_KEY`: Komodo API key. (example: `<your-api-key>`)
- `KOMODO_API_SECRET`: Komodo API secret. (example: `<your-api-secret>`)
Note: Also distributed as a Docker image and supports streamable-http, SSE, and HTTPS transports.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.KOMODO_URLrequiredBase URL of the Komodo instance to connect to.KOMODO_API_KEYrequiredAPI key used for Komodo authentication (with API secret).KOMODO_API_SECRETrequiredAPI secret used for Komodo authentication (with API key).KOMODO_USERNAMErequiredUsername used for Komodo authentication (with password).KOMODO_PASSWORDrequiredPassword used for Komodo authentication (with username).KOMODO_JWT_TOKENrequiredJWT token used for Komodo authentication.Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.