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

**Read an environment's error pages.** Reads an environment's error and maintenance pages and settings, the version every change needs and any lock. Scope: read.

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

## When to use it

Read an environment's error and maintenance pages before changing them. The answer is the Control Panel's own: for each status code (404, 500, 502, 503, 504) whether visitors get the error page (`page`) or the app's own response (`app`), each page's message, the support email, the `version` every change needs, and whether Corefinity has locked the pages.

`available` is false while the environment cannot have its own error pages yet; `unavailable_reason` says why (`runtime`: after the site's next platform update; `varnish`: the Varnish part of that update; `cse`: not offered for this kind of site). `pages[]` summarises each page: `state` is `platform` (our page), `custom` (your HTML) or `app` (the app's own response), with its size in bytes and how many warnings it has. `operation` is the change being applied now, if any. `locked` is set while Corefinity has locked the pages: you can read and preview them, but not change them.

Each page's HTML is left out unless you set `include_sources`, because a page can be up to 64 KiB.

The defaults: 500, 502, 503 and 504 show the error page and 404 shows the app's own response. When the app answers a request to an API path (for example `/rest/`, `/graphql`, `/wp-json/`) or one asking for JSON, its response always passes through, whatever the settings; an error the web server answers itself on such a request (PHP not running, a request over 300 seconds) follows the settings.

## Inputs

- `site_id` (integer, ≥ 1, required): the environment row.
- `include_sources` (boolean): include each page's HTML source. Default false.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "include_sources": {
      "description": "Include each page's HTML.",
      "type": "boolean"
    },
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `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_get",
  "arguments": {
    "site_id": 4211,
    "include_sources": true
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_error_pages_get with site_id 4211, include_sources true. (Read an environment's error pages.) Tell me what it returned.
```

## The same task elsewhere

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