---
title: "corestack_enterprise_deployments_list"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_deployments_list
type: tool
last_updated: 2026-11-13
feature: enterprise-deployments
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md
---
# corestack_enterprise_deployments_list

**CoreStack Enterprise deployments.** A CoreStack Enterprise environment's deployments, newest first, with status, commit and which one is live. Scope: read.

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

## When to use it

List a CoreStack Enterprise environment's deployments, newest first: what ran, whether it worked, which commit it
deployed and which deployment is live (`is_current`). Use `corestack_enterprise_deployment_get` for one deployment's
state and what can be done with it now.

These tools are for CoreStack Enterprise environments only. A CoreStack or CoreCluster site's deployments are the
`corestack_deployment_*` and `corestack_deployments_*` tools (by `site_id`): they answer the site's deployment settings
and run the site's own rules, so they are separate tools. The same list is the public API's
`GET /api/environments/{environment}/deployments` with `limit`, `cursor` or `status`.

## Inputs

- `enterprise_env_id` (integer, ≥ 1, required): the CoreStack Enterprise environment's id
- `status` (string): only deployments in this status: `scheduled`, `running`, `failed`, `succeeded`, `cancelled`,
  `pending` (waiting to be deployed by hand), `queued`
- `limit` (integer, 1–100): items per page (25)
- `cursor` (string): the last answer's `next_cursor`, for the next page

Each item: `id`, `environment_id`, `name`, `status`, `git_commit`, `repository_id`, `pipeline_id`, `trigger` (`manual`,
`api`, `webhook`), `rollback_of_deployment_id`, `attempt_id`, `is_current`, `created_at` and `error`: why a failed
deployment failed, the same line the public API's list gives (null unless it failed). A new release whose container
keeps exiting fails as soon as that is clear, and its `error` starts `Application failure:` and names the container, its
exit code and its last message.

A deployment started by a git push also says what the push said about its commit, as its page shows it:
`git_commit_url` (the commit on the provider), `git_author` {`name`, `avatar_url`} and `git_merge_request` {`ref`
(`!12` for a GitLab merge request, `#12` for a GitHub or Bitbucket pull request), `kind` (`merge_request` or
`pull_request`), `url`}. Each is null when the push did not say, and for every deployment not started by a push; a
link is only ever an https address on the repository's provider. The public API's list gives the same three keys.

`next_cursor` is null on the last page.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cursor": {
      "description": "The last answer's next_cursor.",
      "maxLength": 40,
      "type": "string"
    },
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    },
    "limit": {
      "description": "Items per page, 1–100 (25).",
      "maximum": 100,
      "minimum": 1,
      "type": "integer"
    },
    "status": {
      "enum": [
        "scheduled",
        "running",
        "failed",
        "succeeded",
        "cancelled",
        "pending",
        "queued"
      ],
      "type": "string"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `enterprise_env_id`): this is a CoreStack or CoreCluster environment; name it by its
  `site_id` in the `corestack_deployments_*` tools. Field `cursor`: that page does not exist; list again from the start.
- `tenant_mismatch`: no environment with that id is yours (or a client's of your agency).
- `pin_refused`: a token limited to some sites cannot reach a CoreStack Enterprise environment; the person can widen it
  to everything in the company.
- The refusals every tool can answer: `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_deployments_list",
  "arguments": {
    "enterprise_env_id": 1530,
    "status": "failed",
    "limit": 10
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_deployments_list with enterprise_env_id 1530, status failed, limit 10. (CoreStack Enterprise deployments.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Deployments and pipelines](https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md)
