---
title: "corecluster_delete"
url: https://docs.corefinity.com/mcp/tools/corecluster_delete
type: tool
last_updated: 2026-11-13
feature: clusters
related:
  - https://docs.corefinity.com/api/reference/corecluster/delete-cluster.md
  - https://docs.corefinity.com/guides/corecluster/cluster-overview.md
---
# corecluster_delete

**Delete a CoreCluster.** Delete a CoreCluster and everything on it, for good: every site, environment and deleted site in its grace period at once with no final snapshot, then its snapshots, capacity and SSH address. Read corecluster_delete_preflight first. Scope: destructive. Long-running: answers with a task.

- Scope: `destructive`
- Confirmation: `confirm_name`
- Runs as a task: yes

## When to use it

Delete a CoreCluster and everything on it, for good: every site, environment and deleted site in its grace period at once with no final snapshot, then its snapshots, capacity and SSH address. Read corecluster_delete_preflight first.

If external database access is on for any environment on the cluster, the delete turns it off first and then carries on by itself once access is off. The call then answers at once, and it is not an error: `{"operation": null, "queued": true, "reason": "external_db_delete_queued", "message": "Turning off external access, then deleting.", "turn_off_operation": {"id": 9123, "status_tool": "corestack_site_operation_get"}, "held_delete_id": 41}`. Follow the turn-off with its status tool if you want to; there is nothing else to send, and asking again while it waits gives the same answer.

## Inputs

- `cluster_id` (integer, ≥ 1, required)
- `confirm_name` (string, up to 100 characters, required): The cluster's name, typed exactly.
- `allow_non_empty` (boolean): Also delete every site, environment and snapshot still on the cluster. Without it a cluster that is not empty is refused.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "allow_non_empty": {
      "description": "Also delete every site, environment and snapshot still on the cluster. Without it a cluster that is not empty is refused.",
      "type": "boolean"
    },
    "cluster_id": {
      "minimum": 1,
      "type": "integer"
    },
    "confirm_name": {
      "description": "The cluster's name, typed exactly.",
      "maxLength": 100,
      "type": "string"
    }
  },
  "required": [
    "cluster_id",
    "confirm_name"
  ],
  "type": "object"
}
```

## Refusals

- `cluster_not_empty`: `corecluster_delete` without `allow_non_empty: true` while sites, environments, grace-period sites or snapshots remain; `details.totals` from the preflight and `details.preflight` naming the tool to read (corecluster_delete_preflight); show the person what would go; call again with `allow_non_empty: true` only if they agree.
- `capacity_changes_paused`: removing this cluster's own servers is paused for planned maintenance; nothing was deleted — try again later, or contact support if it is urgent (the refusal's message says so in the Control Panel's words).
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corecluster_delete",
  "arguments": {
    "cluster_id": 812,
    "confirm_name": "Staging"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corecluster_delete with cluster_id 812. (Delete a CoreCluster.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [DELETE /api/corestack/clusters/{cluster}](https://docs.corefinity.com/api/reference/corecluster/delete-cluster.md)
- Guide: [Cluster overview](https://docs.corefinity.com/guides/corecluster/cluster-overview.md)
