Your agent has no address of its own.
It signs your name from your inbox, or it can send but never read the reply.
Give Codex a real inbox. On your server.
Your agent gets an address on your domain. It reads, sends and replies through MCP, with keys that you scope and revoke. The mail is stored on your server.
Self-hosted. You pay your domain and server providers directly. Your agent does the setup; you give access and make the decisions.
Scripted preview with sample data. No email is sent. The guide has the exact configuration for each app.
Agents need email.
Email was not built for them.
Most agents borrow your personal inbox or get a send-only API. Neither gives an agent its own address, its own limits and a home that you control.
One connection can do everything.
A mailbox login lets an agent read, send and delete. You cannot give it less.
Your mail lives in another company's service.
Messages, logs and limits sit with a provider that you do not run.
A real address.
Read, send and reply.
Mail to [email protected] arrives in a real mailbox. Your agent reads it, replies in the same thread and checks the send status. You open the same inbox in webmail.
- Replies stay in the threadThe reply keeps the headers of the original message.
- Attachments are readableYour agent can read messages and their attachments.
- Honest send status"Submitted" means the mail server accepted it. It does not claim delivery.
Sample addresses. The messenger shows where each message goes.
You choose what
each agent can do.
Each key opens one mailbox. Give it read only, or allow sending too. Set an expiry, and revoke the key when the work is done.
- Read only stays read onlyA read-only key gets
scope_deniedwhen it tries to send. - Mail is untrusted inputText in an email cannot give an agent more permissions.
- Nothing sends by itselfIncoming mail creates a draft. It sends only after an explicit approval.
A redraw of Agent access in the Hermesaki dashboard, with sample keys.
Your server. Your domain.
Your mail.
Stalwart stores and delivers the mail. Roundcube is the inbox for people. Hermesaki adds the API, MCP, the send queue and the dashboard, on a Linux server that you run.
- Mail stays in StalwartMessages and attachments stay in your mail server.
- No bodies in the dashboardIt shows delivery state, attempts and audit history only.
- Encrypted where it waitsQueued messages, mailbox credentials and backups are encrypted.
A typical production setup. Cloudflare Access protects browser and MCP traffic; mail uses SMTP.
Everything a mailbox
needs to work for an agent.
One install. Each part has one job, and each part is in the product today.
Mailbox
StalwartReal IMAP folders on your domain. Create an inbox for each agent from the dashboard.
MCP and API
ConnectOne MCP endpoint, a REST API, a TypeScript SDK and a CLI share one permission layer.
MCPRESTSDKCLI
Agent access
AccessKeys for one mailbox, with permissions, an expiry and a Revoke button.
Read onlyRead and send
Webmail
RoundcubeRead and reply yourself in the browser. The Classify plugin can label mail with coloured chips when you add a TypeSafe API key.
Send queue
DeliveryA retry with the same idempotency key returns the same job, not a second email. Queued mail is encrypted.
queuedsubmitteduncertain
Drafts
AccessIncoming mail creates a draft. A draft sends only after an explicit approval.
Needs approval
Webhooks
ConnectSigned events for new mail and send results. Failed deliveries show in the dashboard for replay.
SignedReplay
Dashboard
ServerInboxes, agent access, delivery state and audit history, without message bodies.
Backups
ServerEncrypted snapshots. Restore a complete snapshot into another stack to test it.
EncryptedRestore test
Give it an inbox.
Then just ask.
Your agent understands the request. Hermesaki gives it the mailbox tools and enforces the key's permissions.
Bring the agent
you already use.
Choose your app for its MCP configuration and a setup prompt that you can copy. Keep the chat that you know.
Already have a running server? Connect an inbox directly. New to Hermesaki? Let your agent set it up first.
Own the mailbox.
Scope the agent.
Comparison research is in progress.
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 guides you from account access to a working inbox.