---
title: "corestack_app_versions_list"
url: https://docs.corefinity.com/mcp/tools/corestack_app_versions_list
type: tool
last_updated: 2026-11-13
feature: app-versions
related:
  - https://docs.corefinity.com/api/reference/runtime/list-app-versions.md
  - https://docs.corefinity.com/guides/sites/software-and-services/application-versions.md
---
# corestack_app_versions_list

**List application versions.** Lists the application versions you can create sites with: per platform its editions and lines, each with status, security end date, fresh and empty availability, PHP and MariaDB choices. Optionally where the site would go (cluster_id or region). Pass the chosen app_version and edition to the create tools. Scope: read.

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

## When to use it

Before creating a site, list the application versions you can create it with: for each platform its editions and lines, each line's status (supported, security-only or ended), its security end date, whether a fresh install or an empty site is available and why not, and the PHP and MariaDB versions it allows with their defaults. A line that declares `services` — Mage-OS 4 today — also names the engines it is built for (`search`, `cache`, `broker`, `varnish`), each with the version it targets. Adobe Commerce shows whether the company's own repository keys allow it. A platform that carries a `warning` — Shopware 5's end-of-life notice — returns the same sentence the order page shows, so a caller can pass it on before it creates a site. Pass the chosen `app_version` and `edition` to the create tools.

## Inputs

- `platform` (string, optional): one platform only, for example `magento2`.
- `cluster_id` (integer, optional): a CoreCluster you would create the site on; its architecture and its company's Adobe Commerce keys decide what is available.
- `region` (string, optional): a CoreStack region instead. Give `cluster_id` or `region`, never both.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cluster_id": {
      "minimum": 1,
      "type": "integer"
    },
    "platform": {
      "description": "One platform key, e.g. magento2.",
      "maxLength": 32,
      "type": "string"
    },
    "region": {
      "description": "A CoreStack region key.",
      "pattern": "^[a-z]{2,8}$",
      "type": "string"
    }
  },
  "type": "object"
}
```

## Refusals

- `invalid_arguments`: a platform or region that names nothing you can use, or both `cluster_id` and `region`.
- `catalogue_unavailable`: the versions catalogue cannot be read just now. Try again later; nothing is guessed.
- 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_app_versions_list",
  "arguments": {
    "platform": "magento2",
    "cluster_id": 12
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_app_versions_list with platform magento2, cluster_id 12. (List application versions.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/app-versions](https://docs.corefinity.com/api/reference/runtime/list-app-versions.md)
- Guide: [Application versions](https://docs.corefinity.com/guides/sites/software-and-services/application-versions.md)
