---
title: "corestack_deployments_template_versions_list"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_template_versions_list
type: tool
last_updated: 2026-11-13
feature: deployment-templates
related:
  - https://docs.corefinity.com/api/reference/deployments/list-deploy-template-versions.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/deployment-templates.md
---
# corestack_deployments_template_versions_list

**Deployment template versions.** A deployment template's saved revisions, newest first: who saved each, what it changed and how many environments it reached. With config and stage, only the revisions that set that stage; with level corefinity, Corefinity's default versions. Scope: read.

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

## When to use it

List a deployment template's saved revisions, newest first: who saved each (a person, "MCP token {name}" or Corefinity support), what it changed and how many environments it reached. With `config` and `stage` together, only the revisions that set that stage: the candidates for `corestack_deployments_pipeline_template_reset` `version` (pass `version_ref` as it is). With `level: corefinity`, Corefinity's default versions instead.

The same action in the public REST API, with the same checks, refusals and scope: `GET /api/corestack/companies/{company}/deploy-templates/{platform}/versions`.

## Inputs

- `platform` (string, required)
- `cursor` (integer, 0 to 999999): next_cursor of the page before.
- `config` (string, one of `production`, `uat`): With stage.
- `stage` (string, one of `build`, `database`, `post_deploy`, `settings`): With config.
- `level` (string, one of `corefinity`): Corefinity's default versions instead.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "config": {
      "description": "With stage.",
      "enum": [
        "production",
        "uat"
      ],
      "type": "string"
    },
    "cursor": {
      "description": "next_cursor of the page before.",
      "maximum": 999999,
      "minimum": 0,
      "type": "integer"
    },
    "level": {
      "description": "Corefinity's default versions instead.",
      "enum": [
        "corefinity"
      ],
      "type": "string"
    },
    "platform": {
      "enum": [
        "magento2",
        "laravel",
        "wordpress",
        "shopware5"
      ],
      "type": "string"
    },
    "stage": {
      "description": "With config.",
      "enum": [
        "build",
        "database",
        "post_deploy",
        "settings"
      ],
      "type": "string"
    }
  },
  "required": [
    "platform"
  ],
  "type": "object"
}
```

## Refusals

- 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_deployments_template_versions_list",
  "arguments": {
    "platform": "magento2",
    "config": "production",
    "stage": "post_deploy"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_template_versions_list with platform magento2, config production, stage post_deploy. (Deployment template versions.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/companies/{company}/deploy-templates/{platform}/versions](https://docs.corefinity.com/api/reference/deployments/list-deploy-template-versions.md)
- Guide: [Deployment templates](https://docs.corefinity.com/guides/sites/code-and-deployments/deployment-templates.md)
