tenki-mcp
Related Servers
Alternatives to tenki-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to rent disposable cloud dev environments with a terminal, real browser, repo checkout, git gateway, and live view, so they can build, test, run dev servers, inspect pages, and push branches while keeping keys off the VM.1Apache 2.0
- AlicenseAqualityBmaintenanceProvides secure, disposable, resource-bounded container sandboxes that let AI agents create and inspect files, run shell commands with timeouts, and perform Git operations without exposing the host environment.11MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to execute shell commands and compile or run code snippets inside sub-6ms hardware-isolated KVM MicroVM sandboxes instead of the local machine. It also lets agents spawn, list, hibernate, wake, and destroy sandboxes — optionally bundled with an embedded PostgreSQL database — behind an SSRF/metadata firewall with Base64-escaped code delivery.751,696 npm1Apache 2.0
- AlicenseAqualityBmaintenanceProvides agents with real Linux VMs to run commands, manage files, expose ports, and track costs, all through an ephemeral sandbox service.11MIT

MileHost MCP Serverofficial
AlicenseCqualityCmaintenanceEnables AI coding agents to manage cloud containers, create and edit files, run commands, and deploy projects directly.247MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to operate a persistent Linux sandbox in the cloud, running commands, managing files, using Git, and publishing artifacts through a Streamable HTTP MCP endpoint.-
TDQS
Scored across 71 tools
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.
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.
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.
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.