delete_cluster

Active

declared in 2.0.0

Deletes an autoscaling cluster — tears down the WHOLE Heat stack: every autoscaled EXTRA member VM, the Octavia load balancer, the pool, the cluster security group, and the cluster's *.redu.cloud proxy host. Your SOURCE (hero) VM is NOT part of the stack and is NOT deleted — it was the always-on baseline member but it is your own VM; delete_instance it separately if you no longer need it. Pass stack_name + stack_id from list_clusters. Deleting extra members individually does NOT work (the autoscaling group re-creates them under load) — this deletes the group itself. The managed database / external store the cluster used is NOT touched (data safety); delete_database it separately when you are done with the data. Cannot be undone.

Parameters schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "stack_name",
    "stack_id"
  ],
  "properties": {
    "stack_id": {
      "type": "string",
      "minLength": 1,
      "description": "Cluster (Heat stack) id — from list_clusters (id)."
    },
    "stack_name": {
      "type": "string",
      "minLength": 1,
      "description": "Cluster (Heat stack) name — from list_clusters (stack_name)."
    }
  },
  "additionalProperties": false
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.70.

Parent server

cloud.redu/mcp

1/7 registries

View full server →