Every dashboard action is an MCP tool your agent can call.Read the docs

Email MCP server for any AI agent.

One URL gives your agent real email tools for domains, templates, automations, sends, and metrics. Sign in through the browser, no key to paste.

Start for free

✓Free to start. Unlimited contacts on every tier.

MCP session
Email MCP

Tools with product meaning

Operator prompt

Inspect the onboarding automation, explain where contacts stop, and show the evidence before proposing a change.

Read-only first task

Discover

email_* tools

Inspect

Company context

Propose

Controlled write

OAuth or a scoped API key

[ 01 / 06 ]Connect

How do I connect to the Send & Retain MCP server?

One command in Claude Code, then a browser sign-in. Other clients take the same URL.

  1. Add the server

    In Claude Code, run this in your terminal. No API key, no config file.

    Terminal
    claude mcp add --transport http sendandretain https://sendandretain.com/api/mcp
  2. Using another client? Use the URL

    Cursor, Codex, Gemini CLI, and VS Code take it in their MCP config. Claude adds it as a custom connector under Customize → Connectors, and ChatGPT as a developer-mode app.

    MCP server URL
    https://sendandretain.com/api/mcp
  3. Sign in through the browser

    The server uses OAuth 2.1, so your client opens a sign-in page. Approve once and it keeps the token.

  4. Check it works

    Ask: "List my Send & Retain projects." You should see your projects, or an offer to create one.

[ 02 / 06 ]Tools

What tools does the email MCP server have?

Every dashboard action is a tool, on the same core as the REST API.

Domains and senders

Create a domain, get the DNS records, verify it, and add a sender.

email_create_domain · email_verify_domain · email_create_sender

Templates

Write react.email templates, render them, test them, and publish.

email_create_template · email_render_template · email_publish_template_version

Automations

Build automations from product events. They're created paused.

email_create_automation · email_preview_automation · email_set_automation_status

Contacts and events

Add contacts, record events, and build segments.

email_upsert_contact · email_emit_contact_event · email_create_segment

Sending

Send one transactional email or a test, through the same checks as the API.

email_send_email · email_send_test_email

Metrics

Delivery, engagement, and trends by automation and template.

email_get_email_metrics · email_get_automation_metrics · email_get_metrics_trends

[ 03 / 06 ]Example prompts

What can you ask once it's connected?

Start read-only, then hand it a real change.

  • Audit

    “Check my sending setup and tell me what's misconfigured. Don't change anything.”

  • Domain

    “Set up sending for acme.com and give me the DNS records to add.”

  • Automation

    “Build a paused trial conversion automation that stops when subscription_started arrives.”

  • Diagnose

    “Why did this contact not get our welcome email? Check suppressions and the message log.”

[ 04 / 06 ]Access

Is it safe to give an agent email tools?

Yes. The sign-in says who is acting and what they can reach, and the risky checks sit on the action itself, not on the client that asked.

  • Browser sign-in acts as you, and is checked again on every call.
  • Unattended agents use a scoped API key, pinned to one project, that never auto-applies a change.
  • Revoking a key stops REST and MCP together. There's no second credential to forget.
  • Provider keys never travel over MCP. You paste them into the dashboard yourself.
  • Automations are created paused, and turning one on needs your confirmation.
Delivery checks
Pre-dispatch

Refuse unsafe sends first

Details

not yet sent

To[email protected]

From[email protected]

Templatewelcome

Sourceapi

ProviderSend & Retain

Checks before dispatch

  1. DomainSPF · DKIM · DMARC
  2. RecipientAddress verified
  3. SuppressionNo active block
  4. RouteProvider healthy
Controls run again at dispatch

[ 05 / 06 ]Which one?

MCP server or REST API?

Same core, same send checks. Pick by who's calling.

Who uses it

REST API

Your app's code

MCP server

Your AI agent

How it signs in

REST API

A scoped aem_ API key

MCP server

Browser sign-in, or a scoped key for unattended agents

What it can do

REST API

Sends, contacts, events, templates, automations, domains, and metrics

MCP server

The same core, as tools your agent picks for itself

Cost

REST API

Included on every tier

MCP server

Included on every tier. No AI credits used

Questions people ask us

Give your agent real email tools in one command.

Add the server, sign in through the browser, and ask for a read-only audit first.