Tenki Sandbox MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 86 installs a week from npm. Last commit 21 Oct 2026.
Disposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs.
We read the source, 4 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
"Delete a file or directory in a sandbox. Set recursive to remove a non-empty directory and its contents (rm -r).",
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Tenki Sandbox MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tenki-mcp -e 'TENKI_API_KEY=<TENKI_API_KEY>' -- npx -y @tenkicloud/mcp
{
"mcpServers": {
"tenki-mcp": {
"command": "npx",
"args": [
"-y",
"@tenkicloud/mcp"
],
"env": {
"TENKI_API_KEY": "<TENKI_API_KEY>"
}
}
}
}
[mcp_servers.tenki-mcp]
command = "npx"
args = ["-y", "@tenkicloud/mcp"]
env = { TENKI_API_KEY = "<TENKI_API_KEY>" }
{
"mcpServers": {
"tenki-mcp": {
"command": "npx",
"args": [
"-y",
"@tenkicloud/mcp"
],
"env": {
"TENKI_API_KEY": "<TENKI_API_KEY>"
}
}
}
}
{
"servers": {
"tenki-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tenkicloud/mcp"
],
"env": {
"TENKI_API_KEY": "<TENKI_API_KEY>"
}
}
}
}
Put your own value in place of
<TENKI_API_KEY> (Tenki API key (starts with tk_). Alternatively set TENKI_AUTH_TOKEN (an ory_st_ session token or session cookie); the header is chosen by token prefix).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
TENKI_API_ENDPOINT (Override the control-plane endpoint. Defaults to https://api.tenki.cloud).
Disposable Firecracker microVM sandboxes for agents: run code, snapshot, fork. Needs Linux with KVM.
Cloud Linux VMs for your agent: run code, Docker, files and HTTPS previews in a Sandboxer microVM.
Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.
Disposable email inboxes for AI agents — read messages and verification codes.
Code mode (preview): the AI writes a script against a typed foundry.* API and runs it in a sandbox.
Free disposable email for AI agents: a throwaway inbox to read verification codes over MCP.
Disposable inboxes for AI agents: create an address, wait for the email, get the code or link.
Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes.
Answers built from our own checks of this server.