Built-in shell + files
The in-box MCP server exposes shell and file operations over stdio — typed, bounded tools, not TTY scraping.
Every Containarium box runs an MCP server — shell and file operations, reachable on a hostname with TLS. Host the built-in one, or drop your own MCP server beside it, backed by real compute and persistent disk. Self-hostable, Apache 2.0.
$ containarium create mcp-box
✓ box mcp-box created
✓ MCP server listening · mcp-box.example.com
# point any MCP-aware agent at it, remotely
$ claude mcp add mcp-box https://mcp-box.example.com
Connected. Real shell + files, behind one endpoint.What you get
Most remote MCP servers are thin wrappers. Containarium backs the endpoint with a full Linux box — root, persistent disk, real network — so tool calls do real work and remember it.
The in-box MCP server exposes shell and file operations over stdio — typed, bounded tools, not TTY scraping.
Run your own MCP server inside the box next to the built-in one. The agent sees both, with no extra plumbing.
A sentinel gives the box a routable hostname with TLS; state survives between sessions. Reach the MCP server from anywhere.
Why host it this way
Tool calls run on an actual Linux box — install anything, run builds, hold state.
One box per agent or tenant, sandboxed, with optional eBPF network policy.
Apache 2.0 on your own VM — the MCP server and its data stay in your network.
MCP-native, so Claude Code, Cursor, Cline, or your own connect the same way.
A single hostname per box — no port juggling, no bespoke tunnels.
Scale to many boxes, each its own MCP server; the sentinel handles routing.
FAQ
Create a Containarium box. Each box runs an MCP server exposing shell and file operations on a routable hostname with TLS. Any MCP-aware agent connects remotely — and you can run your own MCP server inside the box alongside the built-in one.
An MCP server an agent reaches over the network rather than as a local process. Containarium backs the endpoint with a real Linux box, so tool calls run on actual compute with persistent state.
Yes — drop it into the box beside the built-in one; the agent sees both. The box gives it a real filesystem, network, and persistent disk, not a sandbox that resets between calls.
Yes — the in-box MCP server is open source (Apache 2.0) and runs on your own VM, so it and everything it touches stay in your network.
Start free on the hosted cloud, or self-host the open source on your VM.