---
title: "corecluster_package_change"
url: https://docs.corefinity.com/mcp/tools/corecluster_package_change
type: tool
last_updated: 2026-11-13
feature: upgrades
related:
  - https://docs.corefinity.com/api/reference/sites/update-cluster-package.md
  - https://docs.corefinity.com/guides/sites/size-and-capacity/upgrade-a-package.md
---
# corecluster_package_change

**Change a CoreCluster's package.** Move a CoreCluster to a larger package. It is charged at the new package's price: price it first with corestack_billing_quote_preview and pass its quote_id. Scope: write. Long-running: answers with a task.

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

## When to use it

Move a CoreCluster to a larger package. It is charged at the new package's price: price it first with corestack_billing_quote_preview and pass its quote_id.

The move is an in-place upgrade: the cluster keeps running and billing throughout. A smaller package is not offered here (`downgrade` below): the person arranges it with Corefinity support — and a package that does not offer every site the cluster runs (a platform or a size) refuses the change all the same, in the same words a new site would answer.

The package must be a CoreCluster package. A Managed Websites (CoreStack) package, such as `cs8`, is refused with `invalid_arguments` on `package`, in the Control Panel's words, and nothing is started.

Automatic upgrades: on a CoreCluster whose company turned them on, a create that would take the cluster past 90 % of its package first buys the smallest add-on raise that makes room (or, when add-ons cannot, the next package), within the company's monthly limit, and goes ahead. Each upgrade stays on the monthly bill until it is changed back. Over the limit it is refused with `capacity_blocked`, naming the limit. See corestack_company_auto_upgrades_get.

## Inputs

- `cluster_id` (integer, ≥ 1, required)
- `package` (string, up to 64 characters, required): The new package's key (corestack_packages_list with cluster_id shows what each change would be).
- `confirm_name` (string, up to 100 characters, required): The cluster's name, typed exactly.
- `quote_id` (string, pattern `^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$`): The quote from corestack_billing_quote_preview; optional.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cluster_id": {
      "minimum": 1,
      "type": "integer"
    },
    "confirm_name": {
      "description": "The cluster's name, typed exactly.",
      "maxLength": 100,
      "type": "string"
    },
    "package": {
      "description": "The new package's key (corestack_packages_list with cluster_id shows what each change would be).",
      "maxLength": 64,
      "type": "string"
    },
    "quote_id": {
      "description": "The quote from corestack_billing_quote_preview; optional.",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "type": "string"
    }
  },
  "required": [
    "cluster_id",
    "package",
    "confirm_name"
  ],
  "type": "object"
}
```

## Refusals

- `stale`: the quote no longer matches this change or has expired; preview a new one with corestack_billing_quote_preview and call again with its quote_id.
- `billing_forbidden`: the person has no billing role in the company; ask a company owner or billing member.
- `downgrade`: this would be a downgrade, which this tool does not do; the person should contact Corefinity.
- `same_package`: the row is already on that package; nothing to change.
- `legacy_cluster`: the cluster has not been moved to the current platform yet; this is available after its upgrade.
- `cluster_busy`: another change is running on the cluster; wait for it and call again.
- `cluster_not_ready`: the cluster is not ready yet (still being created or changed); wait and call again.
- `region_unavailable`: that region is not available; choose another (corestack_regions_list).
- `support_only`: unfinished work or a hold by Corefinity's team blocks this; contact support, retrying cannot help.
- `demo_keep_required`: the site or cluster is a free demo that is not kept yet, and this change costs money: it starts once the demo is kept. Ask the person to keep it (`corestack_demo_keep`, or open `keep_url`); `change` names this change and what it would cost a month once kept.
- `capacity_changes_paused`: changes to this cluster's capacity are paused for planned maintenance; nothing was started — 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_package_change",
  "arguments": {
    "cluster_id": 812,
    "package": "large",
    "confirm_name": "Staging"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corecluster_package_change with cluster_id 812, package large. (Change a CoreCluster's package.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/clusters/{cluster}/package](https://docs.corefinity.com/api/reference/sites/update-cluster-package.md)
- Guide: [Upgrade package](https://docs.corefinity.com/guides/sites/size-and-capacity/upgrade-a-package.md)
