Manage your infrastructure from a conversation.
Triton MCP is built agent-first: a launch-day, first-class surface that lets an agent read and manage the same Instances, Buckets, and networks your CLI does.
Instances, Buckets, and networks — from a prompt.
The launch tool surface covers Instances, Object Storage, and Networking — read plus provision and manage. Nothing else, and nothing pretend.
Instances
Create, list, stop, and resize Instances; read their state, addresses, and metrics.
Object Storage
Create and list Buckets, list and put objects, manage access levels.
Networking
Inspect and manage VPCs, subnets, Reserved IPs, and firewall rules.
A small surface is the point
Every MCP tool is backed by the same coherent /v1 OpenAPI specification as the CLI and console. One well-defined tool set means an agent gets consistent names, consistent errors, and predictable behavior — instead of hundreds of half-tested tools it can wander into. The narrowness is deliberate design, not a gap.
/v1 OpenAPI spec
→ Console · CLI · API · MCP
Same names, same errors, same behavior, whichever surface calls it.
Three steps to a connected agent.
- Add the Triton MCP server to your agent’s configuration.
- Authorize it with an API token from your account.
- Ask for what you want; review the action it proposes.
Creating Baron · 2 vCPU / 4 GB / 50 GB NVMe in ams-1.
web-05 is provisioning. One action, exactly what you asked for.
No new credential type
MCP credentials are ordinary API tokens — the same kind you already use for the CLI and API. Connecting an agent does not require issuing a different kind of secret, so the tokens you audit, scope, and revoke today cover MCP too.
What connecting an agent could mean
A separate agent secret — a new kind of credential to issue, scope, rotate, and audit on its own track.
What it means here
An ordinary API token. The tokens you already audit, scope, and revoke for the CLI and API cover MCP too.
A launch capability, not a labs tab
MCP ships on day one with first-class placement in signup and the console — not an experiment behind a flag. If you manage infrastructure through an agent, this surface was built for that from the start.
MCP is a public-cloud surface at launch; it has no on-prem console presence yet.