corestack_ packages_ list
Packages.
When to use it
The packages on offer — the CoreCluster ladder (product_line cc, the default) or the CoreStack site ladder (cs) — with the platforms each can host; a package is named by its key wherever a tool takes package. No prices: corestack_billing_catalogue_get has them.
Only packages on sale are listed: the first CoreCluster row is the smallest one on sale, and a package Corefinity has taken off sale is not in the answer (a running cluster on one keeps working and keeps its price).
platforms[] (the CoreStack wizard's create lists): php_wait ({message}) is on a platform only while no PHP version of its create list is open to new sites: a create that names none then waits for the platform's default instead of being refused, and message says so ("PHP 8.3 isn't available for new sites yet. Your site will be set up as soon as it is."). php_versions lists only the PHP versions a new site can be created on, each with its status, and default marks the one a create that names none takes, as corestack_site_provisioning_options lists them; while none is open it is empty and php_wait names the version a create waits for.
Ask for it
Using the Corefinity MCP server, call corestack_packages_list. (Packages.) Tell me what it returned.Inputs
Your CoreCluster: marks its current package and what a change to each would be (cc only). At least 1.
Accepted; every package is offered in both families.
generaloptimisedOnly the packages that can host this platform.
wordpresslaravelmagento2shopware5cc (CoreCluster packages, the default) or cs (CoreStack site packages).
csccOnly the packages offered in this region: uk, us, nl or aus. Up to 16 characters.
Example call
{
"name": "corestack_packages_list",
"arguments": {}
}If it is refused
| Reason | What to do |
|---|---|
feature_off | An input needs a feature that is switched off (for example apply: "tonight" while the maintenance window queue is switched off); leave that input out. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |