Atrix Mail: 41-tool MCP server on npm
Multi-tenant email hosting with a developer sending API and AI webmail.
The calls that shaped it
Own the infrastructure that everyone outsources
Postfix, Dovecot and Rspamd with SPF, DKIM and DMARC, run multi-tenant. Email deliverability is unforgiving and most teams never touch it; owning it end-to-end is what makes a hosting-plus-sending product possible.
A developer API and AI webmail on the same core
A Bun API handles sending; PostgreSQL with pgvector gives semantic search across mail. Per-mailbox Stripe billing is live.
Publish the integration
A 41-tool MCP server on npm means any agent can read, search, draft and send through the platform with the user's permission — the same MCP-first approach as Atrix and Atrix Analytics.
What this proves about how I lead
Atrix Mail shows depth on the operations side of engineering: DNS, mail protocols, spam filtering, multi-tenancy and billing all have to be right at once. It is the kind of system I expect a CTO to be able to debug at 2 a.m., and I built it so that I can.
Every product under Atrix was built with the same operating model I bring to a team: a written architecture decision before the first commit, a thin vertical slice in production within the first weeks, AI-assisted delivery for the volume work, and human judgment reserved for the decisions that compound — data model, security boundary, provider choice. The hire-me page lays out how that translates into a 90-day plan for your company.
Want to talk through the architecture?
I'm happy to walk a hiring panel or a founder through any of these systems in detail — or ask my AI twin first.