Superserve
MCP server for Superserve sandboxes: create, exec, and manage Firecracker microVMs
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http superserve 'https://mcp.superserve.ai' --header 'Authorization: <Bearer token — your Superserve API key, e.g. '\''Bearer ss_live_...'\''.>'
{
"mcpServers": {
"superserve": {
"type": "http",
"url": "https://mcp.superserve.ai",
"headers": {
"Authorization": "<Bearer token — your Superserve API key, e.g. 'Bearer ss_live_...'.>"
}
}
}
}
@superserve/mcpclaude mcp add superserve -e 'SUPERSERVE_API_KEY=<your superserve_api_key>' -e 'SUPERSERVE_BASE_URL=https://api.superserve.ai' -- npx -y @superserve/mcp@0.3.3
{
"mcpServers": {
"superserve": {
"command": "npx",
"args": [
"-y",
"@superserve/mcp@0.3.3"
],
"env": {
"SUPERSERVE_API_KEY": "<your superserve_api_key>",
"SUPERSERVE_BASE_URL": "https://api.superserve.ai"
}
}
}
}
Environment variables
SUPERSERVE_API_KEYrequired secret Superserve API key (starts with ss_live_). Create one at https://console.superserve.ai.SUPERSERVE_BASE_URLOverride the Superserve control-plane API base URL. Defaults to https://api.superserve.ai.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Persistent and secure sandboxes for AI Agents, powered by Firecracker microVMs.
Getting Started
Visit superserve.ai or jump straight into the docs.
Structure
apps/
console/ # Sandbox dashboard (Next.js 16, App Router)
ui-docs/ # UI component docs (Vite)
packages/
cli/ # TypeScript CLI (@superserve/cli)
python-sdk/ # Python SDK (superserve on PyPI)
sdk/ # TypeScript SDK (@superserve/sdk)
ui/ # Shared UI components (@superserve/ui)
typescript-config/ # Shared tsconfig presets
tailwind-config/ # Shared Tailwind config
docs/ # Mintlify documentation site
tests/ # SDK end-to-end tests
Monorepo managed with Bun workspaces, Turborepo, and uv workspaces.
Setup
bun install # install all JS/TS dependencies
uv sync # install all Python dependencies
Development
bun run dev # start all dev servers
bun run build # build all packages
bun run lint # lint all packages
bun run format # format all files
bun run typecheck # type check all packages
bun run test # unit/integration tests
For more (per-package targets, dependency management, etc.), see CONTRIBUTING.md.
SDKs
- TypeScript:
@superserve/sdk—bun add @superserve/sdk - Python:
superserve—uv add superserve
Full reference at docs.superserve.ai.
Testing
bun run test # unit tests (no credentials)
SUPERSERVE_API_KEY=ss_live_... bun run test:e2e # e2e against staging
For environment overrides and single-language runs, see CONTRIBUTING.md.
Releasing
See RELEASING.md for publishing the SDKs to npm and PyPI.
Contributing
Contributions welcome — see CONTRIBUTING.md for guidelines.
License
Apache License 2.0 — see LICENSE.
Where to find us
Frequently asked questions
What is Superserve?
MCP server for Superserve sandboxes: create, exec, and manage Firecracker microVMs
How do I install Superserve?
It runs as a remote server. In Claude Code: claude mcp add --transport http superserve 'https://mcp.superserve.ai' --header 'Authorization: <Bearer token — your Superserve API key, e.g. '\''Bearer ss_live_...'\''.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Superserve need an API key?
Yes. It expects SUPERSERVE_API_KEY, Authorization, which you set in its configuration.
Is Superserve open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains Superserve?
It is published by superserve-ai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.