Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
INSTABOX_API_KEYYesInstaBox 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_URLNoAPI base URLhttps://api.instabox.sh
INSTABOX_READ_ONLYNoSet to true to register only the read-only tools.off
INSTABOX_MAX_OUTPUT_CHARSNoCap 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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
instabox_whoamiA

Show which user/org the configured API key belongs to, including allowedSpecs (machine sizes this account may create) and lifecycle policy. Any key may call this, so it is the cheapest way to check that credentials work.

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 creatable: true can be used; the free plan can create from agent-browser only. Needs machines:read or images:read.

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 nextCursor; pass it back as cursor for the next page.

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 templateId OR snapshotId (neither: agent-browser). Leave size fields out for the default 4 vCPU / 8 GiB; other sizes must be ones your plan allows (see instabox_whoami allowedSpecs). Counts against your machine limit even when stopped or paused.

instabox_update_machineA

Change a machine's idle auto-pause time and/or labels. Applies immediately in any state. metadata REPLACES all labels ({} clears them). Fields you leave out are unchanged. Auto-pause is only honoured on accounts with manual lifecycle; the reply shows the effective value.

instabox_machine_powerA

Change a machine's power state. start: boot a stopped machine (resumes a paused one). stop: shut down; processes end, files kept (a paused machine cannot be stopped: resume or delete it). suspend: pause, keeping memory and running processes. resume: continue a paused machine where it left off. A machine runs one operation at a time (409 operation_conflict otherwise). Commands, files and SSH wake an idle-paused machine automatically, but a machine you paused or stopped stays off until you start/resume it.

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, confirm must be the machine's exact ID or name; the server rejects anything else with 409 delete_confirmation_required. Needs the machines:delete scope.

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 waitSeconds it long-polls until the operation changes or finishes.

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 cmd (a shell string, run with bash -lc) OR argv (program + arguments, no shell, no expansion). Runs as the machine's user in /data/home by default. Max 600 s per call: for long jobs start them in the background (e.g. nohup … > /data/home/job.log 2>&1 &) and poll the log. Not idempotent: a retry runs the command again. A machine paused for idleness is woken first; a machine you stopped returns 409 machine_not_running. This executes arbitrary code with root-capable access in the machine.

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 binary: true and no content. Use instabox_exec for larger files. The machine must be running (an idle-paused one is woken).

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. status is ready (usable), pending (a live snapshot still uploading) or failed (see error).

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 snapshotId. A stopped machine is saved at once; a running one is saved live (if the server allows) and the snapshot is pending until uploaded; data programs had not yet written to disk is not included. By default this waits until the snapshot is ready. Counts against your snapshot and storage limits. Needs images:write.

instabox_delete_snapshotA

PERMANENTLY delete a snapshot. Machines already created from it are not affected. confirm must be the snapshot's exact ID or name (server-checked). Needs images:delete.

instabox_list_portsA

List published ports (public HTTPS URLs) of one machine, or of all your machines when id is omitted.

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 ssh command for a machine (no key or CLI needed). SECURITY: the token is a secret; anyone holding it can log in to the machine until it expires or is revoked, and it is shown only in this response. Prefer a short ttl. Not idempotent: each call makes another token.

instabox_list_ssh_tokensA

List a machine's SSH tokens (newest first), without their secrets.

instabox_revoke_ssh_tokensA

Revoke one SSH token (give tokenId) or every token of the machine (omit it), closing their connections.

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 orgId.

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: secrets lets code in the machine send those credentials to their allowed hosts, and envSecrets puts real values into the machine. Delivery then updates in the background; refresh with instabox_refresh_machine_secrets.

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

NameDescription
statusSummarise the account, limits, machines, snapshots and public ports.
runRun a shell command on a machine and show the result.
new-sandboxCreate a short-lived machine, optionally run a setup command, and report how to use it.
exposePublish a machine port as a public HTTPS URL and check something is listening.
backupSave a machine as a snapshot and wait until it is ready.
cleanupList machines and snapshots that look unused and propose what to delete (never deletes without asking).

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 30 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues