Reads and searches
Provider search plus a local index, so "the quote we sent in March" is one question. A local archive keeps every mail and attachment, even after the server drops it.
Open source · Windows & macOS · MCP server
GigaMail is agentic email with a human in the loop. Claude, Codex or any MCP agent reads your inbox, finds what it needs in your documents and calendar, and prepares the reply. Nothing is sent or deleted until you approve it.
What your agent can do
Reading, searching, remembering and drafting are free. Only the actions that leave a trace outside wait for you.
Provider search plus a local index, so "the quote we sent in March" is one question. A local archive keeps every mail and attachment, even after the server drops it.
Attach price lists, terms and product sheets to an account. The reply quotes your figures and stops where your documents stop.
Drafts propose only slots that are free, inside your office hours. Events are created after you approve. Microsoft 365 or Google Calendar.
The text of PDFs and office files is available to the agent, so the answer can come from the brochure, not from a guess.
History, tone and your own notes sit next to each sender. Every draft to that person reads them first.
"Mail from these senders gets a draft from these documents." Semi-auto asks you each time; auto runs inside a scope you signed, with an expiry and a daily cap.
Microsoft 365 and IMAP: Outlook, Gmail, Aruba, Libero, any server. Several accounts, one view in the console, and each reply leaves from the right address.
The masker replaces tax codes, VAT numbers, IBANs and phone numbers before the agent sees them. Deterministic, no AI involved.
The desktop console adds a mail client built around the agent: ask your mail a question in plain language, dictate a command, see the requests waiting for you, manage automations, and read several accounts as one list. The same engine, without a terminal.
The human checkpoint
An agent can ask to send a message. It never receives anything it could use to approve its own request.
A send, reply or delete returns the preview and an inert request id. The agent can show you the proposal; it cannot turn that id into an action.
request req_7f3a · inertFrom the console, the command line, Telegram or a Windows notification. The approval is confirmed with Windows Hello or Touch ID: a person at the machine, not a process.
Held · awaiting approvalExecution uses the arguments you reviewed, never a replacement supplied afterwards. Every write lands in an append-only action log.
Approved by you · sentAn email is input, not authority. Message content is treated as untrusted data. Credentials never pass through the agent channel, and no MCP tool can create or change an automation rule, so an instruction hidden in a mail cannot add an account, read a secret or switch on autopilot.
Security modelThree steps
The desktop app walks you through all three. From a terminal, the same steps take a few minutes.
Step 1
One installer with its own Python: no prerequisites, no administrator password, updates itself.
Signed and notarized. SHA-256 digests on the release page. No graphical app needed? The core alone:
pip install "gigamail[all]"
Step 2
In the app, the onboarding does it: Microsoft 365 with a login in your browser, or IMAP with an app password. From the terminal:
gigamail login # Microsoft 365, device flow
gigamail accounts add-imap # Gmail, Aruba, Libero, ...
gigamail check # a search, a draft held for you
Then say who replies: identity, tone, and the files the agent may quote.
gigamail identity set
gigamail identity add-file ./pricelist.xlsx
Credentials go through you, in your own shell. There is no tool an agent could use to add an account.
Step 3
GigaMail has no AI of its own: the intelligence is the agent you connect. The app's third step copies the exact config for you; by hand it is one of these.
The repository is a Claude Code plugin: it registers the server and adds a skill that teaches Claude the approval gate.
claude plugin marketplace add adecubed/gigamail
claude plugin install gigamail@gigamail
Add the server to claude_desktop_config.json under mcpServers, then restart Claude Desktop.
{
"mcpServers": {
"gigamail": { "command": "gigamail-server" }
}
}
As a Codex plugin, with the same skill:
codex plugin marketplace add adecubed/gigamail
codex plugin add gigamail@gigamail
Or register the server alone, which is also what the OpenAI Plugins Directory entry expects:
codex mcp add gigamail -- gigamail-server
Using ChatGPT rather than the terminal? The step-by-step guide.
OpenClaw probes the server before saving it. Point GIGAMAIL_ROOT at your GigaMail data folder.
openclaw mcp add gigamail --command gigamail-server \
--env "GIGAMAIL_ROOT=<your data folder>"
openclaw skills install @adecubed/gigamail # the approval-gate skill
Hermes passes stdio servers only the environment you declare, so GIGAMAIL_ROOT is required. In ~/.hermes/config.yaml:
mcp_servers:
gigamail:
command: "gigamail-server"
env:
GIGAMAIL_ROOT: "<your data folder>"
Check with hermes mcp test gigamail.
Any MCP client that can start a stdio server works. Command gigamail-server, no network port, no API key. Declare GIGAMAIL_ROOT if the client filters the environment.
Verified setups, tool filters and how to get approvals on your phone: INTEGRATIONS.md.
Videos
Connect a mailbox, say who replies, connect your agent. All set.
A client writes, your agent drafts the reply, you approve outside its reach. Then, and only then, it leaves.
Questions
Email where an AI agent does the reading, searching and drafting for you, and a person keeps the decisions that matter. In GigaMail the agent prepares; sending, replying and deleting wait for your approval.
Claude Code and Claude Desktop, Codex, OpenClaw, Hermes and any client that speaks MCP. GigaMail has no AI of its own: the intelligence is the agent you connect, and its data policy is the one that applies to what it reads.
Microsoft 365 and Outlook.com through Microsoft Graph, and any IMAP server: Gmail, Aruba, Libero and others. Several accounts side by side, each replying from its own address.
On your machine. Mail index, archive, credentials, memory and configuration stay local; GigaMail runs no servers and receives nothing. The masker can hide sensitive fields before the agent sees a message. Details in the Privacy Policy.