TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support
Containerization MCP server exists for a simple reason — assistants are far more useful when they can act on Containerization directly instead of describing what you should do. TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support.
An AI-powered containerization assistant that helps you build, scan, and deploy Docker containers through VS Code and other MCP-compatible tools.
The server ships on npm as containerization-assist-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Containerization is connected, these are the calls the assistant has available:
create-containerization-policy — Step-by-step guidance for authoring a custom OPA Rego policykind-loop — Local dev loop: analyze → build → scan → deploy to Kindaks-loop — Remote dev loop: analyze → build → push → deploy to AKSPrerequisites — The Prerequisites tool exposed by this serverUtilities — The Utilities tool exposed by this serverYou will need 5 environment variables: LOG_LEVEL, DOCKER_SOCKET, CUSTOM_POLICY_PATH, DOCKER_HOST, CONTAINERIZATION_ASSIST_TOOL_LOGS_DIR_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Before starting, ensure you have: - Docker: Running Docker daemon with accessible socket (docker ps should work) - Linux/Mac: /var/run/docker.sock accessible - Windows: Docker Desktop with //./pipe/docker_engine accessible - Kubernetes (optional, for deployment features): - Valid kubeconfig at ~/.kube/config - Cluster connectivity (kubectl cluster-info should work) - Appropriate
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Containerization's toolset — create-containerization-policy, kind-loop, aks-loop and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Azure; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Containerization's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| create-containerization-policy | Step-by-step guidance for authoring a custom OPA Rego policy |
| kind-loop | Local dev loop: analyze → build → scan → deploy to Kind |
| aks-loop | Remote dev loop: analyze → build → push → deploy to AKS |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Utilities | The Utilities tool exposed by this server. |
{
"mcpServers": {
"containerization-assist": {
"command": "npx",
"args": ["-y", "containerization-assist-mcp"],
"env": {
"LOG_LEVEL": "your-value",
"DOCKER_SOCKET": "your-value",
"CUSTOM_POLICY_PATH": "your-value",
"DOCKER_HOST": "your-value",
"CONTAINERIZATION_ASSIST_TOOL_LOGS_DIR_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before starting, ensure you have: - Docker: Running Docker daemon with accessible socket (docker ps should work) - Linux/Mac: /var/run/docker.sock accessible - Windows: Docker Desktop with //./pipe/docker_engine accessible - Kubernetes (optional, for deployment features): - Valid kubeconfig at ~/.kube/config - Cluster connectivity (kubectl cluster-info should work) - Appropriate
| Variable | Description | Required |
|---|---|---|
| LOG_LEVEL | Configuration value read at startup. | Optional |
| DOCKER_SOCKET | Configuration value read at startup. | Optional |
| CUSTOM_POLICY_PATH | Filesystem location the server is allowed to use. | Optional |
| DOCKER_HOST | Endpoint or connection string the server talks to. | Optional |
| CONTAINERIZATION_ASSIST_TOOL_LOGS_DIR_PATH | Filesystem location the server is allowed to use. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.