---
title: "corestack_email_get"
url: https://docs.corefinity.com/mcp/tools/corestack_email_get
type: tool
last_updated: 2026-11-13
feature: email
related:
  - https://docs.corefinity.com/api/reference/site-settings/get-site-email.md
  - https://docs.corefinity.com/guides/sites/site-settings/outbound-email.md
---
# corestack_email_get

**Read a site's email sending.** Read how a row sends email: whether a sending domain is set up and verified, the DNS records it needs and which are found, the sender, and whether a test email can be sent. Scope: read.

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

## When to use it

Read how a row sends email: whether a sending domain is set up and verified, the DNS records it needs and which are found, the sender, and whether a test email can be sent.

The top level is the default sending domain. `domains[]` lists every sending domain of the row, the default first: its `state`, the From domain it carries (`from_domain`), whether the site sends through it yet (`active`), its records and Cloudflare zone, its last test, its newest email change (`operation_id`: follow it with corestack_site_operation_get), and what can be done with it (`can_test`, `can_rotate`, `can_make_default`, `can_remove`, each with its reason when it cannot). `add` says whether another sending domain can be added (`corestack_email_domain_add`) and why not. On a Magento 2 row, `store_mapping` lists each store, the From addresses it sends as, and the sending domain each goes through (`via`: `own`, `pending` until the new domain verifies, or `default`; `warn`: `no_domain` when no sending domain matches its From domain, `capitals` when the address has capitals in its domain); it is read from Magento in the background and is null until the first read answers.

On a preview row (a staging or development environment, or a site with no domain attached yet) `mailpit` says where its mail is caught: `url`, `catches` and `note`. `catches` is `all`, or `php_mail` on a WordPress site whose platform plugins are turned off: then only email sent with PHP mail is caught, an SMTP plugin with its own live credentials can send real email, and `note` says so in the person's words (`corestack_site_platform_plugins_get` shows the setting). On a staging or development environment `role_held` is the sentence `corestack_email_enable` is refused with there.

## Inputs

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

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "site_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `deleted`: the site is deleted (in its grace period); restore it with corestack_site_restore_deleted first.
- `provisioning`: the site is still being created; wait for corestack_site_provisioning_get to finish.
- 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_email_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_email_get with site_id 4211. (Read a site's email sending.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/email](https://docs.corefinity.com/api/reference/site-settings/get-site-email.md)
- Guide: [Outbound email](https://docs.corefinity.com/guides/sites/site-settings/outbound-email.md)
