Automation
Operate Serversinc through the REST API, MCP server, and deploy triggers.
The dashboard, REST API, and MCP server act on the same organisation resources. A deploy trigger can deploy one application and nothing else, so a leaked CI secret can’t affect anything more.
| Need | Interface |
|---|---|
| Build an integration | REST API |
| Let an AI client inspect or manage your servers | MCP server |
| Deploy one application from CI | Deploy trigger |
| Inspect state and make occasional changes | Dashboard |
In CI, log the application, image tag or commit, and the returned deployment ID. Don’t log the deploy secret.
In this section
Section titled “In this section”- API tokens and MCP server: Create tokens and connect the REST API or an MCP client.
- Deploy triggers: Deploy one application from CI.
Next steps
Section titled “Next steps”- Organisation and account: create tokens and review active sessions.
- Applications: configure deploy triggers and inspect deployments.
- Reference: review lifecycle states and operation semantics.