Skip to main content
Glama

Luxor MCP: @luxorai/mcp

A Model Context Protocol server for Luxor Sandbox, part of Luxor Agent Cloud by Luxor AI. Give any agent (Claude, Codex, Cursor) a disposable microVM it can create, run code in, read and write files, run git, and expose to the web. Sandboxes boot in ~2 seconds and are billed per second.

The agent writes code and Luxor runs it in isolation. (Luxor Code Review and Luxor's managed CI runners are separate products; this server currently exposes the Sandbox.)

The old @tenkicloud/mcp name keeps working and publishes the same code.

"Run this Python in a fresh sandbox and tell me what it prints."
        │
        ▼   tenki_run_code
   boots a microVM → runs it → returns stdout → tears it down

Quickstart

export LUXOR_API_KEY=lx_your_key_here
npx -y @luxorai/mcp     # speaks MCP over stdio

Nothing to clone or build. The package installs the command luxor-mcp (and tenki-mcp, the same program).

Use it in Claude Code

Connect to Luxor's hosted MCP service and sign in with your Luxor account:

claude mcp add --transport http luxor https://mcp.luxor.ai/mcp
claude mcp login luxor

Claude Code's mcp add command stores the server configuration; mcp login performs the one-time browser authorization and workspace selection.

Alternatively, run the MCP server locally with an API key:

claude mcp add luxor --env LUXOR_API_KEY=lx_your_key_here -- npx -y @luxorai/mcp

Or install it as a Claude Code plugin

The repo doubles as a plugin marketplace. This prompts for your API key on install and stores it in your OS keychain, so there is no env var to manage:

/plugin marketplace add LuxorLabs/tenki-mcp
/plugin install luxor@luxor

If you added this marketplace before it was named luxor, your installs keep working as luxor@tenki and tenki@tenki. To switch to the new name, run /plugin marketplace remove tenki (this uninstalls its plugins and their saved API key), then add the marketplace again.

The luxor plugin names its tools luxor_*; the legacy tenki plugin keeps tenki_*.

Use it in Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "luxor": {
      "command": "npx",
      "args": ["-y", "@luxorai/mcp"],
      "env": { "LUXOR_API_KEY": "lx_your_key_here" }
    }
  }
}

Use it in Cursor

Add the same block to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "luxor": {
      "command": "npx",
      "args": ["-y", "@luxorai/mcp"],
      "env": { "LUXOR_API_KEY": "lx_your_key_here" }
    }
  }
}

Use it in Codex

The OpenAI Codex CLI reads MCP servers from ~/.codex/config.toml. Add:

[mcp_servers.luxor]
command = "npx"
args = ["-y", "@luxorai/mcp"]
env = { LUXOR_API_KEY = "lx_your_key_here" }

Confirm it's working

After adding the server, start a fresh session so the client loads it, then ask your agent one of:

  • "Check Luxor auth status.": confirms your credential was picked up.

  • "Run print(2+2) in a fresh Luxor sandbox.": a full boot → run → teardown round-trip.

If the tools don't show up, restart the client so it re-reads its config.

No key yet? Start the server without one and ask the agent to check tenki_auth_status; it reports what to set and where. See Auth.

Run it from a clone instead

For development, or to run an unreleased change:

git clone https://github.com/LuxorLabs/tenki-mcp.git && cd tenki-mcp
npm install && npm run build
LUXOR_API_KEY=lx_your_key_here node dist/index.js

Substitute node /absolute/path/to/tenki-mcp/dist/index.js for the npx command in any of the configs above. See CONTRIBUTING.md for the full development loop.

Environment variables

Variable

Default

Purpose

LUXOR_API_KEY

-

API key (lx_…, or tk_…). One of this or LUXOR_AUTH_TOKEN is required.

LUXOR_AUTH_TOKEN

-

Session token (ory_st_… or cookie value). Takes precedence over LUXOR_API_KEY when both are set.

