Skip to content
MCP Chats

Email / Finish the work. And the follow-up.

The work is done.
You’re still writing the update.

Your agent finishes the research. You copy the result, rewrite the message and find the recipient. Again.

Make the follow-up part of the process. Publish the wording once; your agent fills in the details and sends it from the step you allow.

Join the waitlistFill the fields below ↓

Try it: turn a finished research brief into an update.

Your wording → Agent supplies details → Send recorded

You write / Published template

v1

Research ready

Subject: Your research on {topic} is ready

Hi {name},

The brief on {topic} has been reviewed. The findings and source links are ready for you.

Thanks for reading.

Your agent supplies / Required fields

They receive / Live preview

Your research on AI coding tools is ready

Hi Sam,

The brief on AI coding tools has been reviewed. The findings and source links are ready for you.

Thanks for reading.

Same wording. Your values fill the fields.

Example limits: example.com · 1 recipient · “Tell the reader” step

Fill the fields. The preview updates; the published wording stays the same.

Interactive illustration · No email is sent.

Reading roundup

Illustrative template

Hi reader name,

Your roundup for week ending:

Repeat for each reading item

title — summary

source link

Only if a follow-up is needed

Next to explore: follow-up topic.

No more rebuilding the message

A longer list shouldn’t mean another rewrite.

A roundup can have two items or twenty. Some need a follow-up; others don’t. Keep your voice while the template makes room for what changed.

The right details, in the right format

Names, dates and numbers fill the fields you define. Set the format for currencies and percentages once.

Every item gets its place

Repeat a section for each reading item, line item or table row. No copying the same block over and over.

Skip the paragraph that doesn’t apply

Include the follow-up section only when it is needed.

“Did the update go out?” shouldn’t become another task.

Keep the send record with the work: the template used, the recipients and the outcome. Require that record before the step can finish, so the follow-up isn’t left to memory.

Share the research brief

Send recorded
Published template
Research update · v1
Recipient
reader@example.com

  1. Required details checked

    Fields, allowed step and configured recipient limits.

  2. Message sent; record kept in the run

    The follow-up stays attached to the work.

  3. Same send retried

    Existing record returned. No second email.

Illustrative run record · A send record does not prove delivery. Delivery reports are recorded when enabled.

Before you build

Who writes and publishes the template?
You can use the rich editor or ask your agent to draft a template. Publishing requires someone with publishing rights, or their full-access agent. Templates are versioned; attached processes keep their chosen version until updated. Number fields support currency and percent formats. The editor includes starter templates and previews with sample data.
What does MCP Chats check before a send?
It checks the published template, allowed process step, required field types and values, recipient domains and maximum recipient count. Missing or invalid data is refused. Allowed domains can be restricted or left open: the default is any address, with a warning when publishing. The example above deliberately allows only example.com.
How do retries and uncertain sends work?
The email is recorded before sending, so retrying the same send does not send it twice. If the outcome is unclear, MCP Chats checks with the mail provider; an operator resolves anything still uncertain. A step can require the email send record as evidence. Delivery reports are recorded when enabled; a send record alone does not prove delivery.
Can I try a process without emailing anyone?
Yes. Test runs record the message they would have sent and never send a real email. The interactive example on this page is also local to the website and sends nothing.

Current pilot limits. Messages currently use our sending domain. Sending from your own domain and handling replies to agent-sent messages are not available yet.

Connect the rest of the process

ProcessesBuild a routine around your way of working.Your MCP serverYour context and tools in the agents you use.ApprovalsPause for a person’s review where you choose.

Include the update you always send afterwards.

Join the waitlist with one recurring job in mind. When invited, we’ll help you build the process and try it with your agent. Work solo or with a team; the pilot is free.

Join the waitlist