Send the finished work.
Ask your agent to email a progress update or a summary when its work is ready.
“Email this project summary to my teammate.”See the sending example →
A real inbox.
For your agents.
On your server.
Give your agent an email address on your own domain. Read, reply and send through MCP or API—with mail and access under your control.
How your agent sets it up →Loading prompt…
Read the setup prompt
Open text version ↗Your agent handles setup. You provide access and make the decisions.
[email protected]Your agent has an address.
Give it an inbox.
Then just ask.
Once connected, use your agent’s chat to send a message, catch up on mail or reply to a conversation.
You ask. Your agent acts.
Send an email to [email protected]. Subject: “Weekly update”. Body: “The report is ready for your review.”
The mail server accepted your email for sending. Recipient delivery is not yet confirmed.
Email submitted
Submitted to SMTP- Subject
- Weekly update
Submission confirms the server accepted the message. Confirm receipt separately.
Bring the agent
you already use.
Choose your app for its MCP configuration and a setup prompt you can copy. Keep using the chat you know.
CodexConnect through MCP
Claude CodeConnect through MCP
Claude DesktopConnect through MCP
CursorConnect through MCP
GrokConnect through MCP
OpenCodeConnect through MCP
Already have a running server? Connect an inbox directly. New to Hermesaki? Let your agent set it up first →
A useful address.
For real work.
Catch up on incoming mail.
Have your agent read messages and their attachments, then pull out what needs your attention.
“Read my latest emails and summarize the action items.”See the reading example →
Keep the conversation going.
Choose a message and tell your agent what to reply. Responses preserve the conversation’s email headers.
“Reply to Alex: Thursday at 2 pm works for me.”See the reply example →
Your agent interprets the request. Hermesaki provides the mailbox tools and enforces its access permissions.
Your agent sets it up.
You stay in control.
Share a few details, follow the progress, and step in when your agent needs you.
Your part
A working setup.
An honest baseline.
We measured a complete agent-assisted reinstall on 12 September 2026. Email worked end to end. Setup took longer than it should.
- Setup + full verification
- 58m 16s
- Including teardown + cleanup
- 1h 09m 34s
- Human approval questions
- 2 questions
Includes troubleshooting and overlapping DNS waits.
The full measured execution window.
Resolved in one response. Supervisor assistance was also needed.
Verified: native Codex MCP send, read and reply; actual Gmail receipt; SPF, DKIM and DMARC passed. All 11 setup checks passed.
Next target: configure in under 10 minutes with required inputs and access ready. DNS waiting will be reported separately. This target has not been demonstrated.
One assisted application reinstall on an existing VPS with cached dependencies and signed-in provider sessions. Not a blank-server benchmark or a typical-time guarantee.
A familiar mail stack. An agent-friendly interface.
StalwartMail serverRoundcubeWebmailMCP + RESTAgent access
One connection.
Useful mail tools.
Your agent can list folders, search messages, read attachments and reply. Give it read-only access, or explicitly allow sending.
Read the API reference →Connect your MCP clientJSON
{
"url": "https://your-server.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_MAILBOX_KEY"
}
}Streamable HTTP · Add Cloudflare service headers when Access is enabled. Get the complete configuration from Agent access.
Your mail deserves a home.
Hermesaki brings the pieces together. You provide the server and domain, and remain responsible for running them.
Mail stays with you.
Messages and attachments live in Stalwart. Hermesaki adds the API, mailbox credentials, send queue and operator dashboard.
Access is explicit.
Separate mailbox keys from operator access. Choose permissions, set expiry and revoke an agent’s key when its work is done.
Configuration in context.
Review supported DNS, tunnel and access-policy changes before applying them. Keep your webmail address alongside your server settings.
Know what you’re
bringing.
Your agent handles the configuration. You choose the infrastructure and stay in charge of the accounts.
A domain and an address
Choose where your mail lives, such as [email protected]. Your agent checks existing mail routing before proposing DNS changes.
A suitable Linux server
Use a VPS with working mail ports and reverse DNS. Your agent checks the requirements; some providers need to enable SMTP first.
Access to your providers
Share your server access. With a supported browser connection, sign in to Cloudflare and your VPS provider so your agent can help configure them.
A few things
you might be wondering.
Can I use a server I already have?
Yes, if it meets the mail server requirements and has enough available resources. The setup prompt tells your agent to inspect existing services and check for conflicts before making changes. See what to prepare →
Will this replace my existing email?
It depends on the domain you choose. Changing a domain’s MX records changes where its incoming mail goes. Your agent should review existing routing and ask before changing it. A separate domain or subdomain can keep the new mail service separate.
Can I open the inbox myself?
Yes. Roundcube gives you a browser inbox where you can read and reply yourself. Its mailbox password is separate from the scoped key your agent uses.
Can an agent read mail without permission to send?
Yes. Give it read-only access, or explicitly add sending permission. Keys are scoped to an inbox and can expire or be revoked from the dashboard.
Will email always arrive in the recipient’s inbox?
Inbox placement is not guaranteed. Domain authentication, server reputation and recipient filters all matter. During setup, verify sending and receiving with an external inbox, and check Spam or Junk too. “Submitted” means the mail server accepted a message; it does not prove recipient delivery.
Does my agent automatically respond to every email?
No. Connecting MCP makes mailbox tools available when your agent uses them. Automatic monitoring and replies need an agent workflow and an explicit policy. Treat incoming email as untrusted content, and grant only the permissions that workflow needs.
What will I have to do during setup?
Choose your address and server, provide access, and handle sign-in codes or account approvals. Your agent pauses for purchases or changes to existing mail routing. At the end, confirm a test email and reply so it can verify both directions.
A little messenger.
A server you control.
Give your agent the setup prompt. It will guide you from account access to a working inbox.