LUXOR_API_ENDPOINT

https://api.luxor.ai (the same API as https://api.tenki.cloud)

Control-plane base URL (LUXOR_API_URL is an alias).

LUXOR_MCP_READONLY

off

1 registers only read tools (no create/run/delete/spend).

LUXOR_MCP_DISABLED_TOOLS

-

Comma-separated tool names to skip registering.

LUXOR_MCP_AUDIT

off

1 logs each tool call name + arg keys to stderr.

LUXOR_MCP_TOOL_PREFIX

tenki

luxor names every tool luxor_* instead of tenki_* (the luxor Claude Code plugin sets it). Descriptions and errors use the same names.

LUXOR_MCP_TRANSPORT

stdio

http serves Streamable HTTP instead (see below).

PORT

3000

HTTP transport port.

LUXOR_MCP_HTTP_HOST

127.0.0.1

HTTP bind host; non-loopback requires LUXOR_MCP_HTTP_TOKEN.

LUXOR_MCP_HTTP_TOKEN

-

Bearer token for the HTTP endpoint; optional on loopback, required on a non-loopback host.

LUXOR_MCP_PUBLIC_URL

-

Public base URL for an OAuth-protected hosted server.

LUXOR_MCP_OAUTH_ISSUER

-

OAuth authorization-server issuer. Enables delegated OAuth HTTP mode.

LUXOR_MCP_OAUTH_RESOURCE

<public URL>/mcp

RFC 8707 resource identifier accepted in access-token audiences. A comma-separated list serves one resource per domain; metadata and the 401 resource_metadata follow the request host, else the first.

LUXOR_MCP_OAUTH_SCOPE

mcp

Required delegated scope.

LUXOR_MCP_RESOURCE_NAME

Luxor MCP

resource_name in the protected-resource metadata.

LUXOR_MCP_IDENTITY_URL

-

Internal Luxor Identity service endpoint used to exchange OAuth access tokens.

LUXOR_MCP_IDENTITY_SERVICE_TOKEN

-

Service credential for the private Identity token-exchange RPC.

Every LUXOR_* variable above is still accepted under its TENKI_* name (for example TENKI_API_KEY, TENKI_MCP_TRANSPORT). All LUXOR_* credentials are read before any TENKI_* one. Keys start with lx_; tk_… keys are still accepted. LUXOR_API_KEY is only used when it starts with lx_ or tk_; any other value is ignored.

Related MCP server: MileHost MCP Server

Tools

82 tools: all 76 tool-worthy public unary API methods (enforced by a CI parity audit, which also fails if a tool calls a method the API no longer has; GitOperation is exposed as one tool per operation), two workflow helpers, and tenki_auth_status. Tool names use the tenki_ prefix by default; set LUXOR_MCP_TOOL_PREFIX=luxor (as the luxor plugin does) to name them luxor_*. A few admin surfaces (published images, saved Tailscale connections) and implementation-only control-plane methods are intentionally excluded. Grouped by domain:

Domain

Tools

Auth

tenki_auth_status (which credential is configured, and does it work; the only tool available when none is)

Identity

tenki_whoami

Run

tenki_run_code (one-shot: boot → run shell/python/js → tear down)

Sandboxes

tenki_create_sandbox · tenki_get_sandbox · tenki_get_sandbox_metrics · tenki_list_sandboxes · tenki_terminate_sandbox · tenki_pause_sandbox · tenki_resume_sandbox · tenki_fork_sandbox (copies of a running sandbox)

Session admin

tenki_extend_sandbox · tenki_update_sandbox · tenki_terminate_sandboxes (bulk) · tenki_report_sandbox_activity · tenki_list_workspace_sandboxes

Exec

tenki_exec (stdout/stderr/exit inline)

Files

tenki_read_file · tenki_write_file · tenki_list_files · tenki_stat_path · tenki_make_dir · tenki_remove_path · tenki_move_path

