Delete a server that Tarsana did not create

Destructive · POST /v1/tenants/{tenant}/providers/{provider_name}/servers/{server_id}/destroy · MCP tool destroy-server

Deletes one server from your cloud account, by the ID that servers showed. Tarsana reads your server list again first: a server that is not in it is refused, and so is a server that Tarsana created, because you remove those with decommission-server. Your request and its result are both recorded.

Roles that can call it: deployer.

Parameters

Name	In	Required	Description
`tenant`	path	yes	Your tenant ID
`provider_name`	path	yes	The provider's name, for example `hetzner`
`server_id`	path	yes	The server's ID at the provider, as `servers` showed it

Returns

A JSON object with these keys: tenant, provider_name, server_id, destroyed, guarantee, caller_authenticated.

Example request

curl -X POST https://api.tarsana.io/v1/tenants/acme/providers/hetzner/servers/1001/destroy \
  -H "X-Tarsana-Access-Token: $ACCESS_TOKEN" \
  -H 'X-Tarsana-Tenant: acme'

Example response

{
  "tenant": "acme",
  "provider_name": "hetzner",
  "server_id": "1001",
  "destroyed": {
    "journal": "679a3d14fd7f61cc8698f3d2ca50f837",
    "operation_id": "5002",
    "requested_at": "2026-10-05T02:15:41.159329+00:00",
    "server": {
      "id": "1001",
      "name": "my-own-box"
    }
  },
  "guarantee": "namespaces are separated, callers are not authenticated",
  "caller_authenticated": false
}

Errors

Code	HTTP	What it means
`invalid_parameter`	400	A value in your request does not have the expected format, for example a submission ID that is not a spec hash. Check the value against the field's description and try again.
`no_acting_tenant`	400	Your request does not say which tenant you are acting for. Send your tenant ID in the `X-Tarsana-Tenant` header, or with `--as` on the command line.
`isolation_refused`	403	This address belongs to a tenant ID you do not have access to. Check the tenant ID in the address and in your request header.
`tenant_refused`	400	This tenant ID is not allowed, or is not in the expected format. Use a different ID made of lower-case letters, digits, dots, dashes and underscores.
`servers_not_configured`	503	Listing your servers is not available on this Tarsana deployment. Contact Tarsana support if you need it.
`no_such_provider`	404	Tarsana does not support a provider with this name. The response lists the providers you can use.
`servers_unavailable`	502	Your server list could not be read with your stored credential: none is stored, the provider refused it, or the provider could not be reached. Check your credential with `provider-credential`, then try again.
`no_such_server`	404	Your server list at this provider has no server with this ID. Check the ID with `servers` and try again.
`server_accounted_for`	409	Tarsana created this server, so you cannot delete it here. Remove it with `decommission-server` instead.
`destroy_failed`	502	The provider did not delete the server, and your request and its result are recorded. Try again, or check the server at your provider.
`unauthenticated`	401	Your request has no credential, or one that Tarsana does not recognise. Sign in with `login`, or send a valid access token.
`forbidden`	403	Your role does not allow this operation. The response names the roles that do; ask for a credential with one of them.
`rate_limited`	429	You sent too many requests in a short time. Wait for the number of seconds in `retry_after_seconds`, then try again.
`surface_fault`	500	Something went wrong on our side. Try again later, and contact Tarsana support if it keeps happening.

View this page as Markdown