statioEverything you can do to an MCP server from the dashboard, you can do from a pipeline. Statio's deploy API is authenticated with an API key rather than a browser session, so a CI runner can drive it without a human present.
Why this is not just "the same API with a token"Most platforms hand CI a long-lived admin credential and hope. A Statio key acts with the authority of the person who created it and can never exceed it — so a pipeline key cannot deploy a server its owner has no rights to, and revoking that person's access revokes the pipeline at the same moment. There is no separate list of machine permissions to keep in step with the human one.
Cutting a releaseReturns a deployment to poll. The build runs in the background: spec fetch, generation, image build, rollout, tool discovery.
The idempotency key mattersSend one on every release. A pipeline step that times out and retries must not start a second build of the same commit — with the key, the retry replays the original response instead of duplicating work.
Watching itPoll until status reads succeeded or failed. The logs endpoint returns the complete build and deploy output — what you want your pipeline to print when a deploy fails, rather than sending someone to a dashboard.
Rolling backThis redeploys the image already built for that version. It does not rebuild — so you get back exactly what was running before, rather than whatever your spec says today. That distinction matters at 2am: a rollback that rebuilds is not a rollback, it is another deploy that happens to use an older number.
Rollback returns your code, not your configuration. Credentials, permissions and outbound allowlists are current-state and are not versioned with the image.
EnvironmentsDeploy to a lower environment, then promote upward. Promotion requires a different capability from deploying — a developer with full deploy rights still cannot promote their own work to production. That separation is deliberate, and it is enforced by the same roles that govern everything else, not by a second approvals system.
What a caller cannot seeThe complete API reference, generated from the specification the service actually serves, lives at docs.statio.dev.
statio