Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"sandbox": {
"args": [
"--image",
"debian:latest"
],
"command": "/path/to/sandbox-mcp-server"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Docker sandbox MCP server with per-session containers. Each MCP session gets its own isolated Docker container with a dedicated data directory mounted as /home/user.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP Security Weekly
Get CVE alerts and security updates for Sandbox Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Docker sandbox MCP server with per-session containers. Each MCP session gets its own isolated Docker container with a dedicated data directory mounted as /home/user.
sandbox-{session_id})data_dir/sessions/{session_id}/ mounted as /home/user in container--transport flagSingle crate, seven source modules:
| Module | Responsibility |
|---|---|
src/main.rs | CLI parsing, Docker connection, entry point, transport selection |
src/mcp.rs | JSON-RPC 2.0 types, dispatch, tool definitions, stdio loop, server state |
src/http.rs | HTTP transport: axum server, Bearer auth, session management |
src/sandbox.rs | Path resolution: strip home prefix, reject traversal |
src/file.rs | File operations: read, write, list |
src/editor.rs | Editor operations: search, replace, replace_lines |
src/shell.rs | Docker shell: exec, spawn, kill, container lifecycle |
debian:latest)sandbox-mcp-server [OPTIONS]
Options:
--image <IMAGE> Docker image [default: debian:latest]
--data-dir <PATH> Base data directory [default: XDG_DATA_HOME/sandbox-mcp-server]
--timeout <MS> Shell command timeout in ms [default: 60000]
--max-output <BYTES> Max shell output bytes [default: 65536]
--transport <MODE> stdio or http [default: stdio]
--host <HOST> HTTP bind address [default: 127.0.0.1]
--port <PORT> HTTP port [default: 8080]
--auth <TOKEN> Bearer token for HTTP auth
--session-id <UUID> Resume an existing session by ID (stdio only)
--version Print version
cargo build --release
nix develop # reproducible dev environment with git hooks
nix build # build package
/)[start, end] inclusive (1-indexed)One JSON-RPC 2.0 object per line on stdin/stdout. A session is created automatically on startup.
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' | cargo run
To resume a previous session, pass --session-id with the UUID from a prior run:
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' | \
cargo run -- --session-id 550e8400-e29b-41d4-a716-446655440000
cargo run -- --transport http --port 8080 --auth secret123
Initialize (creates session, returns Mcp-Session-Id header):
curl -s -D- -X POST http://127.0.0.1:8080/mcp
... [View full README on GitHub](https://github.com/nizovtsevnv/sandbox-mcp-server#readme)