Ringmaster Sign in Get started

Lifecycle email your agent runs.

Your app sends events. Your agent designs the flows, segments and campaigns over MCP. Ringmaster sends each email and text once, in the recipient's daytime, and never past an unsubscribe. Texts go from your own Twilio number.

$300 a month, flat. Cancel any time.

Running lifecycle email for

Your agent connects from any MCP client

  • Claude
  • ChatGPT
  • Claude Code
  • Cursor

Add it as a custom connector, then sign in: https://app.rngmstr.dev/api/mcp

How it works

  1. 1

    Your app sends events

    One REST call per event, with an Idempotency-Key, so a retry never counts twice. Each event creates or updates the person it is about.

  2. 2

    You ask your agent for the flow

    Describe the emails in plain words. Your agent writes the flow. Ringmaster refuses a misspelt merge field or an unverified domain before it saves, and you confirm before it mails anyone.

  3. 3

    Ringmaster sends it

    Each step waits for the recipient's daytime, skips people who already did the thing, and stops as soon as their consent does.

Rules your agent can't break

They live in the server, so they hold whatever a prompt says.

Nobody gets a message twice
Each email and text is recorded before it goes out, so a crash or a retry never sends it again.
An unsubscribe is final
Every email carries a one-click unsubscribe link and header, and consent is checked again before every send. A bounce or complaint stops all mail to that address, and a reply of STOP stops every text to that number.
Nothing lands at 3am
Delays move into 08:00 to 20:00 in the recipient's time zone, taken from their profile or their country.
A person says go
Activating a flow, sending a campaign and suppressing an address wait for a yes in your agent's client. Scheduling a campaign is a dry run until you execute it.
Bad sending stops itself
When bounces or complaints climb, a circuit breaker pauses your sending until we have looked. A monthly cap sits under every account.
Deleting a person deletes them
One API call erases a profile and everything stored about them, sends and events included.

What your agent can do

Connect your agent and ask for what you want in plain words. It works with the same flows, settings and results you see in the dashboard.

Write your flows
Describe the emails and texts. Your agent writes the flow, sends you a test email, and turns it on once you say yes.
Run a campaign
Pick who gets it, see who matches, and do a dry run that counts recipients before anyone is mailed.
Keep consent straight
Set up topics, find out why someone isn't getting messages, and tell your app when they unsubscribe.
Set up sending
Add your domain, check its DNS records and your Twilio number's setup, and design the layout every email shares.
Read the results
Opens, clicks, unsubscribes and conversions for every step, and where each person is in each flow.
Look after the account
See your plan, members and audit log, and open billing.

One plan. $300 a month.

Sign up, add your company, pay, connect your sending domain and your agent, and send your first event. It takes one sitting, and the domain is one click where your DNS host supports Domain Connect.

US dollars, billed monthly through Stripe. Tax may apply.