Install
pip install "gigamail[all]"Who it is for
For people who need an assistant to touch mail, calendar, and local knowledge files under a permission model. GigaMail speaks MCP; the docs name Claude, Codex, OpenClaw, Hermes, and other MCP hosts. Capabilities include multiple accounts (Microsoft Graph + IMAP), calendar, a local search index, sender memory, and assistant-facing permission controls. It does not ship a model; intelligence comes from your assistant.
There are two hard prerequisites. First install the package with extras via pip, then a human completes mailbox onboarding in their own terminal; the assistant must not do this. The onboarding commands are gigamail login and gigamail accounts add-imap, and they ask for credentials. Without a human login first, later reads and writes have no account to target.
Not for people who want the assistant to finish OAuth or IMAP password entry, nor for people who read “stdio does not listen on a port” as “no local service at all”: the optional human console opens HTTP on 127.0.0.1.
First try in 3 minutes
Official install:
pip install "gigamail[all]"
Configure it under mcpServers in Claude Desktop / Claude Code. The command is gigamail-server; you do not need to add a port. MCP itself uses only stdio and does not listen on a network port.
After install, leave the assistant and run gigamail login in your own shell (or gigamail accounts add-imap for IMAP). The docs say a human must do this, and the system is designed so it cannot be done through the assistant. Do not paste credentials into chat.
After the host starts gigamail-server, the first pass should be read-only. The docs split tools into read-only, auditable safe writes, and 6 dangerous actions. The dangerous set includes send, reply, delete message, delete folder, create/delete calendar event, and needs out-of-band human approval. Do not touch those 6 on the first try. Success is a read-only call returning mail or calendar summaries visible in your account, not a send confirmation. Read-only still sees the real inbox; it is not zero risk.
Use cases
Case 1: Search mail or calendar in an already signed-in account. The docs stress the local search index and controlled mailbox access, and mention a set of read-only tools. Good for “find one message first” or “check today’s schedule first”. The existing docs do not name the read-only tools or their parameters; do not invent search or list commands. What can be confirmed: multiple accounts, Graph and IMAP, and a local index exist.
Case 2: Send, reply, delete a message, delete a folder, or create/delete a calendar event. These are labeled Dangerous, 6 in total, and require out-of-band human approval. For when you really need to change mail or a calendar and a person is present to confirm. Before calling, lock the confirmation point: until a human approves out of band, mail should not go out and events should not be written. The existing docs do not describe an approval UI or timeout, and have no steps to undo an already sent message.
Limits
Mailbox login cannot be completed through the assistant. MCP is described as stdio only and not listening on a port, but the optional console binds HTTP on 127.0.0.1; do not read that as “no network, no local interface”. Mail, calendar, and knowledge files are real data; the permission model reduces mistakes, it does not eliminate reads.
Dangerous actions are fixed as those 6 kinds and need out-of-band approval. Other writes are summarized as auditable safe writes and are not named one by one. There is no built-in model; quality depends on your assistant. The existing docs have no quotas, vendor rate limits, or complete account-removal steps. After credentials are given to gigamail login, any host that can drive this MCP may read the same mailbox.