Make room for
your messenger.
Tell your agent which email address you want. It handles installation, configuration and testing, and asks when it needs your help.
Let your agent set it up.
Copy the prompt into your agent. It will help connect your server and domain, create your mailbox, and test sending and receiving.
Have your server and Cloudflare accounts ready. Your agent will ask for anything else it needs.
Read the setup prompt
Using Codex? Open your provider accounts.
With browser or Computer Use enabled in your Codex desktop setup, your agent can work through the provider websites for you.
- Open Cloudflare ↗ and your server provider, such as Hetzner Console ↗, in the browser connected to your agent.
- Sign in yourself, then share or mention those tabs and tell your agent which domain and server to use.
- Paste the setup prompt. Your agent checks access, configures the installation and reports progress.
Stay available for sign-in codes, account approvals, purchase decisions and the test email. You do not need to copy every setting between websites yourself.
A tab in an unconnected browser is not automatically shared. If browser control is unavailable, your agent will guide you through the specific steps it needs.
Computer Use setup ↗ · Browser connection guide ↗Connect your agent securely.
Need the Cloudflare Client ID and Client Secret? Follow the screenshots, authorize your agent, and load the environment variables on your computer.
Cloudflare credentials and environment setup →Prefer to set it up yourself? View the technical guide.
01. Get the code.
Clone the repository, then open the project directory.
git clone https://github.com/Ansonhkg/hermesaki.git
cd hermesaki02. Run the local stack.
Build the mail server, webmail and Hermesaki API. Seed fictional accounts and messages so you can try the full flow.
make dev
make seedOpen the dashboard at http://localhost:19100 and webmail at http://localhost:19180. Create your administrator username and password on first sign-in, using the one-time code in .runtime/product/administrator-setup-code.
Local outgoing mail is captured in Mailpit. This environment does not send to external recipients.
03. Create an inbox and connect an agent.
In the dashboard, open Inboxes and create an address. Under Agent access, issue a mailbox key with read-only or sending permissions. Copy the complete MCP connection configuration into your client.
Open webmail to read messages yourself. Use Activity to inspect mail submissions, webhook attempts and audit history.
Read the MCP connection guide →04. Prepare your own mail server.
For real email, you need a Linux server, a domain you control, working SMTP connectivity, reverse DNS and valid TLS. Mail DNS includes MX, SPF, DKIM and DMARC records.
Use a separate production installation. Review the deployment guide for Cloudflare Access, tunnel routing, credentials and backups before changing DNS or enabling outbound delivery.
Read the deployment guide ↗The setup wizard helps configure the installation, but local tests and a running API do not prove public email deliverability. Validate sending and receiving on your own infrastructure.
Already running Hermesaki?
Your dashboard lives at the address configured on your own server. This website hosts the public guides only.
Get started ↗