Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
uvx gigamail==0.3.4Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
GIGAMAIL_ROOT=<value> claude mcp add io.github.adecubed-gigamail -- uvx gigamail==0.3.4รันในเทอร์มินัล
{ "mcpServers": { "io.github.adecubed-gigamail": { "command": "uvx", "args": [ "gigamail==0.3.4" ], "env": { "GIGAMAIL_ROOT": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิด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.
gigamail archive)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.
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.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.
pip install "gigamail[all]"
gigamail login # Microsoft device flow
gigamail accounts add-imap # or IMAP: Aruba, Gmail, Libero, ...
gigamail check # search, a draft held for your approval, a test mail to yourself
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_idinsrc/gigamail/core/ms_config.json. IMAP needs none of this.
Give the account its identity and knowledge (this is what makes replies yours):
gigamail identity set # who am I, what I do, tone
gigamail identity add-file C:\docs\pricelist.xlsx
gigamail identity add-file C:\docs\catalog\ # whole folder
Register in Claude Desktop / Claude Code (mcpServers):
{
"gigamail": {
"command": "gigamail-server"
}
}
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
registers the gigamail MCP server and adds a skill that teaches Claude the
approval gate.
claude plugin marketplace add adecubed/gigamail
claude plugin install gigamail@gigamail
Using Codex? The repository is a Codex plugin: it registers the
gigamail MCP server and adds a skill that teaches Codex the approval gate.
codex plugin marketplace add adecubed/gigamail
codex plugin add gigamail@gigamail
GigaMail is also in the OpenAI Plugins Directory,
as a skill: install it from there, then register the server with
codex mcp add gigamail -- gigamail-server (the server comes from pip,
as above).
Using OpenClaw or Hermes? Verified configs in INTEGRATIONS.md.
Are you an AI agent setting this up on behalf of a human? You can do the install and the MCP registration:
pip install "gigamail[all]", then addgigamail-serverto your client's MCP config (see INTEGRATIONS.md; declareGIGAMAIL_ROOTif your client filters the environment). Stop there. Connecting a mailbox (gigamail login,gigamail accounts add-imap) asks for credentials and must be done by the human in their own shell — it is not something you should do, and GigaMail is built so that it cannot be done through you. Tell them what to run, then wait.
Then just ask your agent: "reply to the last quote request using the price list" — it reads the mail, pulls the numbers from your file, drafts the reply, and asks you before sending.
29 typed tools, generated from the server itself:
The calendar is served by Microsoft Graph or Google Calendar, whichever
the user connected; the tools are the same either way. Drive uses the
drive.file scope, so it only ever sees files GigaMail created itself.
Connecting Google: GOOGLE_SETUP.md.
Full map and design decisions: MAPPA_MCP.md.
Email content is treated as untrusted data (prompt injection). The
agent cannot approve its own actions, by construction: a dangerous tool
returns only an inert request_id, and approving it — from the console or
from gigamail approvals approve — requires an OS-level verification of
the person at the machine (Windows Hello / Touch ID). A process,
including an agent that holds a shell, can open that prompt but cannot
pass it. On Linux, where neither exists, a local PIN typed in an
interactive terminal stands in (gigamail approvals pin): weaker, and
declared so in SECURITY.md. Telegram approval is opt-in and
the weakest channel of the three. No secret ever
enters the model context, so an injected instruction has nothing to
spend. Repeating the id just returns awaiting approval. The agent
can only read files explicitly registered by the user, never the rest of the
filesystem. Every write action is logged to %APPDATA%/ADE/agent_audit.jsonl
(append-only: GigaMail never rewrites past entries — it is not, and does not
claim to be, tamper-proof storage).
We red-team this: hostile emails ordering exfiltration, mass deletion, and the agent to approve itself — fed to a real agent with every mail tool enabled.
This design is a fix. v0.1.0 returned a one-time confirm token in the tool result, which put it in the model's context: the agent held both halves. Thanks to u/ranbuman and u/anderson_the_one on r/mcp for catching it. The switch now sits where the agent cannot reach.

The structural half of that suite runs in CI on every push (tests/test_injection.py); the real-agent half is opt-in (scripts/injection_e2e.py) and runs with a dry-run guard so confirmed actions are audited but never executed.
You can tell GigaMail: mail from these senders (or in this folder) gets a
reply drafted from these documents. Rules are created from the CLI —
gigamail rules add — behind the same Windows Hello / Touch ID prompt as
approvals, and gigamail watch is the process that applies them. The MCP
server stays passive and there is no MCP tool that touches rules: an
injected instruction cannot enable autopilot.
gigamail desktop-setup once — UAC prompt — to make
them clickable; they open the approval, which raises Hello) and
Telegram (gigamail telegram setup, your own bot: ✅ approve if you
opted in with --approve behind Hello, ❌ reject, ✏️ ask for changes —
accepted only from your chat). Telegram approval is a convenience, not
the normal path: any device signed into your Telegram can tap it, so it
is weaker than Hello (see SECURITY.md).decided_by automode:<rule_id> —
you gave that approval when you created the rule, for a precise scope,
with a mandatory expiry, a daily cap and a per-sender cooldown. The
notification still fires.The drafter (your own agent, via claude -p) produces the reply body
and nothing else: recipient, subject and thread are fixed from the incoming
message — always the sender, never Reply-To, never an address written by
the draft. Deterministic barriers run first: no DMARC pass → never auto;
auto-generated mail, lists, no-reply senders, the provider's spam verdict,
executable attachments → no reply at all; the first message from a new
sender always goes through you; a burst of matches pauses the rule by
itself. Details in SECURITY.md.
The gigamail package does mail: accounts, index, search, two-phase
send, calendar, knowledge files, audit. What only makes sense for one
trade lives outside it and is off until you turn it on:
appointments (built in, off by default): mail and calendar,
connected, from the first reply to the follow-up.
gigamail debrief lists the
unanswered ones). The answer goes into the contact's notes.real_estate (extras/real_estate): flat-type
check on drafts and unit codes that pick the attachments, for agencies
answering property-portal enquiries. This is where GigaMail grew up.gigamail extensions list
gigamail extensions enable appointments # asks for Windows Hello / Touch ID
gigamail extensions install real_estate # into the data folder: survives app updates
gigamail extensions enable real_estate
An enabled extension that fails to load stops automatic drafts and tells the human; it is never skipped silently.
AGPL-3.0-or-later. Free to use, study, modify and share. If you distribute a modified version — or run one as a network service — you must make its source available under the same license. Commercial licenses for closed-source use are available from the copyright holder.
Server MCP che dà al tuo agente — Claude, Codex, OpenClaw, Hermes o qualunque client MCP — accesso sicuro e controllato alla tua posta — multi-account (Microsoft Graph + IMAP), calendario, indice di ricerca locale, memoria dei mittenti e un modello di permessi pensato per gli agenti.
Nessun LLM interno: l'intelligenza è quella del tuo agente. Il server MCP parla solo stdio — nessuna porta di rete. (La console per l'umano, che è opzionale, aggiunge una API HTTP locale su 127.0.0.1.)
Sui tuoi dati: GigaMail tiene indici della posta, credenziali, memoria e configurazione sul tuo computer — noi non gestiamo alcun servizio e non riceviamo nulla. Il contenuto delle mail che il tuo agente legge è ovviamente trattato da quell'agente e dal suo fornitore di modello secondo le loro policy. Scegli l'agente di conseguenza; il masker permette di nascondere i dati sensibili (codici fiscali, partite IVA, IBAN, email, telefoni — validati in modo deterministico, senza AI) prima che l'agente li veda.
Un minuto: la console scrive la bozza, prende la cifra dai tuoi file, si ferma dove i documenti si fermano, e niente parte senza la tua approvazione — dalla console o dal tuo agente.
gigamail archive)GigaMail si installa da due canali:
App desktop, Windows e macOS — si scarica da gigamail.ai o dall'ultima release. La console umana con il suo Python incluso: un solo installer, nessun prerequisito, nessuna password di amministratore, e si aggiorna da sola.
GigaMail-Setup.exe, firmato. Il
certificato è nuovo: al primo avvio Windows può ancora dire "app non
riconosciuta"; clicca Ulteriori informazioni, poi Esegui
comunque.GigaMail-arm64.dmg per Apple Silicon,
GigaMail-x64.dmg per Intel, firmati con Apple
Developer ID e notarizzati da Apple.I digest SHA-256 sono accanto ai file nella pagina della release. Per
buildarla in casa: Node 22+, console/prepare-python.ps1 (Windows) o
console/prepare-python.sh (macOS), poi npm run dist o
npm run dist:mac.
pip install gigamail — il core agentico: server MCP, CLI, watcher
e il backend HTTP locale della console. Nessuna app grafica — è il
canale giusto quando l'interfaccia è il tuo agente.
Tutto quello che segue riguarda il canale pip.
pip install "gigamail[all]"
gigamail login # device flow Microsoft
gigamail accounts add-imap # oppure IMAP: Aruba, Gmail, Libero, ...
gigamail check # ricerca, bozza in attesa della tua approvazione, mail di prova a te stesso
Nota sul login Microsoft: l'app Azure inclusa non è ancora publisher-verified, quindi la schermata di consenso mostra l'avviso "unverified" (funziona comunque; alcuni tenant aziendali potrebbero bloccarla). Alternativa standard: registra la tua app Azure e metti il tuo
client_idinsrc/gigamail/core/ms_config.json. Per IMAP non serve nulla di tutto questo.
Dai all'account la sua identità e la sua conoscenza (è ciò che rende le risposte tue):
gigamail identity set # chi sono, cosa faccio, tono
gigamail identity add-file C:\docs\listino.xlsx
gigamail identity add-file C:\docs\catalogo\ # intera cartella
Registrazione in Claude Desktop / Claude Code (mcpServers):
{
"gigamail": {
"command": "gigamail-server"
}
}
I comandi restano disponibili anche con i vecchi nomi
(ade-mail-agent, ade-mail-agent-server), e il package Python risponde
anche al vecchio nome ade_mail_agent (python -m ade_mail_agent.server),
così le installazioni esistenti continuano a funzionare.
Usi Claude Code? Il repository è anche un plugin Claude Code: registra
il server MCP gigamail e aggiunge una skill che insegna a Claude il gate di
approvazione.
claude plugin marketplace add adecubed/gigamail
claude plugin install gigamail@gigamail
Usi Codex? Il repository è un plugin Codex: registra il server MCP
gigamail e aggiunge una skill che insegna a Codex il gate di approvazione.
codex plugin marketplace add adecubed/gigamail
codex plugin add gigamail@gigamail
Usi OpenClaw o Hermes? Configurazioni verificate in INTEGRATIONS.md.
Poi chiedi al tuo agente: "rispondi all'ultima richiesta di preventivo usando il listino" — legge la mail, prende i numeri dal tuo file, prepara la risposta e ti chiede conferma prima di inviare.
29 tool tipizzati, generati dal server stesso:
Il calendario è servito da Microsoft Graph o da Google Calendar, secondo
quello che l'utente ha collegato: i tool sono gli stessi. Drive usa lo
scope drive.file, quindi vede solo i file creati da GigaMail.
Per collegare Google: GOOGLE_SETUP.md.
Mappa completa e decisioni di design: MAPPA_MCP.md.
Il contenuto delle email è trattato come dato non fidato (prompt
injection). L'agente non può approvare le proprie azioni, per costruzione:
un tool pericoloso restituisce solo un request_id inerte, e approvarlo —
dalla console o con gigamail approvals approve — richiede una verifica
dell'utente fisico a livello di sistema operativo (Windows Hello /
Touch ID). Un processo, compreso un agente con la shell, può aprire quel
prompt ma non superarlo; senza un backend del genere, nulla viene approvato.
Nessun segreto entra nel contesto del modello, quindi un'istruzione
iniettata non ha nulla da spendere. Ripetere
l'id restituisce solo in attesa di approvazione. L'agente può leggere solo i file
registrati esplicitamente dall'utente, mai il resto del filesystem. Ogni
azione di scrittura finisce in %APPDATA%/ADE/agent_audit.jsonl (append-only:
GigaMail non riscrive mai le voci passate — non è, e non pretende di essere,
un archivio a prova di manomissione).
Lo mettiamo alla prova: mail ostili che ordinano esfiltrazione, cancellazione di massa e all'agente di approvarsi da solo, date a un agente reale con tutti i tool attivi.
Questo disegno è una correzione. La v0.1.0 restituiva un token di conferma monouso nel risultato del tool, quindi dentro il contesto del modello: l'agente aveva entrambe le metà. Grazie a u/ranbuman e u/anderson_the_one su r/mcp per averlo notato. Ora l'interruttore sta dove l'agente non arriva.

