---
title: "corestack_environment_list"
url: https://docs.corefinity.com/mcp/tools/corestack_environment_list
type: tool
last_updated: 2026-11-13
feature: environments
related:
  - https://docs.corefinity.com/api/reference/environments/list-site-environments.md
  - https://docs.corefinity.com/guides/sites/environments-and-copies/create-an-environment.md
---
# corestack_environment_list

**Environments.** A site's environments — production and its staging environments — with what each can be copied from and whether you can add another. Scope: read.

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

## When to use it

A site's environments — production and its staging environments — with what each can be copied from and whether you can add another.

`queued_copies` lists the copies waiting their turn onto these environments (a copy that would only have to wait is queued and starts on its own; see corestack_site_clone), each as `{id, state, reason, message, ahead, source, target, operation_id, queued_at, deadline_at, ended_at}`, with `message` in the queue's words ("Waiting for another copy on this site to finish. It starts on its own."). It shows the copies onto environments the person may change, however they were queued: in the Control Panel, through the public API or by an MCP client. Cancel one while it waits with corestack_queued_copy_cancel (`queued_id`: its `id`), however it was queued; a copy your grant queued can also be cancelled with its task (tasks/cancel, or corestack_task_cancel). `source` is null when the person may not see the environment it copies from (a copy from another site on the cluster), and `message` then calls it "the environment it copies from". With pins, a copy is listed only onto a covered environment, its `source` null (and out of `message`) when the source is outside them, a `site` pin included.

## Inputs

- `site_id` (integer, ≥ 1, required): Any row of the site: the site or one of its environments.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "description": "Any row of the site: the site or one of its environments.",
      "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_environment_list",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

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

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/environments](https://docs.corefinity.com/api/reference/environments/list-site-environments.md)
- Guide: [Create an environment](https://docs.corefinity.com/guides/sites/environments-and-copies/create-an-environment.md)
