
What is mcp-sandboxd?
mcp-sandboxd is an MCP-compatible server that allows running arbitrary commands inside isolated sandboxes in Docker or Kubernetes.
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿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.
AbrirDel publicador

mcp-sandboxd?mcp-sandboxd is an MCP-compatible server that allows running arbitrary commands inside isolated sandboxes in Docker or Kubernetes.
MCP server for running commands in persistent, isolated sandboxes on Docker or Kubernetes
The core idea is simple: an identifier (e.g. a conversation id) maps to a long-running sandbox environment reused across runs. This makes agent workflows feel like a "real machine", without exposing your host.
/artifacts and download them via the server HTTP endpoint.run_sandbox: run one or more commands in a sandbox keyed by identifier.delete_sandbox: delete a sandbox environment.restart_sandbox: recreate a fresh sandbox for an identifier.Write files inside the sandbox under /artifacts. After a run completes, the server copies artifacts out of the sandbox into ARTIFACTS_DIR and serves them over HTTP.
From an MCP client’s point of view this is the same for local Docker, Docker-in-Docker, and the Kubernetes-native backend: clients always download via GET /artifacts/... and never talk to the sandbox filesystem directly.
GET /artifacts/<identifier>/<run_id>/<path>GET /artifacts/<identifier>/latest/<path>make docker-build-sandbox
cp .env.example .env
make dev
This starts the server on http://localhost:8080.
http://localhost:8080/mcphttp://localhost:8080/mcp/events?run_id=...Below are example configs for connecting to a running server over HTTP + SSE.
// ~/.config/opencode/config.json
{
"mcpServers": {
"mcp-sandboxd": {
"type": "sse",
"url": "http://localhost:8080/mcp"
}
}
}
Add a custom connector and point it at your running server.
http://localhost:8080/mcp (or your deployed https://.../mcp)Starts mcp-sandboxd on http://localhost:8080/mcp.
{
"mcpServers": {
"mcp-sandboxd": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-p",
"8080:8080",
"-e",
"PORT=8080",
"-e",
"MCP_PATH=/mcp",
"-e",
"SANDBOX_BACKEND=docker",
"-e",
"SANDBOX_IMAGE=ghcr.io/jeliasson/mcp-sandboxd-sandbox:latest",
"-v",
"/var/run/docker.sock:/var/run/docker.sock",
"ghcr.io/jeliasson/mcp-sandboxd:latest"
]
}
}
}
General
Backend
no-new-privileges is enabled by default; sudo won’t work inside the sandbox.run_sandbox.options.as_user="root" for administrative operations.mcp-sandboxd in a dedicated namespace with default-deny egress.MCP server for running commands in persistent, isolated sandboxes on Docker or Kubernetes
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.
MCP Sandboxd se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. MCP server for running commands in persistent, isolated sandboxes on Docker or Kubernetes