adecubed/gigamail

**English** · Italiano · 中文
**MCP server that gives your agent — Claude, Codex, OpenClaw, Hermes, or any
MCP client — safe, controlled access to your email** — multi-account (Microsoft Graph + IMAP), calendar,
local search index, sender memory, and an agent-aware permission model.
No built-in LLM: the intelligence is your agent's. The MCP server speaks
stdio only — no network port. (An optional human console adds a local HTTP
API bound to 127.0.0.1.)
**On your data**: GigaMail keeps mail indexes, credentials, memory and
configuration **on your machine** — we run no service and receive nothing.
Mail content your agent reads is, of course, handled by that agent and its
model provider under their own data policies. Choose your agent
accordingly; the masker lets you hide sensitive fields (tax codes, VAT
numbers, IBANs, emails, phone numbers — validated deterministically, no AI)
before the agent ever sees them.
*One minute: the console drafts a reply, takes the figure from your own files, stops where the documents stop, and nothing leaves without your approval — from the console or from your agent.*
Why
- **Hybrid search**: provider search (Graph/IMAP) + local SQLite index — fast
and offline-friendly
- **Its own archive**: every mail of every account saved locally,
attachments included, and still searchable after the server has dropped
it. Outlook's history on the PC is imported once (gigamail archive)
- **Sender memory**: tone, topics and history per sender, so replies sound right
- **Contact notes**: what happened with each person — how a meeting went,
what they are after — is written next to their name, and every draft to
them reads it
- **Observer**: patterns learned from how the user edited past drafts
- **Calendar-aware drafts**: a draft only proposes times that are free in
your calendar, inside your office hours
- **Accounts viewed together** (console): drag one account tile onto
another to read both mailboxes as one list; every mail keeps its
account, so replies leave from the right address, and "Split" undoes
it. The agent keeps seeing separate accounts
- **Knowledge files**: attach your price lists, terms, product sheets to an
account — the agent reads them to answer mail. Your agent doesn't need to
know everything: the account carries its own knowledge
- **Agent-aware permissions**: reads are free; send/delete require an
approval given **out of band** — the agent gets an inert request id, a
human approves from the console or the CLI, and only then does it execute,
with the exact arguments the human saw. Every write lands in an
append-only action log
- **Credentials never touch the agent channel**: login and account management
live in the CLI only — a prompt injection inside an email cannot add
accounts or read secrets
Quick start
GigaMail ships through two channels:
- **Desktop app, Windows and macOS** — download it from
gigamail.ai or from the
latest release. The human console with its own Python: one
installer, no prerequisites, no administrator password, and it updates
itself.
- **Windows 10/11**: GigaMail-Setup.exe, code-signed. The
certificate is new, so on first launch Windows may still say
"unrecognized app": click **More info**, then **Run anyway**.
- **macOS**: GigaMail-arm64.dmg for Apple Silicon,
GigaMail-x64.dmg for Intel, both signed with an
Apple Developer ID and notarized by Apple.
The SHA-256 digests are next to the files on the release page.
To build it yourself: Node 22+, console/prepare-python.ps1
(Windows) or console/prepare-python.sh (macOS), then npm run dist or
npm run dist:mac.
- **pip install gigamail** — the agentic core: MCP server, CLI, watcher
and the console's local HTTP backend. No graphical app — the right
channel when your agent is the interface.
Everything below covers the pip channel.
> **Microsoft login note**: the bundled Azure app is not yet
> publisher-verified, so the consent screen shows an "unverified" notice
> (works fine; some corporate tenants may block it). Standard alternative:
> register your own Azure app and set your client_id in
> src/gigamail/core/ms_config.json. IMAP needs none of this.
Give the account its identity and knowledge (this is what makes replies yours):
Register in Claude Desktop / Claude Code (mcpServers):
The commands are also available under their legacy names
(ade-mail-agent, ade-mail-agent-server), and the Python package answers
to its old name ade_mail_agent too (python -m ade_mail_agent.server),
so existing setups keep working.
Using **Claude Code**? The repository is also a Claude Code plugin: it