La metà strutturale della suite gira in CI a ogni push (tests/test_injection.py); quella con l'agente reale è opt-in (scripts/injection_e2e.py) e usa una modalità dry-run, così le azioni confermate finiscono nell'audit ma non vengono mai eseguite.
Puoi dire a GigaMail: le mail da questi mittenti (o in questa cartella)
ricevono una risposta preparata da questi documenti. Le regole si creano
dalla CLI — gigamail rules add — dietro lo stesso prompt Windows Hello /
Touch ID delle approvazioni, e gigamail watch è il processo che le
applica. Il server MCP resta passivo e nessun tool MCP tocca le regole:
un'istruzione iniettata non può accendere l'autopilota.
gigamail desktop-setup — prompt UAC — per renderli
cliccabili; aprono l'approvazione, che alza Hello) e Telegram
(gigamail telegram setup, col tuo bot: ✅ approva se hai scelto
--approve dietro Hello, ❌ rifiuta, ✏️ chiedi modifiche — accettati
solo dalla tua chat).decided_by automode:<rule_id> — quell'approvazione l'hai data tu creando la regola,
per uno scope preciso, con scadenza obbligatoria, tetto giornaliero e
cooldown per mittente. La notifica parte comunque.Chi scrive (il tuo agente, via claude -p) produce il corpo della
risposta e nient'altro: destinatario, oggetto e thread li fissa GigaMail
dal messaggio in arrivo — sempre il mittente, mai il Reply-To, mai un
indirizzo scritto dalla bozza. Prima passano barriere deterministiche:
niente DMARC pass → mai auto; posta automatica, liste, mittenti no-reply,
il verdetto spam del provider, allegati eseguibili → nessuna risposta; il
primo messaggio di un mittente nuovo passa sempre da te; una raffica di
match mette in pausa la regola da sola. Dettagli in
SECURITY.md.
Il pacchetto gigamail fa posta: account, indice, ricerca, invio a due
fasi, calendario, documenti, audit. Cio' che serve a un solo mestiere
vive fuori ed e' spento finche' non lo accendi:
appointments (incluso, spento di default): posta e calendario
collegati, dalla prima risposta al follow-up.
gigamail debrief
elenca quelle senza risposta). La risposta finisce nelle note del
contatto.real_estate (extras/real_estate): controllo
della tipologia sulle bozze e codici delle unita' che scelgono gli
allegati, per le agenzie che rispondono ai portali. E' qui che GigaMail
e' nato.gigamail extensions list
gigamail extensions enable appointments # chiede Windows Hello / Touch ID
gigamail extensions install real_estate # nella cartella dati: resiste agli aggiornamenti
gigamail extensions enable real_estate
Un'estensione accesa che non si carica ferma le bozze automatiche e avvisa l'umano: non viene mai saltata in silenzio.
AGPL-3.0-or-later. Libero di usarlo, studiarlo, modificarlo e condividerlo. Se distribuisci una versione modificata — o la offri come servizio in rete — devi rendere disponibile il sorgente con la stessa licenza. Licenze commerciali per usi closed-source sono disponibili dal titolare del copyright.
一个 MCP 服务器,让你的代理 —— Claude、Codex、OpenClaw、Hermes 或任何 兼容 MCP 的客户端 —— 安全、受控地访问你的真实邮箱 —— 多账户(Microsoft Graph + IMAP)、日历、本地搜索索引、发件人 记忆,以及面向代理的权限模型。
不内置任何 LLM:智能来自你自己的代理。MCP 服务器只使用 stdio 传输,不开 网络端口。(可选的人工控制台会在 127.0.0.1 上提供一个本地 HTTP API。)
关于你的数据:GigaMail 把邮件索引、凭据、记忆和配置全部保存在你自己 的机器上 —— 我们不运行任何服务,也收不到任何数据。代理读取的邮件内容当 然会经过该代理及其模型提供商,适用他们各自的数据政策。请据此选择你的代理。
一分钟:控制台起草回复,数字取自你自己的文件,文档没有的地方就停下,未经你批准什么都不会发出 —— 无论是从控制台还是从你的代理。
gigamail archive)GigaMail 通过两个渠道发布:
桌面应用,Windows 与 macOS — 可从 gigamail.ai 或最新版本下载。面向人的控制台,内置 Python:一个安装包、无需前置依赖、 无需管理员密码,并会自动更新。
GigaMail-Setup.exe,已代码签名。证书较新,
首次启动时 Windows 可能仍提示"无法识别的应用":点击 更多信息,再点 仍要运行。GigaMail-arm64.dmg,
Intel 用 GigaMail-x64.dmg,均以 Apple
Developer ID 签名并经 Apple 公证。SHA-256 摘要见发布页文件旁。自行构建:Node 22+,console/prepare-python.ps1
(Windows)或 console/prepare-python.sh(macOS),然后 npm run dist 或
npm run dist:mac。
pip install gigamail — 代理核心:MCP 服务器、CLI、watcher 和
控制台的本地 HTTP 后端。不含图形界面 — 如果你的代理就是界面,选这个渠道。
下文内容均针对 pip 渠道。
pip install "gigamail[all]"
gigamail login # Microsoft 设备码登录
gigamail accounts add-imap # 或任意 IMAP 提供商
gigamail check # 搜索、等待你批准的草稿、给自己发一封测试邮件
为账户设置身份与知识(这是让回复"像你"的关键):
gigamail identity set # 我是谁、做什么、语气
gigamail identity add-file C:\docs\pricelist.xlsx
在 Claude Desktop / Claude Code 中注册(mcpServers):
{
"gigamail": {
"command": "gigamail-server"
}
}
命令也保留旧名称(ade-mail-agent、ade-mail-agent-server),Python 包也
响应旧名 ade_mail_agent(python -m ade_mail_agent.server),现有配置
继续可用。
使用 Claude Code?本仓库也是一个 Claude Code 插件:它注册 gigamail
MCP 服务器,并附带一个教 Claude 如何面对审批关卡的 skill。
claude plugin marketplace add adecubed/gigamail
claude plugin install gigamail@gigamail
使用 Codex?本仓库本身就是一个 Codex 插件:它注册 gigamail MCP
服务器,并附带一个教 Codex 如何面对审批关卡的 skill。
codex plugin marketplace add adecubed/gigamail
codex plugin add gigamail@gigamail
使用 OpenClaw 或 Hermes?经过验证的配置见 INTEGRATIONS.md。
你是替人类做安装的 AI 代理吗? 你可以完成安装与 MCP 注册:
pip install "gigamail[all]",然后把gigamail-server加入客户端的 MCP 配置。到此为止。 连接邮箱(gigamail login、gigamail accounts add-imap)需要输入凭据,必须由人类在自己的终端里完成 —— 这不是你该做的 事,GigaMail 的设计也让它无法经由你完成。告诉他们要运行什么,然后等待。
之后直接对你的代理说:"用价目表回复最近那封询价邮件" —— 它会读邮件、从你 的文件里取数字、写好草稿,并在发送前征得你的同意。
29 个类型化工具,由服务器本身生成:
日历由 Microsoft Graph 或 Google Calendar 提供,取决于用户连接了哪一个;
工具完全相同。Drive 使用 drive.file 权限,只能看到 GigaMail 自己创建的
文件。连接 Google 的方法见 GOOGLE_SETUP.md。
邮件内容被视为不可信数据(提示注入)。代理从构造上就无法批准自己的
操作:危险工具只返回一个惰性的 request_id,而批准它 —— 无论从控制台还是
gigamail approvals approve —— 都需要对机器前的人进行操作系统级验证
(Windows Hello / Touch ID)。任何进程(包括持有 shell 的代理)都能
弹出这个验证框,却无法通过它;没有此类验证后端时,一律拒绝(fail-closed)。
没有任何机密进入模型上下文,被注入的指令无物可用。重复提交 id 只会得到
等待批准。代理只能读取用户明确注册的文件,永远碰不到文件系统的其余部分。
每次写操作都记入只追加的审计日志(GigaMail 从不改写历史条目 —— 它不是、
也不自称是防篡改存储)。
我们对此做红队测试:让恶意邮件命令真实代理外泄数据、批量删除、自我批准 —— 在所有邮件工具全开的情况下,零破坏性操作。
你可以告诉 GigaMail:来自这些发件人(或这个文件夹)的邮件,用这些文档起草
回复。规则只能从 CLI(gigamail rules add)或控制台创建,且要经过与批准
相同的 Windows Hello / Touch ID 验证;gigamail watch 是执行规则的进程。
MCP 服务器保持被动,不存在任何能触碰规则的 MCP 工具:被注入的指令无法
打开自动驾驶。
gigamail desktop-setup 使其可点击;按钮只是打开批准流程,仍需 Hello),
以及 Telegram(gigamail telegram setup,用你自己的机器人:✅ 批准需
在 Hello 背后显式开启 --approve;❌ 拒绝、✏️ 要求修改 —— 且只接受来自
你那个会话的指令)。decided_by automode:<rule_id> —— 这份批准是
你创建规则时在 Hello 背后给出的,范围精确、必有过期时间、每日上限和按
发件人的冷却时间。通知照常发出。起草者(你自己的代理,经 claude -p)只产出回复正文:收件人、主题与
会话线程由 GigaMail 从来信中确定 —— 永远回给通过验证的发件人,绝不理会
Reply-To,也绝不使用草稿里写出的地址。确定性栅栏先行:DMARC 未通过 →
永不 auto;自动生成的邮件、邮件列表、no-reply 发件人、提供商的垃圾邮件判定、
可执行附件 → 一律不回复;新发件人的第一封邮件永远经过你;短时间内大量命中
会让规则自动暂停。详见 SECURITY.md。
gigamail 包只做邮件:账户、索引、搜索、两阶段发送、日历、知识文件、审计。
只对某一个行业有意义的功能放在核心之外,默认关闭,需要时才开启:
appointments(内置,默认关闭):把邮件和日历连接起来,从第一次回复
一直到跟进。
gigamail debrief
列出尚未回答的问题)。回答会写入该联系人的备注。real_estate(extras/real_estate):为回复房产门户
询盘的中介检查草稿中的户型,并按房源编号选择附件。GigaMail 就是在这里成长起来的。gigamail extensions list
gigamail extensions enable appointments # 需要 Windows Hello / Touch ID
gigamail extensions install real_estate # 装在数据目录中:应用更新后仍然保留
gigamail extensions enable real_estate
已开启但无法加载的扩展会停止自动草稿并通知人类,绝不会被悄悄跳过。
AGPL-3.0-or-later. 自由使用、研究、修改与分享。若你分发修改版 —— 或将 其作为网络服务运行 —— 必须以相同许可证提供其源代码。闭源商用许可可向版权 持有人洽询。
Your real mailbox and calendar for your agent (M365/IMAP); a human approves every send.
{ "mcpServers": { "io.github.adecubed-gigamail": { "command": "uvx", "args": [ "gigamail==0.3.4" ], "env": { "GIGAMAIL_ROOT": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: GIGAMAIL_ROOT
Gigamail ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Your real mailbox and calendar for your agent (M365/IMAP); a human approves every send.