MailMan
- CATEGORYMCP server · AI email
- INTERFACEAI chat + npm CLI
- RUNS ONmacOS · Linux · Windows
- LICENCEMIT · no telemetry
Send and read Gmail just by asking your AI assistant — “send those docs to Kalpesh,” “show my last 10 emails.” MailMan is an MCP server that drafts, previews, and only sends on your OK. Nothing leaves your machine without you.
Where MailMan fits
- Agencies & Dev Teams
- Lets developers send and read Gmail from their AI editor — draft, preview, confirm — without leaving the terminal.
Send and read Gmail from your AI assistant.
One idea, two audiences. Whether you write code or not, MailMan turns your AI assistant into the fastest way to move email — the same instinct behind our AI agents work, packaged as a tool you run yourself.
MailMan lets you send and read email just by asking your AI assistant — “send those docs to Kalpesh,” “show my last 10 emails,” “reply politely and decline.”
You set it up once. After that you just talk — no menus, no copy-paste, no leaving your chat. And it always shows you the email before it sends, so you’re never surprised.
MailMan is a Node.js MCP server (Model Context Protocol). Your AI tool launches it over a pipe — npx -y @integratex/mailman — and calls its tools from natural language.
It reaches Gmail two ways — SMTP/IMAP for App Password accounts, or the Gmail REST API for OAuth2. Pure Node, so behavior is identical across operating systems, and every tool returns plain JSON any MCP host can render.
Ask, preview, then it sends.
You stay in your editor and just talk. MailMan drafts, shows you exactly what will go out, and only sends on your OK — then pings you it’s done.
- to
- kalpesh.gamit@indianic.com
- subject
- Q3 Report
- attach
- Q3-report.pdf (84 KB) · signature appended
- Reimbursement approved
- Q3 budget sign-off
- Invoice #4412
Three moves, and the last one is yours.
Everyday email goes through your AI. Anything sensitive — setup, accounts, credentials — stays in your own hands at the terminal.
You ask
“MailMan, send the checklist to Kalpesh.” Your AI resolves the file and composes the message, right in the editor you already had open.
You preview
MailMan drafts it and shows exactly what will go out — From, To, Subject, attachments, signature. Nothing has left your machine yet.
You confirm
Say “send it.” Only then does confirm_send dispatch, over Gmail SMTP or the API — with a desktop notification to close the loop.
Everything email, hands-free.
A full email toolkit exposed to your AI assistant — with the safety rails a human would want. Every one of these is a tool your model can call, and none of it can send behind your back.
- 01 · TOOL
Natural-language send
Ask in plain English. MailMan composes the subject and body and shows you a preview before anything goes out.
- 02 · TOOL
182 message templates
FYI, follow-up, meeting, status, forward and reply — plus 175 more, each a subject prefix and a hint your AI composes from. Browse them with list_templates.
- 03 · TOOL
Draft → preview → confirm
Nothing leaves your machine until you approve it. confirm_send won’t dispatch without an explicit confirmation — and it’s idempotent.
- 04 · TOOL
Attachments & globs
Attach files, whole folders, or wildcard patterns like *.pdf — with a 25 MB size guard and a preview of exactly what attaches.
- 05 · TOOL
Scheduled sends
“Send tomorrow at 9am.” An OS-level timer fires it even if your AI tool is closed.
- 06 · TOOL
Read & search inbox
List recent mail, read full messages, and search by sender, subject, date, or has:attachment.
- 07 · TOOL
Contacts & suggestions
Everyone you email is remembered. Say “email John” and get ranked, fuzzy-matched suggestions.
- 08 · TOOL
Desktop notifications
A native “email sent” notification after every send — interactive and scheduled. On by default.
- 09 · TOOL
Machine-bound security
AES-256-GCM over your credentials, with the master key in the OS keychain. Copy-proof across machines.
- 10 · TOOL
Cross-OS, pure Node
Identical behavior on macOS, Linux and Windows. Ships as @integratex/mailman on the public npm registry.
- 11 · TOOL
Session reports
Turn past AI coding sessions into an email — search by project, branch or date, digest one or many, and send. Tool output is dropped and secrets redacted first.
- 12 · TOOL
Built-in doctor
mailman doctor verifies the whole environment, and --fix prints the exact install command for anything missing.
Built so it can’t misbehave.
Handing an AI assistant your email is a real trust decision. Here is exactly what MailMan does with it — and what it deliberately cannot do. It’s the security posture our AI & ML engineering brings to anything that touches real systems.
Credentials never leave your machine
Your Gmail App Password or OAuth2 token is encrypted with AES-256-GCM, and the master key lives in your OS keychain — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux. Copy the config file elsewhere and you get useless ciphertext.
Nothing sends without your explicit OK
Every send is draft → preview → confirm. MailMan builds the message, shows you exactly what will go out — recipients, subject, body, attachments — and only dispatches once you approve that specific draft.
There is no raw “send” tool to misuse
The AI is never handed a one-shot send. The only tool that dispatches is confirm_send; it accepts nothing but a draft id and an approval flag, and it cannot carry a recipient or body of its own. The gate is structural, not a policy the model is asked to follow.
No servers, no accounts, no telemetry
MailMan runs entirely on your machine and talks to Gmail directly over SMTP, IMAP or the Gmail API. There is no MailMan backend, no sign-up, and no analytics — we never see your mail, your contacts or your credentials.
Session digests are scrubbed first
When MailMan summarises past AI sessions, it drops every tool result, redacts known token shapes — API keys, GitHub and npm tokens, JWTs, KEY=value pairs — and shortens home paths, all before the draft you review is written.
Auditable and open
MIT-licensed, source on GitHub, published to the public npm registry. Local activity is logged so you can see what ran and when — if a claim here matters to you, you can read the code that makes it true.
Works with your tools and your OS.
One install, wired into whatever AI editor you already use. mailman register sets it up — idempotent, safe to re-run — because MailMan speaks MCP, not a per-editor plugin.
macOS
Verified end-to-end
Linux
Verified (Docker)
Windows
Supported · pure Node
Same behavior everywhere — it’s pure Node.js. Credentials go in each OS’s native keychain: Keychain, Secret Service and Credential Manager.
Say it however you’d say it.
Once it’s installed, you just talk to your AI. Here’s the kind of thing you can say — in your own words, no special syntax.
- “Email the Q3 report to kalpesh.gamit@indianic.com.”
- “Reply to the last email from finance and say I approve.”
- “Send a thank-you note to everyone on yesterday’s call.”
- “Show my last 10 emails.”
- “Any unread mail from Priya this week?”
- “Find the invoice with an attachment from March.”
- “Send this tomorrow at 9am.”
- “Schedule the newsletter for Monday morning.”
- “What sends do I have queued?”
- “Attach all the PDFs in ~/reports and send to the team.”
- “Send the deck folder to Kalpesh Gamit.”
- “What would *.png in this folder attach?”
That’s twelve of them. The live product indexes 250 more, grouped by the job you’re doing — standups, invoices, hiring, incidents, inbox triage. For a build like this shaped to your own workflow, see our rapid POC program.
Up and running in three commands.
Requires Node 18+. Nothing to sign up for — it installs from the public npm registry and runs entirely on your machine.
- 01
Install globally
npm install -g @integratex/mailman - 02
First-run setup
mailman init - 03
Register with your AI editor
mailman register
Your normal Gmail password won’t work — Google blocks it for mail apps. Connect with a 16-character App Password (simplest) or sign in with the browser over OAuth2 for passkey and Workspace accounts. The same steps appear inside the CLI as you go.
Everything you’d ask before trying it.
The questions people actually ask about handing email to an AI — answered plainly.
Do I need to be technical to use it?
No. A developer (or the setup wizard) installs it once. After that you just talk to your AI assistant in plain English — “email this to Kalpesh,” “what did I get from finance today?”
Will it send an email without my permission?
Never. Every send follows draft → preview → confirm. MailMan prepares the message, shows you exactly what will go out, and only sends after you say yes.
Is my email account safe?
Yes. Your credentials are encrypted with AES-256-GCM and the key lives in your operating system’s keychain — never in a plain file and never uploaded to us. Copying the config to another machine yields useless ciphertext.
Which email providers work?
Gmail today — via a simple App Password (recommended) or OAuth2 for Workspace setups. Sending uses SMTP; reading and search use IMAP or the Gmail API.
What happens if I close my AI tool?
Scheduled emails still go out. The first time you schedule something, MailMan installs an OS-level timer (launchd, cron or Task Scheduler) that fires independently of your editor.
Which AI tools does it work with?
Anything that speaks MCP — Claude Code, Claude Desktop, Cursor, Gemini CLI, Windsurf and Codex. mailman register writes the config for whichever ones you pick, so you never hand-edit a JSON file.
Is it free? Can I read the source?
Free and MIT-licensed. The package is @integratex/mailman on the public npm registry and the source is on GitHub.
Try MailMan on its own site.
MailMan runs its own live micro-site — the full walkthrough, the 250-use-case index, and the install command. It’s one of a portfolio of products we build and run in-house.
Ship email from the chat, under your own brand.
MailMan is production-ready and MIT-licensed today — and white-label capable. Tell us how your team works and we’ll help you deploy it under your brand, wired into your assistants and your accounts.