---
title: "corestack_deployments_get"
url: https://docs.corefinity.com/mcp/tools/corestack_deployments_get
type: tool
last_updated: 2026-11-13
feature: deployments
related:
  - https://docs.corefinity.com/api/reference/deployments/get-site-deployments.md
  - https://docs.corefinity.com/guides/sites/code-and-deployments/connect-a-repository.md
---
# corestack_deployments_get

**Deployments.** A row's deployment settings — manual uploads or Git, the repository and branch — and its recent deployments with their status. Scope: read.

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

## When to use it

A row's deployment settings (manual uploads or Git, the repository and branch, and on a WordPress site what the repository holds: `contents`, `target_path`, `effective_target_path`, with `repository_options`) and its recent deployments with their status. A failed deployment's `error` is the line the Control Panel shows, for example why a first Git deployment stopped before the switch: a shared path the live release and the shared folder hold differently (in counts), or a Bedrock release that cannot reach its database.

Each deployment row's `ref` names its branch and commit; a deployment started by a git push also carries `git_commit_url`, `git_author` {`name`, `avatar_url`} and `git_merge_request` {`ref` (`!12` GitLab, `#12` GitHub or Bitbucket), `kind`, `url`}: what the push said about that commit, each null when it did not say. A link is only ever an https address on the repository's provider.

`releases.previous` is the release Roll back offers (`corestack_deployment_rollback`). With `before_git: true` (and `deployed_at` null) it is the site's files from before its first Git deployment, offered when no earlier deployment's release can be rolled back to.

What your role may change is answered per person, each `{available, reason}` where `reason` is the sentence the write would refuse with (the permission and who can grant it): `can_change_repository` (`corestack_deployments_repository_set`), `can_change_mode` (`corestack_deployments_mode_set`), `can_turn_on_auto_deploy` and `can_turn_off_auto_deploy` (deploy on push, set with the repository), `can_switch_to_git` (the mode set to `git`, which also needs Create Deployments when it would turn automatic deploys back on), and `can_stop_deployments` and `can_retry_deployments` (`corestack_deployment_stop` and `corestack_deployment_retry`; a deployment's own `can_stop` and `can_retry` say only whether its state allows it).

A failed deployment that switched maintenance mode on and failed before switching it off has `maintenance_lift`
{`state`, `message`}: `switching_off` (it is being switched off automatically), `switched_off`, or `not_switched_off`
(Corefinity has been alerted); `message` is the sentence its page shows. Every other row has `maintenance_lift: null`.
Only the deployment that switched maintenance on ever switches it off this way.

A failed deployment whose crons and queues stay paused has `crons_paused` {`state`, `message`}: `database_failed` (a
database command failed: they stay paused until `corestack_deployment_stop` or `corestack_deployment_retry` reverts the
deployment; its `can_stop` is then true unless another deployment of the site is still running) or `revert_unfinished`
(a Stop or Retry did not finish reverting it: on a failed deployment whose `can_retry` is true Retry runs it again;
otherwise, a stopped deployment included, Corefinity releases them). `message` is the sentence its page shows. Every
other row has `crons_paused: null`, including while a Stop or Retry is still reverting it.

## Inputs

- `site_id` (integer, ≥ 1, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "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_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_deployments_get with site_id 4211. (Deployments.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/deployments](https://docs.corefinity.com/api/reference/deployments/get-site-deployments.md)
- Guide: [Connect a repository](https://docs.corefinity.com/guides/sites/code-and-deployments/connect-a-repository.md)
