MCP Reference

Send & Retain is MCP-first — an agent runs the whole product through email_* tools. Every tool, with schemas, so you can call them directly.

Send & Retain is MCP-first. The primary way to drive it is the email_* MCP tools — the same tools the in-app copilot uses. An agent can stand up a company's entire email stack and operate it in natural language: connect a provider, verify a domain, author and translate templates, send transactional mail, build event-triggered automations, and read the metrics — without a human clicking through a dashboard.

This reference lists every tool with its full parameter schema, grouped by domain, so an agent (or you) can discover and call them directly. For connecting a client and tokens, see Connecting; for the safety model, Guardrails.

Why choose the Send & Retain MCP

One surface for the whole lifecycle

Send, templates, contacts, events, automations, suppressions, and analytics — one connected toolset, not a send-only API.

Schemas an agent can trust

Every tool is typed and validated; this reference is generated from the real tool definitions, so it never drifts from what the server accepts.

Safe by construction

No blast sends, per-project kill switch + daily cap, and read/write scopes — an agent can't accidentally torch a domain.

Same tools as the dashboard

Anything the operator UI or in-app copilot can do, an MCP client can do — one code path, no second-class API.

Read vs write

Each tool page carries a badge:

  • read — safe, idempotent reads (carries readOnlyHint over MCP).
  • write — changes state or sends mail (carries destructiveHint). A read-scoped token only exposes the read tools.

Tool domains

From zero to running, in one command

The fastest path: point an agent at a company and let it bootstrap the whole setup. email_bootstrap_company materializes the starter templates and lifecycle sequences for a business archetype (SaaS, e-commerce, newsletter/media, marketplace) — welcome, cart recovery, trial conversion, win-back — all created paused, so nothing sends until a human enables it. Then email_get_optimization_plan is the ranked "what to fix next" feed as real sends accumulate.

On this page