instabox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSTABOX_API_KEY | Yes | InstaBox API key (ibk_...), sent as X-API-Key. A key with machines:read|write|delete and images:read|write|delete covers every tool. | |
| INSTABOX_API_URL | No | API base URL | https://api.instabox.sh |
| INSTABOX_READ_ONLY | No | Set to true to register only the read-only tools. | off |
| INSTABOX_MAX_OUTPUT_CHARS | No | Cap on text returned per tool call. | 60000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instabox_whoamiA | Show which user/org the configured API key belongs to, including |
| instabox_list_templatesA | List the templates a machine can start from (e.g. agent-browser, universal, herdr, orca) with their software and default size. Only templates with |
| instabox_get_usageA | Account-wide counts of machines and snapshots, stored data (measured about hourly) and plan limits (max machines, snapshots, storage). Check this before creating machines when you may be near a limit. |
| instabox_list_machinesA | List your machines (any state except deleted), one page at a time. Optionally filter by metadata labels. Returns |
| instabox_get_machineA | Get one machine by ID or name: state (creating, starting, running, stopping, stopped, suspending, suspended = paused, resuming, deleting, error), spec, template, auto-pause setting, labels, guest user and whether its runtime is ready. |
| instabox_create_machineA | Create a Linux machine (Firecracker microVM, Debian, root, Docker, 20 GiB persistent /data; home is /data/home) from a template or one of your snapshots. Starts as an asynchronous operation; by default this waits until the machine is running. Give |
| instabox_update_machineA | Change a machine's idle auto-pause time and/or labels. Applies immediately in any state. |
| instabox_machine_powerA | Change a machine's power state. |
| instabox_delete_machineA | PERMANENTLY delete a machine and its disks (snapshots saved from it are kept). Cannot be undone. To guard against deleting the wrong machine, |
| instabox_get_operationA | Get the status of an operation (create, start, stop, suspend, resume, delete) returned by a lifecycle call: state queued, running, succeeded or failed, plus phase and error. With |
| instabox_get_machine_metricsA | CPU and memory samples (one per 30 s, oldest first) measured on the host for a machine. Empty while the machine is not running; a new machine's first sample appears after ~90 s. Default window is the last 5 minutes, at most 24 h back. |
| instabox_get_machine_usageA | Resource usage of one machine over a window (running seconds, vCPU-seconds, GiB-seconds of memory and disk), for billing or cost checks. Defaults to the current UTC month; the window may span at most 366 days. Works for deleted machines too (by ID). |
| instabox_execA | Run a command inside a RUNNING machine and return stdout, stderr and the exit code once it exits (a non-zero exit is still a normal result). Output is collected, not streamed, and each stream is cut at 1 MiB. Give |
| instabox_list_filesA | List a directory (up to 5000 entries, directories first) or read a text file (up to 256 KiB) from a machine, live and as root. Binary files come back with |
| instabox_write_fileA | Create or replace a file inside a RUNNING machine, creating parent directories. Implemented over exec (base64 on stdin), so it is limited to about 700 KB of content; for bigger files use instabox_exec with curl/git inside the machine. Overwrites without asking. Relative paths start at /data/home. |
| instabox_list_snapshotsA | List your snapshots, oldest first. A snapshot is a saved copy of a machine's software and /data files (not memory or processes); new machines can start from it. |
| instabox_get_snapshotA | Get one snapshot by ID. |
| instabox_list_snapshot_filesA | List a directory or read a text file from a snapshot's installed software without starting a machine. Files under /data are not shown. |
| instabox_create_snapshotA | Save a machine as a private snapshot, then start new machines from it with instabox_create_machine |
| instabox_delete_snapshotA | PERMANENTLY delete a snapshot. Machines already created from it are not affected. |
| instabox_list_portsA | List published ports (public HTTPS URLs) of one machine, or of all your machines when |
| instabox_publish_portA | Give a port of a machine a public HTTPS URL. WARNING: the URL is not secret; anyone who has it can reach the whole service on that port until you unpublish it. It does not start a server. A visit wakes an idle-paused machine. Max 16 per machine, ports 1024-65535. Publishing again keeps the URL and renames it. |
| instabox_unpublish_portA | Remove a port's public URL and close its open connections. The server inside the machine keeps running. |
| instabox_create_ssh_tokenA | Create a ready-to-run |
| instabox_list_ssh_tokensA | List a machine's SSH tokens (newest first), without their secrets. |
| instabox_revoke_ssh_tokensA | Revoke one SSH token (give |
| instabox_list_org_secretsA | List the names, delivery mode (proxy or env), allowed hosts and versions of an org's Secrets. Values are never returned. Get the org ID from instabox_whoami or a machine's |
| instabox_get_machine_secretsA | Show which org Secrets a machine has selected and the delivery status of the outbound proxy and the guest environment (metadata only). |
| instabox_update_machine_secretsA | Replace the org Secrets a machine may use. Each field you pass replaces that whole selection; omitted fields stay as they are. SECURITY: |
| instabox_refresh_machine_secretsA | Push the current Secret selection to a RUNNING machine now (installs the environment and CA, requests proxy reconciliation). Check the returned proxy and guest statuses. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| status | Summarise the account, limits, machines, snapshots and public ports. |
| run | Run a shell command on a machine and show the result. |
| new-sandbox | Create a short-lived machine, optionally run a setup command, and report how to use it. |
| expose | Publish a machine port as a public HTTPS URL and check something is listening. |
| backup | Save a machine as a snapshot and wait until it is ready. |
| cleanup | List machines and snapshots that look unused and propose what to delete (never deletes without asking). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.