corestack_ company_ magento_ keys_ check
Check the Magento repository keys.
When to use it
Ask repo.magento.com again whether your company's own Magento repository keys still work and whether they include Adobe Commerce, for example after the company's Adobe licence changed. The answer is the keys as corestack_company_magento_keys_get reads them, with entitlements. Never a key. For a client company your agency manages, send client_company_id.
Ask for it
Using the Corefinity MCP server, call corestack_company_magento_keys_check. (Check the Magento repository keys.) Tell me what it returned.Inputs
client_company_idinteger
A client company your agency manages, by id. Omit for your own company. At least 1.
Example call
{
"name": "corestack_company_magento_keys_check",
"arguments": {}
}If it is refused
| Reason | What to do |
|---|---|
not_configured | Your company has no keys of its own (it uses Corefinity's, or none). |
upstream_unavailable | Repo.magento.com did not answer; the last answer stands. |
rate_limited | At most 6 checks an hour per company, shared with the Control Panel. |
pin_refused | A token limited to some sites cannot change company-wide settings. |
tenant_mismatch | The company is not one your agency manages, or it does not exist; the same answer for both. Being attached to your agency is not enough: one of its live CoreStack sites must name your agency as its managing agency. |
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. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
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?