API tokens and MCP server

Create a token

1. Open Settings → Account and find API tokens.
2. Create a token and give it a name.
3. Optionally set an expiry.
4. Copy the token. Serversinc shows it once.

API and MCP requests use the permissions of the account that created the token, in its current organisation. A request can’t reach a resource in another organisation, even with a valid ID.

Use the REST API

The versioned REST API at https://api.serversinc.io/v1 exposes the platform resources used by the dashboard. Send the personal access token as a bearer token and request JSON responses.

Provisioning, deployments, commands, database operations, backups, and restores run in the background. The response contains the resource ID. Poll that resource until it reaches a final status. See Statuses.

Connect an MCP client

The Serversinc MCP server is available at https://api.serversinc.io/mcp. It lets a compatible AI client inspect and operate resources through named tools. Current tool groups cover servers, applications, deployments, container logs, databases, storage providers, backups, insights, and organisation activity.

Give the MCP client its own API token. The MCP server acts on the current organisation of the account that owns the token.

The client can call tools that deploy, delete, restore, and power off resources. Secret values are write-only over MCP. Configuration changes need a redeploy, and long operations return before they finish, so have the client check the resulting status after a change.

Rotate or revoke a token

To rotate a token, create a new one, update the client, then revoke the old one. Revoke a token immediately if it may have leaked.