Git

tenki_git_clone · tenki_git_checkout · tenki_git_diff · tenki_git_log (the four operations the API supports; pass directory to target a cloned repo; run other git commands via tenki_exec)

Ports & previews

expose · list-exposed · unexpose · create-preview-url · open-preview (viewer-token-gated, not public; port 7681 is the web terminal) · list/get/delete-preview-url · touch-preview · bind/unbind-preview-url · resolve-preview-token

Artifacts (binary transfer)

tenki_get_upload_url · tenki_get_download_url (signed URLs for binary PUT/GET)

SSH

tenki_update_ssh_keys · tenki_issue_ssh_cert · tenki_list_ssh_gateways

Snapshots

create · get · list · list-session · list-workspace · list-dangling · update · delete · get-download-url

Volumes

create · get · list · update · delete · resize · attach · detach

Egress policies

create · get · list · update · delete (named workspace allowlists that tenki_create_sandbox pins via egress_policies)

Templates

create · get · list · update · delete · build · cancel-build · get-build · list-active-builds · list-builds · delete-build

Workspace

tenki_get_workspace_usage · tenki_list_ci_runner_sizes · tenki_get_workspace_preview_domains · tenki_update_workspace_preview_domains

Full per-release breakdown in CHANGELOG.md.

Deprecated upstream, still served: tenki_expose_port / tenki_unexpose_port / tenki_list_exposed_ports (the API prefers the preview-URL tools), tenki_list_workspace_sandboxes / tenki_list_workspace_snapshots (prefer the credential-scoped lists), and the ExecuteCommand RPC behind tenki_exec / tenki_run_code / tenki_move_path (successor is the data-plane Run stream, which needs an HTTP/2 transport this server does not have yet). The parity audit prints these on every run.

Auth

