Developer · Local MCP server

Tenki Sandbox MCP

Disposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs.

Visit Tenki Sandbox MCP's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.LuxorLabs/tenki-mcp
Version
0.3.0
Status
Active
Category
developer
Transport
stdio (local process)
Package
npm
Published
2026-09-17
Updated
2026-09-17
Publisher
LuxorLabs (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/LuxorLabs) · how
Website
tenki.cloud/?utm_source=mcp-registry&utm_medium=mcp-registry&utm_campaign=mcp-registry
Repository
github.com/LuxorLabs/tenki-mcp
Source
Registry API entry

Packages

RegistryPackageVersionTransportEnvironment variables
npm@tenkicloud/mcp0.3.0stdioTENKI_API_KEY (required, secret), TENKI_API_ENDPOINT

How to connect Tenki Sandbox MCP

Tenki Sandbox MCP runs locally from a Node.js package published to the npm registry: @tenkicloud/mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @tenkicloud/mcp@0.3.0. It reads these environment variables: TENKI_API_KEY (required, secret) and TENKI_API_ENDPOINT; set them in the client's configuration for this server.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "tenki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tenkicloud/mcp@0.3.0"
      ],
      "env": {
        "TENKI_API_KEY": "<secret>",
        "TENKI_API_ENDPOINT": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
TempoGraphCode graph context engine with 24 MCP tools. 170+ languages via tree-sitter.Local · stdioPyPI: tempograph
temporal-mcpWall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.Remote & Local · HTTP, stdioLive check: ✓ handshaketemporal-mcp.dev
Tempreon - Personal AI MemoryPerson-owned AI memory that learns, not just stores - portable context for any MCP client.Remote · HTTPLive check: sign-in requiredapi.tempreon.com
TenantsdbMulti-tenant database orchestration: isolated Postgres, MySQL, MongoDB, Redis tenants on demand.Remote · HTTPLive check: sign-in requiredapi.tenantsdb.com
TensorcadDesign transformer LLM architectures and report their parameters, FLOPs, memory and cost.Local · stdionpm: @tensor-cad/mcp
Tentra - Memory for AI Coding AgentsMemory for AI coding agents. Call graphs + refactor safety + persistent code context. 35 MCP tools.Remote & Local · SSE, stdioLive check: sign-in requiredtrytentra.com
TeramindMCP server for Teramind's insider-threat/employee-monitoring API (read-only, metadata-only surface).Local · stdioOCI image (Docker): ghcr.io/wyre-ai/teramind-mcp:v1.0.0
TermadaPersistent, policy-controlled missions for AI agents operating local and SSH environments.Local · stdioOCI image (Docker): ghcr.io/islomzoda/termada:0.12.0