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

**Set a CoreCluster's add-ons.** Set a CoreCluster's four add-on allowances — extra cores, memory, disk and log storage — to the values given (a decrease too). It applies at once. Price it first with corestack_billing_quote_preview. Scope: write.

- Scope: `write`
- Runs as a task: no

## When to use it

Set a CoreCluster's four add-on allowances — extra cores, memory, disk and log storage — to the values given (a decrease too). It applies at once. Price it first with corestack_billing_quote_preview.

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)
- `cores` (integer, 0–512, required)
- `memory_gb` (integer, 0–4096, required)
- `disk_gb` (integer, 0–65536 in MCP, required)
- `log_storage_gb` (integer, 0–65536, required)
- `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}$`): A quote from corestack_billing_quote_preview (optional): the write refuses with stale if the price moved.

MCP refuses `disk_gb` above 65536 during schema validation, before the service runs. REST and the domain allow up to 102400 GB (100 TB), subject to their validation rules; that higher range is unavailable through this MCP tool. Values within the MCP range must still meet the domain's steps and other checks.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cluster_id": {
      "minimum": 1,
      "type": "integer"
    },
    "cores": {
      "maximum": 512,
      "minimum": 0,
      "type": "integer"
    },
    "disk_gb": {
      "maximum": 65536,
      "minimum": 0,
      "type": "integer"
    },
    "log_storage_gb": {
      "maximum": 65536,
      "minimum": 0,
      "type": "integer"
    },
    "memory_gb": {
      "maximum": 4096,
      "minimum": 0,
      "type": "integer"
    },
    "quote_id": {
      "description": "A quote from corestack_billing_quote_preview (optional): the write refuses with stale if the price moved.",
      "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",
    "cores",
    "memory_gb",
    "disk_gb",
    "log_storage_gb"
  ],
  "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.
- `contract_missing`: the billing contract changed while the change was being made; read the options again and call again. (A site or cluster with no billing contract is changed all the same, without a quote: it is not billed in the Control Panel.)
- `platform_cluster`: this is a platform cluster, where this setting is not yours to change.
- `cluster_legacy`: the cluster has not been moved to the current platform yet; this is available after its upgrade.
- `no_payment_method`: the company has no payment method; the person must add one in the Control Panel.
- `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.
- `cluster_deleting`: the cluster is being deleted.
- `capacity_blocked`: there is not enough capacity for this; check corecluster_capacity_check or choose another size.
- `addon_bounds`: the add-on amount is outside what the package allows; choose a value inside its bounds.
- `billing_forbidden`: the person has no billing role in the company; ask a company owner or billing member.
- `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.
- 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_addons_set",
  "arguments": {
    "cluster_id": 812,
    "cores": 1,
    "memory_gb": 1,
    "disk_gb": 1,
    "log_storage_gb": 1
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corecluster_addons_set with cluster_id 812, cores 1, memory_gb 1, disk_gb 1, log_storage_gb 1. (Set a CoreCluster's add-ons.) Tell me what it returned.
```

## The same task elsewhere

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