---
title: "corestack_site_restore_deleted"
url: https://docs.corefinity.com/mcp/tools/corestack_site_restore_deleted
type: tool
last_updated: 2026-11-13
feature: restore-deleted
related:
  - https://docs.corefinity.com/api/reference/sites/restore-deleted-site.md
---
# corestack_site_restore_deleted

**Restore a deleted site.** Bring back a site deleted with corestack_site_delete while it is still in its grace period. Scope: write.

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

## When to use it

Bring back a site deleted with corestack_site_delete while it is still in its grace period.

## Inputs

- `site_id` (integer, ≥ 1, required): The deleted site's id (its production row).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "description": "The deleted site's id (its production row).",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `not_restorable`: only a production row in its grace period can be restored. A site deleted while its create was still waiting for a tested version was never set up, so there is nothing to restore (message: "This site was deleted before it was set up, so there is nothing to restore. You can create it again.").
- `provisioning`: the site is still being created; wait for corestack_site_provisioning_get to finish.
- `capacity_blocked`: the site's CoreCluster has no room for it now (a deleted site stops counting against the cluster's disk once its deletion has finished, so the room may have been used since). Restoring it is checked as creating it would be: with automatic upgrades on (corestack_company_auto_upgrades_get), the CoreCluster first grows within the company's monthly limit; otherwise, or over the limit, the message says what is short. Free some room or upgrade the package (corecluster_upgrade_options_get), then try again. Nothing was restored.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done.
- `rate_limited`: the person has restored as many deleted sites this minute as the limit allows (10 by default, shared with the Control Panel and the API; deleting sites never uses it up). A restore that is refused does not count. Wait `retry_after_seconds`, then call again.
- 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_site_restore_deleted",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_site_restore_deleted with site_id 4211. (Restore a deleted site.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/restore-deleted](https://docs.corefinity.com/api/reference/sites/restore-deleted-site.md)
