Container Use MCP — Instalar & Demo en vivo

Por qué usarlo

Características clave

One isolated container per agent task — no host pollution
Multiple agents work in parallel on the same repo via git worktrees inside containers
Replay, diff, and discard any environment after the fact
Pre-baked language images (node, python, go) or BYO Dockerfile
Works with Claude Code, Cursor, Goose, Aider through the same MCP layer

Demo en vivo

Cómo se ve en la práctica

container-use-mcp.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "container-use-mcp": {
      "command": "cu",
      "args": [
        "mcp"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "container-use-mcp": {
      "command": "cu",
      "args": [
        "mcp"
      ]
    }
  }
}

Cursor usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "container-use-mcp": {
      "command": "cu",
      "args": [
        "mcp"
      ]
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "container-use-mcp": {
      "command": "cu",
      "args": [
        "mcp"
      ]
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "container-use-mcp",
      "command": "cu",
      "args": [
        "mcp"
      ]
    }
  ]
}

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

{
  "context_servers": {
    "container-use-mcp": {
      "command": {
        "path": "cu",
        "args": [
          "mcp"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

claude mcp add container-use-mcp -- cu mcp

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Container Use

Try three refactoring approaches in parallel, keep the best

👤 Engineers exploring design space ⏱ ~15 min intermediate

Cuándo usarlo: You have 3 different ideas for a refactor and want to see all of them run/pass tests before picking one.

Requisitos previos

Server/skill installed and authenticated — See repo README

Flujo

Spin up three isolated envs

Create three container-use environments named refactor-a/b/c, all on this repo at HEAD.✓ Copiado

→ Three env_ids printed
Apply each approach in its own env

In refactor-a do the strategy-pattern version; in -b inline everything; in -c extract a service object. Run the full test suite in each. Report pass/fail and diff size.✓ Copiado

→ Per-env test summary and diff stats
Pick the winner and merge

Apply the diff from refactor-b to my working copy. Discard the other two environments.✓ Copiado

→ Patch applied locally

Resultado: Three real experiments evaluated side-by-side without ever breaking your host repo.

Errores comunes

Forgetting to discard old envs leaks disk — Forgetting to discard old envs leaks disk — cu environment list then cu environment discard <id> periodically.

Combinar con: github · filesystem

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

container-use-mcp + github

Pair with github for complementary capabilities

Use this server together with github to complete a multi-step task.✓ Copiado

container-use-mcp + filesystem

Pair with filesystem for complementary capabilities

Use this server together with filesystem to complete a multi-step task.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
environment_create	name: str, image: str	Start a fresh sandbox for the next task	Local CPU/disk
environment_run_cmd	env_id, cmd	Execute build/test commands inside the sandbox	free
environment_file_write	env_id, path, contents	Apply edits without touching the host	free
environment_diff	env_id	Review the agent's work before merging back	free

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: See provider docs for rate limits
Tokens por llamada: Varies by tool
Monetario: See repo README for pricing details
Consejo: Cache tool results and avoid repeated identical calls.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: Use environment variables; never commit secrets

Salida de datos: Tool calls go to the provider's API as documented

Resolución de problemas

Errores comunes y soluciones

docker daemon not running

Container Use requires a local Docker or compatible runtime. Start Docker Desktop or colima.

Verificar: Run `docker ps` successfully

out of disk

Old environments aren't auto-pruned. Run cu environment list then cu environment discard <id> for anything older than a day.

Verificar: Check `docker system df`

Alternativas

Container Use vs otros

Alternativa	Cuándo usarla	Contrapartida
Dagger Cloud	You want hosted, multi-tenant agent envs	Paid; container-use is local-first

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills