MCP and HTTP API
Manage environments from your terminal or native client through the same authorized controller.
Connect an operator MCP client
Register enginebox-fleet-mcp as a stdio server in your client's normal MCP configuration. With a source build:
export ENGINEBOX_API_URL=http://127.0.0.1:8765
export ENGINEBOX_API_TOKEN_FILE="$HOME/.local/state/enginebox/api.token"
target/release/enginebox-fleet-mcpThe operator token stays on the operator/controller machine. Do not put it inside agent guests or browser storage. Guest browser/computer MCP is a separate, narrower interface. Remote API origins require HTTPS; a local SSH tunnel can keep the configured origin on loopback.
Use the tool for the operation
| Work | MCP tools |
|---|---|
| Inspect and allocate | fleet_inventory, fleet_allocate, fleet_create |
| Lifecycle and jobs | fleet_action, fleet_job |
| Templates | template_catalog, template_register, template_install, template_sync |
| Native agents | agent_connections, agent_launch, agent_run |
| Checkout storage | storage_catalog, storage_inspect, storage_preview, storage_import, storage_fork, storage_action |
Tool schemas describe required arguments. Host and project IDs come from the administrator's registry. Native agent launches use assigned running workspaces and return private run results.
The same operations over HTTP
All /v1/ endpoints require a bearer token. Common entry points are:
| Request | Purpose |
|---|---|
GET /v1/fleet | Hosts, capacity and workspaces |
GET /v1/templates | Template manifests and node installation state |
GET /v1/agents | Owner account connections |
GET /v1/storage | Registered storage nodes and projects |
POST /v1/hosts/{host_id}/allocations | Claim a fresh reserve or create a clone |
POST /v1/hosts/{host_id}/instances/{name}/actions | Pause, resume, hibernate or stop |
GET /v1/jobs/{job_id} | Poll an operation |
Use the fleet reference and storage reference for complete request shapes and restrictions.
Accepted is not ready
Lifecycle, creation and storage mutations return a job. Poll it until completion; a queue receipt is not a ready workspace. Admission, ownership checks and per-host coordination apply equally to the dashboard, API and MCP.
After an interrupted operation, inspect actual resources before retrying. The controller does not replay an uncertain mutation automatically. Native runs have their own bounded queue and private result endpoint.
These are infrastructure and launch interfaces. Multi-agent planning, task delegation policies and application data publication remain separate layers.