Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add containerization-assist-mcp -- npx -y containerization-assist-mcp@1.5.0Ejecútalo en una terminal.
{ "mcpServers": { "containerization-assist-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirAn AI-powered containerization assistant that helps you build, scan, and deploy Docker containers through VS Code and other MCP-compatible tools.
Full control over containerization through Rego policies:
Example Policies Included:
See Policy Authoring Guide for details.
Add the following to your VS Code settings or create .vscode/mcp.json in your project:
{
"servers": {
"ca": {
"command": "npx",
"args": ["-y", "containerization-assist-mcp", "start"],
"env": {
"LOG_LEVEL": "info"
}
}
}
}
Restart VS Code to enable the MCP server in GitHub Copilot.
For direct tool usage without MCP protocol (e.g., VS Code extensions, programmatic access):
import { analyzeRepo, buildImageContext, scanImage } from 'containerization-assist-mcp/sdk';
import { execSync } from 'child_process';
// Simple function calls - no MCP server needed
const analysis = await analyzeRepo({ repositoryPath: './myapp' });
if (analysis.ok) {
console.log('Detected:', analysis.value.modules);
}
// buildImageContext returns build context with security analysis and commands
const buildContext = await buildImageContext({ path: './myapp', imageName: 'myapp:v1', platform: 'linux/amd64' });
if (buildContext.ok) {
const { securityAnalysis, nextAction } = buildContext.value;
console.log('Security risk:', securityAnalysis.riskLevel);
// Execute the generated build command from the build context directory
execSync(nextAction.buildCommand.command, {
cwd: buildContext.value.context.buildContextPath,
env: { ...process.env, ...nextAction.buildCommand.environment }
});
}
const scan = await scanImage({ imageId: 'myapp:v1' });
See the SDK integration examples for full SDK documentation.
For Windows, use the Windows Docker pipe:
"DOCKER_SOCKET": "//./pipe/docker_engine"
The easiest way to understand the containerization workflow is through an end-to-end example:
This MCP server guides you through a complete containerization workflow for a single application. The journey follows this sequence:
kubectl applyBefore starting, ensure you have:
docker ps should work)
/var/run/docker.sock accessible//./pipe/docker_engine accessible~/.kube/configkubectl cluster-info should work)Once configured in your MCP client (VS Code Copilot, Claude Desktop, etc.), use natural language:
Starting the Journey:
"Analyze my Java application for containerization"
Building the Container:
"Generate an optimized Dockerfile with security best practices"
"Build a Docker image tagged myapp:v1.0.0"
"Scan the image for vulnerabilities"
Deploying to Kubernetes:
"Generate Kubernetes manifests for this application"
"Prepare my cluster and deploy to the default namespace"
"Verify the deployment is healthy"
This server is optimized for one engineer containerizing one application at a time. Key characteristics:
The server detects and supports monorepo structures with multiple independently deployable services:
analyze-repo identifies monorepo patterns (npm workspaces, services/, apps/ directories)generate-dockerfile and generate-k8s-manifests support multi-module workflowsMulti-Module Workflow Example:
1. "Analyze my monorepo at ./my-monorepo"
→ Detects 3 modules: api-gateway, user-service, notification-service
2. "Generate Dockerfiles"
→ Automatically creates Dockerfiles for all 3 modules:
- services/api-gateway/Dockerfile
- services/user-service/Dockerfile
- services/notification-service/Dockerfile
3. "Generate K8s manifests"
→ Automatically creates manifests for all 3 modules
4. Optional: "Generate Dockerfile for user-service module"
→ Creates module-specific deployment manifests
Detection Criteria:
The server provides 11 MCP tools organized by functionality:
Interactive workflow tools that return step-by-step plans (output is collapsed by default in VS Code Copilot Chat):
All generated artifacts include version metadata so you can track which version of containerization-assist produced them.
Dockerfiles (generate-dockerfile):
The tool output includes attributionLabels.labels with a version label, included as a LABEL instruction in the generated Dockerfile:
Kubernetes Manifests (generate-k8s-manifests):
The tool output includes attributionLabels.annotations applied to all generated Kubernetes resource metadata:
Organizations can add custom labels via the policy system's orgStandards.requiredLabels configuration.
The following environment variables control server behavior:
Progress Notifications: Long-running operations (build, deploy, scan-image) emit real-time progress updates via MCP notifications. MCP clients can subscribe to these notifications to display progress to users.
Enable detailed logging of all tool executions to JSON files for debugging and auditing:
export CONTAINERIZATION_ASSIST_TOOL_LOGS_DIR_PATH=/path/to/logs
Log File Format:
ca-tool-logs-${timestamp}.jsonlca-tool-logs-2025-10-13T14-30-15-123Z.jsonlLog Contents:
{
"timestamp": "2025-10-13T14:30:15.123Z",
"toolName": "analyze-repo",
"input": { "path": "/workspace/myapp" },
"output": { "language": "typescript", "framework": "express" },
"success": true,
"durationMs": 245,
"error": "Error message if failed",
"errorGuidance": {
"hint": "Suggested fix",
"resolution": "Step-by-step instructions"
}
}
The logging directory is validated at startup to ensure it's writable.
The policy system uses OPA Rego for security, quality, and compliance enforcement. Rego is the industry-standard policy language from Open Policy Agent, providing expressive rules with rich built-in functions.
Default Behavior (No Configuration Needed):
By default, all policies in the policies/ directory are automatically discovered and merged:
policies/security-baseline.rego - Essential security rules (root user prevention, secrets detection, privileged containers)policies/base-images.rego - Base image governance (Microsoft Azure Linux recommendation, no :latest tag, deprecated versions)policies/container-best-practices.rego - Docker best practices (HEALTHCHECK, multi-stage builds, layer optimization)This provides comprehensive out-of-the-box security and quality enforcement.
The policy system supports four priority-ordered search paths for easy customization:
Priority Order (highest to lowest):
CUSTOM_POLICY_PATH environment variable (highest priority)<git-root>/.containerization-assist/policy/ (tracked in git)~/.config/containerization-assist/policy/ (XDG-compliant)policies/ (shipped with package, lowest priority)Migration Note: The
policies.user/directory is deprecated. For project-specific policies, use.containerization-assist/policy/at your git root. For user-wide policies, use~/.config/containerization-assist/policy/. The old directory still works but will log a deprecation warning.
# Option 1: Global policies (no env var needed)
mkdir -p ~/.config/containerization-assist/policy
# Copy example policy from the npm package
cp node_modules/containerization-assist-mcp/policies.user.examples/allow-all-registries.rego \
~/.config/containerization-assist/policy/
# Policies are auto-reloaded on the next tool execution — no restart needed
Or set a custom location in .vscode/mcp.json:
{
"servers": {
"ca": {
"env": {
"CUSTOM_POLICY_PATH": "/path/to/policies"
}
}
}
}
The policies.user.examples/ directory (included in the npm package) provides three ready-to-use examples:
See policies.user.examples/README.md for detailed usage.
Three production-ready Rego policies are included by default:
policies/security-baseline.rego - Essential security rules (root user prevention, secrets detection, privileged containers)policies/base-images.rego - Base image governance (Microsoft Azure Linux recommendation, no :latest tag, deprecated versions)policies/container-best-practices.rego - Docker best practices (HEALTHCHECK, multi-stage builds, layer optimization)User policies override built-in policies by package namespace.
Policy File Format (Rego):
package containerization.custom_policy
# Blocking violations
violations contains result if {
input_type == "dockerfile"
regex.match(`FROM\s+[^:]+:latest`, input.content)
result := {
"rule": "block-latest-tag",
"category": "quality",
"priority": 80,
"severity": "block",
"message": "Using :latest tag is not allowed. Specify explicit version tags.",
"description": "Prevent :latest for reproducibility",
}
}
# Non-blocking warnings
warnings contains result if {
input_type == "dockerfile"
not regex.match(`HEALTHCHECK`, input.content)
result := {
"rule": "suggest-healthcheck",
"category": "quality",
"priority": 70,
"severity": "warn",
"message": "Consider adding HEALTHCHECK instruction for container monitoring",
"description": "HEALTHCHECK improves container lifecycle management",
}
}
# Policy decision
default allow := false
allow if count(violations) == 0
# Result structure
result := {
"allow": allow,
"violations": violations,
"warnings": warnings,
"suggestions": [],
"summary": {
"total_violations": count(violations),
"total_warnings": count(warnings),
"total_suggestions": 0,
},
}
Priority Levels:
Using Policies:
# List discovered policies
npx containerization-assist-mcp list-policies
# List policies and show merged result
npx containerization-assist-mcp list-policies --show-merged
# Validate Dockerfile with policies (automatic discovery)
npx containerization-assist-mcp fix-dockerfile --path ./Dockerfile
Creating Custom Policies:
See Policy Customization Guide and existing policies in policies/ for examples.
Testing Policies:
# Validate policy syntax
opa check .containerization-assist/policy/my-policy.rego
# Run policy tests
opa test .containerization-assist/policy/
# Test with MCP Inspector
npx @modelcontextprotocol/inspector containerization-assist-mcp start
npx @modelcontextprotocol/inspector containerization-assist-mcp start
# Check Docker is running
docker ps
# Check socket permissions (Linux/Mac)
ls -la /var/run/docker.sock
# For Windows, ensure Docker Desktop is running
# Test with MCP Inspector
npx @modelcontextprotocol/inspector containerization-assist-mcp start
# Check logs with debug level
npx -y containerization-assist-mcp start --log-level debug
The server performs fast-fail validation when Kubernetes tools are used. If you encounter Kubernetes errors:
Kubeconfig Not Found
# Check if kubeconfig exists
ls -la ~/.kube/config
# Verify kubectl can connect
kubectl cluster-info
# If using cloud providers, update kubeconfig:
# AWS EKS
aws eks update-kubeconfig --name <cluster-name> --region <region>
# Google GKE
gcloud container clusters get-credentials <cluster-name> --zone <zone>
# Azure AKS
az aks get-credentials --resource-group <rg> --name <cluster-name>
Connection Timeout or Refused
# Verify cluster is running
kubectl get nodes
# Check API server address
kubectl config view
# Test connectivity to API server
kubectl cluster-info dump
# Verify firewall rules allow connection to API server port (typically 6443)
Authentication or Authorization Errors
# Check current context and user
kubectl config current-context
kubectl config view --minify
# Test permissions
kubectl auth can-i create deployments --namespace default
kubectl auth can-i create services --namespace default
# If using cloud providers, refresh credentials:
# AWS EKS: re-run update-kubeconfig
# GKE: run gcloud auth login
# AKS: run az login
Invalid or Missing Context
# List available contexts
kubectl config get-contexts
# Set a context
kubectl config use-context <context-name>
# View current configuration
kubectl config view
MIT License - See LICENSE file for details.
See SUPPORT.md for information on how to get help with this project.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.
TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support
{ "mcpServers": { "containerization-assist-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Containerization Assist se ejecuta localmente por stdio.
Última comprobación: 2026-11-11. TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support