> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendrealm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard MCP

> Use the Sendrealm MCP server to work with dashboard resources through an API key.

The Sendrealm MCP endpoint is available at:

```text theme={null}
https://mcp.sendrealm.com/mcp
```

Connect with a SendRealm API key through the `Authorization` header:

```text theme={null}
Authorization: Bearer your_sendrealm_api_key
```

The server is API-key scoped and does not persist credentials.

## MCP Features

| Area            | Available capabilities                                                                                                                                   |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Project         | Inspect the project and capabilities assigned to the API key.                                                                                            |
| Domains         | List domains and inspect verification state, DNS records, sending settings, and tracking settings without refreshing or mutating provider state.         |
| Audiences       | Create, list, retrieve, and update audiences and audience properties.                                                                                    |
| Contacts        | Create, list, retrieve, and update contacts; look up or upsert by email; attach or remove audience membership; update topic subscriptions.               |
| Topics          | Create, list, retrieve, and update subscription topics.                                                                                                  |
| Templates       | List and retrieve dashboard-authored email or push templates and inspect version history.                                                                |
| Automations     | Create and edit drafts, validate definitions, inspect runs, cancel or retry eligible runs, and test drafts with synthetic events and virtual time.       |
| Events          | Ingest customer events with contact resolution, idempotency, and optional correlation data.                                                              |
| Email campaigns | Create, list, retrieve, and update email campaign drafts and inspect readiness and delivery summaries.                                                   |
| Push apps       | Create, list, retrieve, and rename push apps; inspect redacted FCM, APNs, and Web Push readiness and notification channels.                              |
| Push devices    | Find registered devices and inspect permission, subscription, SDK, environment, activity, and provider-error diagnostics without exposing device tokens. |
| Push delivery   | List push notification records and inspect provider and client event timelines.                                                                          |
| Push campaigns  | Create, list, retrieve, and update drafts and preview reachable devices by platform.                                                                     |
| Push tests      | Send one real test to one explicitly selected device, poll its delivery trace, and start, update, or end a single-device Live Activity test.             |

## Not Exposed Through MCP

* Email or push campaign scheduling and production launch.
* Broad direct email or push sends.
* Push provider credential upload or replacement.
* Domain creation, transfer, deletion, or settings changes.
* Campaign deletion, asset uploads, and email campaign test sends.
* Template authoring, publishing, restoring, and archiving.

These operations require an explicit human handoff to the SendRealm dashboard or
trusted backend code using the public API.

For recovery workflows, agents should use contact lookup/upsert, put a stable
business identifier in event correlation, validate the automation, and run the
draft through the no-send test-run tools before publishing. Live run cancellation
and retry are explicit, audited operations; campaign scheduling and sending stay
in the dashboard.

Campaign scheduling and sending are intentionally unavailable through MCP. Agents should complete the draft, inspect readiness, and leave final scheduling and delivery approval to the SendRealm dashboard.

For push integration testing, agents can inspect provider readiness, find a
registered device, send one explicit test, and poll its provider/client event
trace. MCP does not expose broad direct push sends. Provider credential upload
and campaign launch stay in the dashboard.