---
title: "corestack_company_magento_keys_delete"
url: https://docs.corefinity.com/mcp/tools/corestack_company_magento_keys_delete
type: tool
last_updated: 2026-11-13
feature: magento
related:
  - https://docs.corefinity.com/api/reference/organisation/delete-company-magento-keys.md
  - https://docs.corefinity.com/guides/platforms/magento-2.md
---
# corestack_company_magento_keys_delete

**Remove the Magento repository keys.** Remove your company's own repo.magento.com keys. Its Magento 2 sites go back to Corefinity's keys where those are available. While Adobe Commerce sites use the keys, also send confirm_company set to the company name, exactly. For a client company your agency manages, send client_company_id. Scope: write.

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

## When to use it

Remove your company's own repo.magento.com keys. Its Magento 2 sites go back to Corefinity's keys where those are available. While Adobe Commerce sites use the keys, also send `confirm_company` set to the company name, exactly. For a client company your agency manages, send `client_company_id`.

When your agency removes a client company's keys, the client company's owners are emailed which agency and which person removed them, and when.

## Inputs

- `confirm_company` (string, up to 255 characters): Only needed while Adobe Commerce sites use the keys: the company name, exactly. Not needed when no Adobe Commerce site uses them.
- `client_company_id` (integer, at least 1): A client company your agency manages, by id. Omit for your own company.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "description": "A client company your agency manages, by id. Omit for your own company.",
      "minimum": 1,
      "type": "integer"
    },
    "confirm_company": {
      "description": "Only needed while Adobe Commerce sites use the keys: the company name, exactly (the client company's, with client_company_id).",
      "maxLength": 255,
      "type": "string"
    }
  },
  "type": "object"
}
```

## Refusals

- `confirm_mismatch`: Adobe Commerce sites use the keys and `confirm_company` was left out or is not the company name; `field` is `confirm_company`, `details.commerce_sites` counts them, and the message gives the company name to send; nothing was removed. Call again with `confirm_company` set to that name, exactly (their installs and builds fail until new keys are added).
- `tenant_mismatch` (with `client_company_id`): 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.
- `pin_refused` (with `client_company_id`): a token limited to some sites cannot act on a client company's keys.
- 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": "corestack_company_magento_keys_delete",
  "arguments": {}
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_company_magento_keys_delete. (Remove the Magento repository keys.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [DELETE /api/companies/{company}/magento-keys](https://docs.corefinity.com/api/reference/organisation/delete-company-magento-keys.md)
- Guide: [Magento 2](https://docs.corefinity.com/guides/platforms/magento-2.md)
