Aduki Hermers

Mail infrastructure engineered for the machine age.

Email

Developer Tools

Artificial Intelligence

Visit WebsiteSee on Product HuntTwitter ⧉

👋 Hey Product Hunt, I'm Fredrick Femar from aduki, Inc. we build infrastructure and software, and Hermers grew out of a simple frustration: every time we wanted to give an AI agent access to email or a calendar, we ended up hand-rolling IMAP parsers or duct-taping half-supported APIs together. So we built the thing we wished existed: one relay engine that speaks IMAP, SMTP, JMAP, CalDAV, CardDAV, gRPC, REST, and MCP against a single source of truth. Point a legacy mail client at it, or point an LLM at it via MCP same data, same guarantees, zero config translation layer in between. A few things we're proud of under the hood: Delta-sync, not full-scan CONDSTORE/QRESYNC means clients resync with a single modseq comparison after any disconnect. Exactly-once delivery every webhook, gRPC push, and Kafka event is written atomically with the state change that triggered it. MCP-first for agents hermes_list_messages, hermes_book_appointment, hermes_search_contacts, and more, so agents get structured tools instead of raw message bodies. Isolation enforced at the data layer an unset tenant session variable returns zero rows by design. There's no application code path to cross-tenant data. We're in sandbox testing right now (beta) and opening a private Early Access Beta; beta testers get a dedicated sandbox instance, priority gRPC/MCP/CLI gateway access, unlimited SMTP relays, and direct developer support over Telegram/Discord. 👉 Request early access: https://hermers.aduki.org/soon Would love feedback from anyone building agent tooling, dev platforms, or anything that touches inbox/calendar data; what would you want an MCP mail server to expose first?