instabox-mcp
Related Servers
Alternatives to instabox-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables managing Akamai Cloud (Linode) Compute Instances via MCP, with tools to list, create, view, update, delete, boot, reboot, shutdown, resize, and clone VMs. Each connecting client brings its own Linode Personal Access Token, which is passed through without being stored.-
- AlicenseAqualityCmaintenanceEnables MCP clients to start and control Owner-approved local POSIX subprocess sessions over stdio, with cursor-based output reads, input writes, status checks, termination, and resource/time limits.5MIT
- AlicenseBqualityBmaintenanceProvides an MCP control plane for a dedicated Linux VM, enabling shell-equivalent command execution, bounded filesystem and Git workspace operations, persistent process and coding-agent orchestration, artifact presentation, and optional upstream MCP bridge re-exports.271ISC

AgentComputerofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP clients to provision and control agent computers that provide workspace-scoped file tools, terminal command execution, and optional Playwright browser automation.5,106 npmApache 2.0- AlicenseNot gradedqualityBmaintenanceEnables workspace-authorized creation and operation of isolated Firecracker microVMs over MCP or HTTP, letting users execute commands in full Debian guests, manage VM lifecycle, and transfer files without affecting the host process.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables managing multiple Linux SSH servers from MCP clients, with structured filesystem operations, shell commands, durable long-running jobs, process listing, and CPU/RAM/disk/GPU status.MIT
TDQS
Scored across 30 tools
Each tool targets a fairly specific resource+action, and descriptions explicitly distinguish the closest pairs (e.g. account-wide instabox_get_usage vs per-machine instabox_get_machine_usage vs instabox_get_machine_metrics; live instabox_list_files vs instabox_list_snapshot_files). The remaining overlap is mild but real: usage vs metrics vs whoami's plan limits all report capacity-ish data, and a naive agent could still pick the wrong granularity.
The dominant pattern is a consistent instabox_verb_noun scheme (create_machine, list_snapshots, revoke_ssh_tokens, update_machine_secrets), which makes the set easy to scan. A few outliers break it: instabox_machine_power uses noun-first ordering, instabox_whoami is a bare phrase, and instabox_exec is a verb with no object.
30 tools is on the heavy side, but the server genuinely spans seven sub-domains (machines, operations, metrics/usage, files/exec, snapshots, ports, SSH tokens, secrets), each covered by roughly 3-5 tools. It is defensible breadth rather than padding, though a few read-only lookups could be merged into their parent get_* responses.
Lifecycle coverage is strong: full CRUD plus power control for machines, full snapshot CRUD with file inspection, complete SSH token and port publish/unpublish flows, and a secrets selection/delivery flow with an explicit reconciliation call. Minor gaps exist — there is no file delete/rename (must fall back to instabox_exec), no get_port for a single published port, and no org-level secret creation/update, only listing.