Set one of LUXOR_API_KEY or LUXOR_AUTH_TOKEN (TENKI_API_KEY / TENKI_AUTH_TOKEN are still accepted). When both are set, the auth token wins. The header is chosen by token prefix: lx_… or tk_… → Authorization: Bearer, ory_st_… → X-Session-Token, otherwise a session cookie. Override the endpoint with LUXOR_API_ENDPOINT (default https://api.luxor.ai, the same API as https://api.tenki.cloud).

Without a credential the server still starts, registering only tenki_auth_status, so instead of an MCP client reporting an opaque "server failed to start", the agent can call that tool and get told what to set. Ask it "check Luxor auth status" any time other tools return auth errors: it reports the credential kind (API key vs session token), the endpoint, and whether a live identity probe succeeded, never the token itself. It reports status only; get a credential from the Luxor dashboard.

Host it over HTTP (v2.0-beta)

Besides stdio, the server speaks Streamable HTTP so it can be hosted for remote MCP clients:

LUXOR_MCP_TRANSPORT=http PORT=3000 LUXOR_API_KEY=… npx -y @luxorai/mcp
# → tenki-mcp running on http://127.0.0.1:3000/mcp (Streamable HTTP) [loopback only, no auth]

For a single-user deployment, HTTP mode can hold one shared LUXOR_API_KEY and therefore exposes a powerful capability. By default it:

  • binds to loopback (127.0.0.1) only: set LUXOR_MCP_HTTP_HOST=0.0.0.0 to expose it, but then

  • it requires a bearer token: set LUXOR_MCP_HTTP_TOKEN and send Authorization: Bearer <token>. It refuses to start on a non-loopback host without one.

  • DNS-rebinding protection is on (Host-header allowlist), so a malicious web page can't drive your local server.

# expose to a network safely:
LUXOR_MCP_TRANSPORT=http LUXOR_MCP_HTTP_HOST=0.0.0.0 PORT=3000 \
  LUXOR_MCP_HTTP_TOKEN=$(openssl rand -hex 32) LUXOR_API_KEY=… npx -y @luxorai/mcp

Point an HTTP-capable MCP client at /mcp. Static-key mode uses one shared LUXOR_API_KEY for all sessions. Verified end-to-end (test/http-transport.test.mjs: auth gate, DNS-rebinding rejection, connect → tools/list → tool call over HTTP).

Hosted multi-tenant deployments instead use Luxor Identity's OAuth facade. The MCP server publishes RFC 9728 protected-resource metadata and exchanges each caller's access token through the private Identity service. Identity owns Hydra, validates the requested audience and scope, and issues a short-lived API delegation bound to the user, client, and workspace selected on the Luxor consent page. tenki-mcp has no Hydra Admin access and does not hold the delegation-signing secret.

How it works

Luxor's API is ConnectRPC: JSON over HTTP/1.1, not REST. Every control-plane call is POST https://api.luxor.ai/tenki.sandbox.v1.SandboxService/{Method} with a lowerCamelCase JSON body. Per-session file I/O runs on a separate data-plane endpoint returned at create time, authenticated with a short-lived session certificate. This server owns both transports so the tools stay one-liners.

Command output: tenki_exec and tenki_run_code capture stdout/stderr by redirecting to files (sh -c '… > out 2> err') and reading them back over the data plane, so you get the output inline through a plain HTTP client.

The wire details are ported from the live-verified n8n community node.

Security

This server holds a Luxor API key and can run code + spend credits, so treat it as a capability. Full model + CSA MCP Server Top-10 mapping in SECURITY.md. Quick controls:

  • Least privilege: every tool carries a title and MCP annotations: readOnlyHint on reads, and destructiveHint on every tool that can overwrite, modify, interrupt or delete existing state (only tools that create, resume, extend, attach or keep alive without changing existing state are non-destructive). Run LUXOR_MCP_READONLY=1 for an inspection-only server (read tools only), or LUXOR_MCP_DISABLED_TOOLS=tenki_run_code,… to drop specific tools.

  • HTTP transport is loopback-only by default and requires a bearer token to expose to a network (see Host it over HTTP).

  • Audit: LUXOR_MCP_AUDIT=1 logs each tool call's name to stderr.

  • Untrusted output: tenki_run_code/tenki_exec/tenki_read_file return output from untrusted code; clients should treat tool results as data, not instructions.

Report vulnerabilities via a private security advisory, not a public issue.

License

MIT

Available Tools

71 tools
tenki_attach_volumeA

Mount a volume into a running sandbox at an absolute path. Set read_only to mount without write access.

Inputs: volume_id (required), mount_path (required), session_id (required), read_only.

tenki_auth_statusA
Read-onlyIdempotent

Report whether the server has a usable Tenki credential, which kind (API key vs OAuth session token), and the endpoint it targets — verified with a live identity probe. Call this first when other tools fail with auth errors, or when this is the only tool available (which means no credential is configured). Reports status only; it does not log in and never returns the token.

Inputs: no named parameters. Returns: error, detail, source, endpoint, +4 more

tenki_bind_preview_urlA

Bind a named preview URL to a sandbox session and port (advanced routing).

Inputs: port (required), session_id (required), preview_url_id (required).

tenki_build_templateA

Trigger a build for a template, producing a bootable image. Returns the created build — poll it with tenki_get_template_build until READY; the ready build's imageDigestRef is what tenki_create_sandbox's image arg takes.

Inputs: template_id (required), build_env, image_name, build_secrets, +1 more.

tenki_cancel_template_buildA

Cancel an in-progress template build by its build ID.

Inputs: build_id (required).

tenki_create_preview_urlA

Create a shareable public preview URL for a port in a sandbox. The sandbox must have inbound networking enabled (create it with allow_inbound).

Inputs: port (required), slug (required), session_id (required), expires_at.

tenki_create_sandboxA

Create a persistent sandbox microVM, optionally from a snapshot or template image. Returns the session (id, state) and its data-plane endpoint. Boots in ~2s. Use tenki_exec / tenki_read_file / tenki_write_file against the returned session_id.

Inputs: env, name, tags, image, +11 more.

tenki_create_snapshotA

Capture a running sandbox's disk and memory as a reusable snapshot (attached volumes are NOT captured); boot a new sandbox from it later with tenki_create_sandbox + snapshot_id.

Inputs: session_id (required), name, expires_at, store_raw_image.

tenki_create_templateA

Create a custom-image template (a reusable sandbox-image spec: base image + setup script + default resources). Build it into a bootable image later with tenki_build_template. NOTE: only a TYPED template (created with builder_spec, no legacy fields) can build a named, publishable image (image_name) that tenki_create_sandbox boots via its image arg.

Inputs: name (required), tags, env_vars, cpu_cores, +9 more.

tenki_create_volumeA

Create a workspace-scoped persistent volume — durable block storage that survives sandbox teardown. Defaults the workspace to the API key's first; override with workspace_id.

Inputs: name (required), size_bytes (required), workspace_id.

tenki_delete_preview_urlA
Destructive

Delete a preview URL by id, taking it permanently offline.

Inputs: preview_url_id (required).

tenki_delete_snapshotA
Destructive

Permanently delete a snapshot by ID.

Inputs: snapshot_id (required).

tenki_delete_templateA
Destructive

Delete a template by ID. Pass force to delete even when builds or dependents exist.

Inputs: template_id (required), force.

tenki_delete_volumeA
Destructive

Permanently delete a volume and destroy its data. Fails with VolumeInUse if the volume is still attached to a session — detach it first.

Inputs: volume_id (required).

tenki_detach_volumeB
Destructive

Unmount a volume from a sandbox session.

Inputs: volume_id (required), session_id (required).

tenki_execA

Run a command in an existing sandbox and return stdout, stderr, and exit code inline. Streams over max_output_bytes (default 64KB) come back as a head+tail preview with the full output retained at stdoutPath/stderrPath in the sandbox.

Inputs: command (required), session_id (required), cwd, env, +3 more. Returns: ok, args, stderr, stdout, +7 more

tenki_expose_portA

Expose a port from a sandbox and get a public preview URL. Useful when an agent starts a web server it wants to show.

Inputs: port (required), session_id (required), slug.

tenki_extend_sandboxA

Extend a running sandbox's wall-clock lifetime by N seconds so it isn't auto-terminated at its max-duration cap.

Inputs: session_id (required), additional_duration_seconds (required).

tenki_get_download_urlA
Read-onlyIdempotent

Get a short-lived signed URL to download (HTTP GET) a command artifact from a sandbox by its artifact id (e.g. a command's stdout/stderr artifact). Note: the API supports download-by-artifact-id only, not download-by-path.

Inputs: session_id (required), artifact_id (required).

tenki_get_preview_urlA
Read-onlyIdempotent

Fetch a specific preview URL's details by id.

Inputs: preview_url_id (required).

tenki_get_sandboxB
Read-onlyIdempotent

Fetch a sandbox's current state and metadata.

Inputs: session_id (required).

tenki_get_snapshotA
Read-onlyIdempotent

Fetch one snapshot's status and metadata by ID.

Inputs: snapshot_id (required).

tenki_get_snapshot_download_urlA
Read-onlyIdempotent

Get a short-lived, pre-signed URL to download a snapshot's raw disk image (requires the snapshot to have been created with store_raw_image).

Inputs: snapshot_id (required).

tenki_get_snapshot_retention_settingsA
Read-onlyIdempotent

Get the workspace's pause- and snapshot-retention periods. DEPRECATED upstream: this RPC is marked deprecated in the API — tenki_get_workspace_settings returns the same retention fields alongside the quotas. An empty response means no retention override, i.e. kept indefinitely.

Inputs: workspace_id.

tenki_get_templateA
Read-onlyIdempotent

Retrieve one template by ID.

Inputs: template_id (required).

tenki_get_template_buildA
Read-onlyIdempotent

Retrieve one template build by its build ID (state, progress, and result image). A READY build's imageDigestRef is the reference tenki_create_sandbox's image arg takes.

Inputs: build_id (required).

tenki_get_upload_urlA

Get a short-lived signed URL to upload (HTTP PUT) a binary file to a path inside a sandbox. Use for non-text payloads too large or binary for tenki_write_file.

Inputs: path (required), session_id (required), content_type.

tenki_get_volumeA
Read-onlyIdempotent

Fetch a single volume's metadata and current state by its id.

Inputs: volume_id (required).

tenki_get_workspace_settingsA
Read-onlyIdempotent

Read a workspace's sandbox quotas and retention policy: max snapshots/templates/volumes/total bytes, max concurrent and sticky sessions, max preview URLs, and the pause/snapshot retention periods. These are workspace limits — there are no per-session defaults (idle timeout and max duration are set per sandbox at creation).

Inputs: workspace_id.

tenki_get_workspace_usageA
Read-onlyIdempotent

Get per-second sandbox billing and usage figures for a workspace — use this for cost visibility across all of the workspace's sandboxes.

Inputs: workspace_id.

tenki_gitA

Run a git operation in a sandbox. Only clone, checkout, diff, and log are supported by the API — for any other git command (status, add, commit, push, ...) use tenki_exec with git .... clone arg keys: repo (required, the URL), branch?, depth?, directory?. CAVEAT (live-verified): checkout/diff/log run in the session's working directory (/home/tenki), which is not a repository and has no directory arg — so on a repo cloned into a subdirectory they fail with 'not a git repository'. Use tenki_exec with git -C <directory> ... instead (e.g. git -C /home/tenki/hw log -n 2). For reference, their arg keys are — checkout: ref (required), create? ('true' = -b); diff: range? or base?+head?, path?; log: max_count?, range?, path?.

Inputs: operation (required), session_id (required), args.

tenki_issue_ssh_certA

Issue a short-lived SSH certificate for a public key, authorizing SSH access to a sandbox via the SSH gateway.

Inputs: public_key (required), session_id (required).

tenki_list_active_template_buildsA
Read-onlyIdempotent

List the currently active (in-progress) builds for a given template.

Inputs: template_id (required).

tenki_list_dangling_snapshotsA
Read-onlyIdempotent

List dangling snapshots — those whose source session no longer exists — for the workspace, useful for cleanup.

Inputs: page_size, page_token.

tenki_list_exposed_portsA
Read-onlyIdempotent

List the ports currently exposed from a sandbox.

Inputs: session_id (required).

tenki_list_filesA
Read-onlyIdempotent

List a directory in a sandbox, including dotfiles (.git, .env, .gitignore) by default — set include_hidden false to omit them.

Inputs: path (required), session_id (required), include_hidden.

tenki_list_preview_urlsA
Read-onlyIdempotent

List the workspace's preview URLs, newest page first. Pass session_id to keep only the ones bound to that sandbox (filtered here, not server-side — so it applies to the page you fetched; raise page_size or follow next_page_token to widen it). Results are paginated: a nextPageToken in the response means more pages exist.

Inputs: page_size, page_token, session_id, workspace_id.

tenki_list_sandboxesC
Read-onlyIdempotent

List sandboxes for the workspace.

Inputs: page_size, page_token, include_terminated.

tenki_list_session_snapshotsA
Read-onlyIdempotent

List the snapshots captured from a specific sandbox session.

Inputs: session_id (required), page_size, page_token.

tenki_list_snapshotsB
Read-onlyIdempotent

List the saved snapshots for the workspace (owner inferred from the API key).

Inputs: page_size, page_token.

tenki_list_ssh_gatewaysA
Read-onlyIdempotent

List the currently active SSH gateways for the workspace.

Inputs: workspace_id.

tenki_list_templatesA
Read-onlyIdempotent

List templates for the workspace, optionally filtered by tags.

Inputs: tags, page_size, page_token, workspace_id.

tenki_list_volumesA
Read-onlyIdempotent

List persistent volumes in a workspace (defaults to the key's first workspace). Supports pagination.

Inputs: page_size, page_token, workspace_id.

tenki_list_workspace_sandboxesA
Read-onlyIdempotent

List every sandbox belonging to a specific workspace (defaults to the API key's workspace) — useful for spotting leaked, still-billing sandboxes across the workspace.

Inputs: page_size, page_token, workspace_id, include_terminated.

tenki_list_workspace_snapshotsA
Read-onlyIdempotent

List all snapshots in a workspace (defaults to the key's first workspace). Supports pagination.

Inputs: page_size, page_token, workspace_id.

tenki_make_dirA

Create a directory in a sandbox. Set recursive to also create any missing parent directories (mkdir -p).

Inputs: path (required), session_id (required), recursive.

tenki_move_pathB

Move or rename a file or directory within a sandbox. Both paths are under /home/tenki.

Inputs: to (required), from (required), session_id (required).

tenki_open_previewA

Open a viewer-token-gated (AUTHENTICATED-mode) preview. USE tenki_expose_port OR tenki_create_preview_url INSTEAD for an ordinary web server: for any port other than the web terminal (7681) the API deliberately returns a non-regional fallback host that currently has no edge route, so the URL 404s (live-verified). The returned viewerToken does resolve via tenki_resolve_preview_token; only the URL is unreachable. Requires allow_inbound.

Inputs: port (required), session_id (required), expires_at.

tenki_pause_sandboxA

Pause a sandbox (snapshot + suspend) so it can be resumed later.

Inputs: session_id (required).

tenki_read_fileA
Read-onlyIdempotent

Read a UTF-8 text file from a sandbox (paths under /home/tenki).

Inputs: path (required), session_id (required).

tenki_remove_pathA
Destructive

Delete a file or directory in a sandbox. Set recursive to remove a non-empty directory and its contents (rm -r).

Inputs: path (required), session_id (required), recursive.

tenki_report_sandbox_activityA

Report client-side activity on a sandbox to reset its idle timer and keep it from being reaped as idle (a keep-alive heartbeat).

Inputs: session_id (required).

tenki_resize_volumeA

Grow a volume to a new size in bytes (1 MiB … 100 GiB). Volumes can grow but not shrink.

Inputs: volume_id (required), size_bytes (required).

tenki_resolve_preview_tokenA
Read-onlyIdempotent

Resolve a preview token to the sandbox/port it points at (advanced).

Inputs: token (required).

tenki_resume_sandboxA

Resume a previously paused sandbox.

Inputs: session_id (required).

tenki_run_codeA

Boot a throwaway microVM, run a snippet (shell/python/javascript), return its stdout/stderr/exit code, and tear the sandbox down. Cost-guarded and self-terminating. Use this for one-shot execution when you don't need a persistent sandbox. Output over ~64KB per stream is truncated head+tail — and the sandbox is gone, so for large output use tenki_create_sandbox + tenki_exec and page through the retained file.

Inputs: code (required), language (required), env, timeout_seconds.

tenki_stat_pathA
Read-onlyIdempotent

Get metadata (size, mode, type, timestamps) for a file or directory in a sandbox. Use to check whether a path exists or inspect it before reading/removing.

Inputs: path (required), session_id (required).

tenki_terminate_sandboxA
Destructive

Terminate (destroy) a sandbox. The microVM and its filesystem are gone after this.

Inputs: session_id (required).

tenki_terminate_sandboxesA
Destructive

Terminate MULTIPLE sandboxes in one call (bulk). IRREVERSIBLE — every listed sandbox and its filesystem is destroyed. Use tenki_terminate_sandbox for a single one.

Inputs: session_ids (required).

tenki_touch_previewA

Refresh (keep-alive) a live preview by its preview token so it isn't torn down as idle.

Inputs: preview_token (required).

tenki_unbind_preview_urlA
Destructive

Unbind a named preview URL from its current session/port (advanced routing).

Inputs: preview_url_id (required).

tenki_unexpose_portA
Destructive

Remove an inbound port exposure from a sandbox, taking its public URL/preview offline. Use this to un-publish a port previously exposed with tenki_expose_port.

Inputs: port (required), session_id (required).

tenki_update_sandboxA

Update mutable fields on an existing sandbox — its name, tags, idle timeout, or max duration.

Inputs: session_id (required), name, tags, idle_timeout_minutes, +1 more.

tenki_update_snapshotA

Update a snapshot's mutable metadata (name and/or expiry).

Inputs: snapshot_id (required), name, expires_at.

tenki_update_snapshot_retention_settingsA

Update the workspace's snapshot-retention policy: how long snapshots are kept before automatic cleanup. Pass retention_days to set it, or clear_retention to keep snapshots indefinitely (the unset state) — exactly one of the two. DEPRECATED upstream: prefer tenki_update_workspace_settings, which sets the same retention (and pause retention) alongside the quotas.

Inputs: workspace_id, retention_days, clear_retention.

tenki_update_ssh_keysA

Set the SSH authorized public keys on a running sandbox, enabling direct SSH access for the given keys.

Inputs: session_id (required), public_keys (required).

tenki_update_templateA

Update mutable fields on a template. Only the fields you provide are changed; pass clear_tags to remove all tags.

Inputs: template_id (required), name, tags, env_vars, +8 more.

tenki_update_volumeA

Rename a volume (update its human-readable name). To change a volume's size use tenki_resize_volume instead.

Inputs: name (required), volume_id (required).

tenki_update_workspace_settingsA

Update a workspace's sandbox quotas and retention periods. Only the fields you pass change. Each quota has a matching clear_* flag to remove the override and fall back to the platform default; pass the value OR its clear flag, not both. There are no per-session defaults here — idle timeout and max duration are set per sandbox at creation.

Inputs: max_volumes, workspace_id, max_snapshots, max_templates, +8 more.

tenki_whoamiA
Read-onlyIdempotent

Return the identity and workspaces for the current API key. Cheap credential test.

Inputs: no named parameters.

tenki_write_fileA

Write a UTF-8 text file to a sandbox (paths under /home/tenki).

Inputs: path (required), content (required), session_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 71 tools

    Disambiguation2/5

    Multiple tools overlap significantly: tenki_list_sandboxes and tenki_list_workspace_sandboxes have nearly identical purposes, several snapshot listing variants coexist, and deprecated retention-settings tools duplicate workspace-settings tools. Descriptions often clarify when to use what, but the boundary between run_code and create_sandbox+exec, git and exec, and open_preview versus expose_port/create_preview_url still creates real selection risk.

    Naming Consistency5/5

    Every tool uses the tenki_ prefix with a clear verb_noun pattern: create/get/list/update/delete for resources, plus exec/read/write/move for file operations and expose/unexpose for ports. Singular get_ versus plural list_ conventions are consistent, making the API predictable despite its size.

    Tool Count1/5

    71 tools is far beyond a well-scoped MCP surface and hits the extreme end of the calibration scale. Even accounting for a broad sandbox-management domain, the count is bloated by near-duplicate list/retrieval variants and deprecated endpoints that could be consolidated.

    Completeness5/5

    The domain is very thoroughly covered: full sandbox lifecycle, file operations, execution, preview URLs, snapshots, volumes, templates, SSH access, workspace settings, usage billing, and auth diagnostics. There are no obvious dead ends or missing core operations for managing sandboxes and their related resources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers