---
title: "corestack_error_pages_copy"
url: https://docs.corefinity.com/mcp/tools/corestack_error_pages_copy
type: tool
last_updated: 2026-11-13
feature: error-pages
related:
  - https://docs.corefinity.com/api/reference/site-settings/copy-site-error-pages.md
  - https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md
---
# corestack_error_pages_copy

**Copy error pages from another environment.** Copies another environment's error pages onto this one (its version from corestack_error_pages_get). Onto production needs confirm_production. Scope: write. Long-running: answers with a task.

- Scope: `write`
- Confirmation: `confirm_production`
- Runs as a task: yes

## When to use it

Copy another environment's error pages onto this one: the codes, every page with its message, and the support email. Call it on the environment that changes (`site_id`), name the one to copy from (`from_site_id`), and send this environment's `version` from `corestack_error_pages_get`. To promote staging's pages to production, call it on the production row with `confirm_production: true`.

The copy is a new revision on this environment and is applied exactly like `corestack_error_pages_update`: the same task, the same `error_pages` outcome in its result and the same refusals. The environment copied from does not change. Pages that are already the same answer `{operation: null, revision: null}`.

## Inputs

- `site_id` (integer, ≥ 1, required): the environment that changes.
- `from_site_id` (integer, ≥ 1, required): the environment to copy from. A token limited to some sites must cover both.
- `version` (integer, ≥ 0, required): this environment's version from `corestack_error_pages_get`.
- `note` (string, at most 200 characters): why, shown in the history.
- `confirm_production` (boolean): required (true) when this environment is production.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "confirm_production": {
      "description": "Required (true) when this environment is production.",
      "type": "boolean"
    },
    "from_site_id": {
      "description": "The environment to copy from.",
      "minimum": 1,
      "type": "integer"
    },
    "note": {
      "description": "Shown in the history.",
      "maxLength": 200,
      "type": "string"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    },
    "version": {
      "minimum": 0,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "from_site_id",
    "version"
  ],
  "type": "object"
}
```

## Refusals

- `confirm`: this environment is production; send `confirm_production: true`.
- `stale`: someone changed this environment's pages since `version` was read.
- `error_pages_locked`: Corefinity has locked this environment's error pages.
- `invalid_page`, `overlap_nginx_rules`, `too_large`, `runtime_lacks_capability`, `operation_in_progress`, `switch_reconcile_failed`, `managed_elsewhere`: as `corestack_error_pages_update`.
- `feature_off`: error pages are not available to you yet.
- 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_error_pages_copy",
  "arguments": {
    "site_id": 4211,
    "from_site_id": 4212,
    "version": 2,
    "confirm_production": true,
    "note": "Promote the staging pages"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_error_pages_copy with site_id 4211, from_site_id 4212, version 2, note Promote the staging pages. (Copy error pages from another environment.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [POST /api/corestack/sites/{site}/error-pages/copy](https://docs.corefinity.com/api/reference/site-settings/copy-site-error-pages.md)
- Guide: [Error pages](https://docs.corefinity.com/guides/sites/site-settings/error-and-maintenance-pages.md)
