Skip to main content
The Sendrealm MCP endpoint is available at:
Connect with a SendRealm API key through the Authorization header:
The server is API-key scoped and does not persist credentials.

MCP Features

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.