Agent servers
Sizing, disk, self-deploy tokens, and what happens when you delete an agent server.
What an agent server is
An agent server — instances in the API and MCP tools — is the always-on workstation one or more Teammates run on: its own files, its own tools, always running. You create one, decide which Teammates share it, and wire up who on your team can talk to them. Everything you configure here (size, disk, self-deploy) stages as a pending change and takes effect on your next deploy.
Size
Every agent server has a size, chosen from two families:
| Family | Best for |
|---|---|
| Standard | Ops, support, SEO, sales — general-purpose Teammates |
| Performance | Engineering — heavier compute workloads |
Each family comes in Small, Medium, Large, and XL, differing in vCPU and RAM. See pricing for the full size catalog and current rates — this page won't restate numbers that live there.
Changing size later works the same as setting it initially: it's a pending change, applied on deploy.
Disk
Disk size ranges from 20 GB to 1000 GB. The default for a new agent server is 20 GB — raise it if your Teammates' workspace, skills, or working files need more room.
Self-deploy
Each agent server has its own MCP token, used when a Teammate (or a script acting through that server) calls the API on the server's behalf. The allow_self_deploy toggle controls whether that token is allowed to trigger a deploy for its own server. Leave it off unless you specifically want a Teammate to be able to deploy changes to its own server without a human clicking Deploy.
Trial limits
Note: Trial accounts are capped to a single agent server, and that server's configuration is locked — you can't edit its size, disk, or self-deploy setting, and you can't delete it. Upgrading your plan lifts all three restrictions. See Team & billing.
These limits exist so a trial always has a working baseline to build on — see Getting started for how your first agent server is provisioned automatically.
Deleting an agent server
Deleting an agent server stages a removal that takes effect on your next deploy. Once it goes live, the server's MCP tokens are revoked — anything that was authenticating with that server's token stops working. Make sure nothing outside the platform depends on that token before you delete.
Deleting removes every Teammate on that server along with it.
You can't delete your only agent server while on a trial (see Trial limits above).
Shutdown vs. delete
Shutting down an agent server stops it without deleting its configuration. Deleting is permanent (subject to the pending/deploy cycle above); shutdown is not.
Also configurable per server
A few things that live at the agent-server level are documented on their own pages because they have enough surface area to need it:
- Model configuration — an agent server can narrow the company-wide allowed model list to a subset for its own Teammates.
- Secrets & egress — host allowlists and secret overrides can be scoped to a server.
- Deploys & pending changes — force-deploy and discard operate per server.
API and MCP
Agent servers have full dashboard/API/MCP parity — everything above is available through the HTTP API and MCP tools as well as the dashboard. See API & MCP for the resource map.