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

**Pipeline versions.** A binding's saved pipeline versions, newest first: who saved each, when, what it changed and whether it can be restored. Read one with corestack_deployments_pipeline_get version_id; restore one with corestack_deployments_pipeline_restore. Scope: read.

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

## When to use it

List a binding's saved pipeline versions, newest first: who saved each, when, from where (`source`), which stages or settings it changed, and whether it can be restored (the kept version from before the conversion and the current one cannot). Pass `stage` for only the versions that changed that stage or the settings. Read one with `corestack_deployments_pipeline_get` `version_id`, restore one with `corestack_deployments_pipeline_restore`. Every kept version is on one page.

The same action in the public REST API, with the same checks, refusals and scope: `GET /api/corestack/sites/{site}/deployments/pipeline/{binding}/versions` (`stage`).

## Inputs

- `site_id` (integer, ≥ 1, required)
- `binding_id` (integer, ≥ 1): Default: the environment's default binding.
- `stage` (string, one of `build`, `database`, `post_deploy`): Only the versions that changed this stage or the settings.
- `cursor` (string, up to 200 characters): Every kept version is on one page: next_cursor is always null.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "binding_id": {
      "description": "Default: the environment's default binding.",
      "minimum": 1,
      "type": "integer"
    },
    "cursor": {
      "description": "Every kept version is on one page: next_cursor is always null.",
      "maxLength": 200,
      "type": "string"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "stage": {
      "description": "Only the versions that changed this stage or the settings.",
      "enum": [
        "build",
        "database",
        "post_deploy"
      ],
      "type": "string"
    }
  },
  "required": [
    "site_id"
  ],
  "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_pipeline_versions_list",
  "arguments": {
    "site_id": 4211,
    "stage": "post_deploy"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_pipeline_versions_list with site_id 4211, stage post_deploy. (Pipeline versions.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/deployments/pipeline/{binding}/versions](https://docs.corefinity.com/api/reference/deployments/list-site-deployment-pipeline-versions.md)
- Guide: [Pipeline](https://docs.corefinity.com/guides/sites/code-and-deployments/pipeline-stages.md)
