Superserve — Claude Code MCP server: Firecracker sandboxes
Gives your agent isolated Firecracker microVMs: create a sandbox, run a command, move files around. Useful when code has to run off your own machine.
claude mcp add --env SUPERSERVE_API_KEY=<SUPERSERVE_API_KEY> --env SUPERSERVE_BASE_URL=<SUPERSERVE_BASE_URL> --transport stdio mcp -- npx -y @superserve/mcpWhat Superserve does
Superserve plugs into an MCP client and drives Superserve sandboxes. Locally it runs over stdio through npx, and each call targets a sandbox by id. There is also a hosted endpoint at https://mcp.superserve.ai over Streamable HTTP, so no local install is needed and the key travels as a bearer token.
The tool set is broad. sandbox_create spins up a sandbox and returns its id, sandbox_exec runs a shell command and hands back stdout, stderr and the exit code, while sandbox_files_read and sandbox_files_write handle files. sandbox_computer is the odd one out: it drives a GUI desktop with screenshots, mouse, keyboard, scroll and a live viewer URL. Pause, resume, kill, port publishing via sandbox_preview_url and outbound connection auditing are all there too.
Clients do not inherit SUPERSERVE_API_KEY from your shell, so it has to go into the env block of the config. The hosted endpoint takes a static bearer, but Claude.ai, the Custom Connector UI in Claude Desktop and ChatGPT developer mode expect OAuth, which it does not support yet. File reads reject anything over 1 MiB, and downloading a directory as a ZIP is capped at 10 MiB.
What it helps with
- run untrusted code away from your own machine
- execute a shell command and capture its output
- read or write a file inside a sandbox
- publish a port and get a preview URL
- audit a sandbox's outbound connections
Example prompts for the agent
- Create a sandbox and run
npm testin it - Write this script to a file in the sandbox and execute it
- Take a screenshot of the sandbox desktop and tell me what's on screen
How to install Superserve
1Platform CLI
claude mcp add --env SUPERSERVE_API_KEY=<SUPERSERVE_API_KEY> --env SUPERSERVE_BASE_URL=<SUPERSERVE_BASE_URL> --transport stdio mcp -- npx -y @superserve/mcpReplace <…> with your own values
2Platform CLI: remote server
claude mcp add --transport http mcp https://mcp.superserve.ai1Platform CLI: remote server
codex mcp add mcp --url https://mcp.superserve.ai2Platform CLI
codex mcp add mcp --env SUPERSERVE_API_KEY=<SUPERSERVE_API_KEY> --env SUPERSERVE_BASE_URL=<SUPERSERVE_BASE_URL> -- npx -y @superserve/mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"mcp": {
"url": "https://mcp.superserve.ai"
}
}
}{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@superserve/mcp"
],
"env": {
"SUPERSERVE_API_KEY": "<SUPERSERVE_API_KEY>",
"SUPERSERVE_BASE_URL": "<SUPERSERVE_BASE_URL>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.superserve.ai"
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@superserve/mcp"
],
"env": {
"SUPERSERVE_API_KEY": "<SUPERSERVE_API_KEY>",
"SUPERSERVE_BASE_URL": "<SUPERSERVE_BASE_URL>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http mcp https://mcp.superserve.ai2Platform CLI
gemini mcp add -e SUPERSERVE_API_KEY=<SUPERSERVE_API_KEY> -e SUPERSERVE_BASE_URL=<SUPERSERVE_BASE_URL> mcp npx -y @superserve/mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Superserve
How do I install Superserve in Claude Code?
Add the server with claude mcp add mcp -e SUPERSERVE_API_KEY=<SUPERSERVE_API_KEY> -- npx -y @superserve/mcp. Create the key in the Superserve console.
What does Superserve do?
It is an MCP server for Superserve's Firecracker sandboxes. Your agent uses it to create microVMs, run commands in them, read and write files, and drive a GUI desktop.
Can I connect without installing anything locally?
Yes, a hosted endpoint runs at https://mcp.superserve.ai over Streamable HTTP. The key goes in as a bearer token, and the server is stateless and account-scoped.
