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

**CoreStack Enterprise deployment settings.** A CoreStack Enterprise environment's deployment settings: pipeline on or off, deployment source, whether git pushes deploy automatically, and each pipeline's folders. Scope: read.

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

## When to use it

Read how a CoreStack Enterprise environment deploys, as its environment page's Deployments tab shows it: whether the
deployment pipeline is on, the deployment source (`manual` or `git`; `sftp` only on an environment still set to it),
the sources it may be changed to, whether git pushes deploy automatically (`git_deploys`, null unless the source is git),
how many repositories it has, and its pipelines: each with `pipeline_id`, `name`, its web folder (`root_directory`), its
storage folder (`root_storage`) and `folders_editable` (whether the person may change that pipeline's folders), and its
build switches: `pause_crons_during_build` and `isolate_build_var` (null where a switch does not apply to that pipeline),
`build_switches_editable`, and `notes` (what the switches change for that pipeline's build commands). Read it
before `corestack_enterprise_deployment_settings_update`.

The public API's `GET /api/environments/{environment}/deployment-settings` answers the same.

## Inputs

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

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments` (field `enterprise_env_id`): a CoreStack or CoreCluster environment; use the
  `corestack_deployments_*` tools by `site_id`.
- `tenant_mismatch`, `pin_refused`, and 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_deployment_settings_get",
  "arguments": {
    "enterprise_env_id": 1530
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_deployment_settings_get with enterprise_env_id 1530. (CoreStack Enterprise deployment settings.) Tell me what it returned.
```

## The same task elsewhere

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