---
title: "corecluster_progress_get"
url: https://docs.corefinity.com/mcp/tools/corecluster_progress_get
type: tool
last_updated: 2026-11-13
feature: cluster-create
related:
  - https://docs.corefinity.com/api/reference/corecluster/get-cluster-progress.md
  - https://docs.corefinity.com/guides/corecluster/create-a-cluster.md
---
# corecluster_progress_get

**CoreCluster creation progress.** How far the creation of a CoreCluster (and its first sites) has got, step by step. Scope: read.

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

## When to use it

How far the creation of a CoreCluster (and its first sites) has got, step by step.

`retrying` is null, or the step the create is trying again on its own after a temporary problem, instead of failing: `stage` (the stage it is on), `attempt`, `attempts` (null when the wait is bounded by time only), `since`, `next_attempt_at` and `message` — "Setting up your cluster is taking longer than usual. We are trying again automatically." before the cluster is saved, "Publishing your cluster's SSH address is taking longer than usual. We are trying again automatically." at the SSH address. The same sentence is that stage's `detail`, and corecluster_operation_get's note `cluster_create_retrying`. Keep polling: `failed` is set only once the create has stopped.

When a step after the cluster was saved fails on a temporary problem (the platform slow to pick up or ready the cluster's capacity, or its SSH address not published in time), the cluster is set up again on its own a few minutes later, with the same name and its first sites carried over: `failed` stays null, the stage reads `current`, and `retrying` gives the attempt, `attempts`, `since` (when the step failed), `next_attempt_at` (when it is set up again) and the message "Setting up your cluster is taking longer than usual. We are setting it up again automatically." — the same while the new attempt runs. The cluster reads `creating` meanwhile. Keep polling; do not create the cluster again. Only when the automatic attempts are used up does `failed` appear.

## Inputs

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

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "cluster_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "cluster_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": "corecluster_progress_get",
  "arguments": {
    "cluster_id": 812
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corecluster_progress_get with cluster_id 812. (CoreCluster creation progress.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/clusters/{cluster}/progress](https://docs.corefinity.com/api/reference/corecluster/get-cluster-progress.md)
- Guide: [Create a cluster](https://docs.corefinity.com/guides/corecluster/create-a-cluster.md)
