corestack_ node_ catalogue_ get
Node.js catalogue.
When to use it
See which Node.js majors the Control Panel offers, with their status and end-of-life dates, the default for new sites, the curated global packages and the package limit. With site_id the answer is that row's own options (16 only where it already runs, the platform's floor, which majors need an end-of-life acknowledgement); with platform it is what a new site of that platform may choose. Without a row any token reads it.
Ask for it
Using the Corefinity MCP server, call corestack_node_catalogue_get with site_id 4211. (Node.js catalogue.) Tell me what it returned.Inputs
platformstring
A site not created yet: its platform's floor.
wordpresslaravelmagento2shopware5site_idinteger
A row: its own availability and offer rules. At least 1.
Example call
{
"name": "corestack_node_catalogue_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
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. |
The same task elsewhere
Was this helpful?