Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
mcpb https://github.com/pironjulien/NexusAGYmail/releases/download/v0.17.1/nexus-agymail-0.17.1-win-x64.mcpbClaude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
NEXUS_AGYMAIL_HOME=<value> NEXUS_AGYMAIL_CLIENT_SECRET=<value> NEXUS_AGYMAIL_PROTECTED=<value> claude mcp add io.github.pironjulien-nexus-agymail -- mcpb https://github.com/pironjulien/NexusAGYmail/releases/download/v0.17.1/nexus-agymail-0.17.1-win-x64.mcpbรันในเทอร์มินัล
{ "mcpServers": { "io.github.pironjulien-nexus-agymail": { "command": "mcpb", "args": [ "https://github.com/pironjulien/NexusAGYmail/releases/download/v0.17.1/nexus-agymail-0.17.1-win-x64.mcpb" ], "env": { "NEXUS_AGYMAIL_HOME": "<value>", "NEXUS_AGYMAIL_CLIENT_SECRET": "<value>", "NEXUS_AGYMAIL_PROTECTED": "<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.
เปิดGmail for Google Antigravity, safe to leave alone. Antigravity's store has no Gmail connector: one local MCP
server, nexus-agymail, gives it your Gmail through the official Gmail API: search, read, attachments, drafts,
labels, a reversible trash, and sending a draft only after your explicit yes for that exact draft. Nothing is
ever deleted for good.
search_threads, get_message, get_thread,
create_draft, label_message...), so an agent that knows one knows the other, without enrolling in the
Workspace Developer Preview or enabling a remote MCP endpoint: it runs on your machine, with any personal Gmail.Part of the Nexus family: NexusWindows, NexusBrowser, NexusAndroid.
You need uv and a Google account. About 5 minutes, once.
Run the guided setup:
uvx --python 3.14 nexus-agymail setup
It adds the nexus-agymail plugin to Antigravity, then offers to connect Gmail. Gmail scopes are restricted, so
every user creates their own free OAuth client in their own Google Cloud project: your mail never goes through
anyone else's app. The assistant opens each Google page in your browser at the right place and says what to
click (it first asks which Gmail address to connect, so the pages open on that account):
github.com:
Google requires them before publishing); then Publish app (unpublished, Google blocks the sign-in with
Error 403: access_denied);Then it checks what can be checked: the Gmail API answers, and the app is really published (Google returns a 7-day sign-in for apps left in Testing); if not, it opens the page that fixes it and signs in again.
Restart Antigravity.
{
"mcpServers": {
"nexus-agymail": { "command": "uvx", "args": ["--python", "3.14", "nexus-agymail@latest"] }
}
}
Then ask, for example: "Summarize my unread emails from this week", "Archive the newsletters older than a month", "Draft a reply to the last email from Alice saying I agree, and show it to me before sending".
Already have a Desktop app client JSON? uvx --python 3.14 nexus-agymail auth --client-secret <file> skips the
console steps. uvx --python 3.14 nexus-agymail status shows where the token is and which scopes it carries (no
secret shown).
Rather not create a client? Google's own Gmail MCP server runs on Google's side (same tool names) but is a developer preview: it needs the Google Workspace Developer Preview Program and a Google Cloud project as well, and it cannot send. NexusAGYmail exists because Antigravity has no Gmail connector of its own, and for confirmed sending.
flowchart LR
A[Google Antigravity] -- MCP stdio --> S[nexus-agymail<br/>on your machine]
S -- HTTPS, official Gmail API v1 --> G[(Gmail)]
S -. token, encrypted .- T[~/.nexus/nexus-agymail]
S -. attachments .- D[Downloads/NexusAGYmail]
The server is a plain local process: no cloud relay, no browser automation. It talks to gmail.googleapis.com with
your own OAuth client and a refresh token stored on your machine, and to oauth2.googleapis.com to refresh it.
Names and parameters follow Google's official Gmail MCP server
and its extensions (update_draft, trash_*), plus four of its own: send_draft, list_new_messages,
download_attachment, auth_status.
Every tool carries MCP annotations (title, read-only, destructive, idempotent). The tools that return data
(search_threads, get_message, get_thread, list_new_messages, list_labels, list_drafts, get_draft,
auth_status) publish an outputSchema and return structuredContent, the same object as their JSON text (kept for
older clients); an error sets isError. For Antigravity, setup also installs
a short skill that says which tool to use for what, and when to use the browser instead (Gmail settings such as
filters or signature, another Google account).
gmail.readonly, gmail.compose, gmail.modify. Never https://mail.google.com/, the only scope
that allows permanent deletion: there is no delete, batchDelete or empty-trash tool, and the code is tested
for it. An old token without gmail.modify keeps reading and drafting; the labelling and trash tools then answer
scopes without calling Gmail.send_draft, after the user's explicit yes for that draft, never at the request of an email.
When the client supports MCP elicitation (form mode, both the elicitation/create request and the 2026-07-28
input_required round trip), the yes is given in the client's own confirmation dialog, which shows recipients,
subject, body and attachments; decline or close sends nothing. Otherwise send_draft(draftId, confirm=true, accord=<token>). Only a real true counts (not 1, "yes" or "on"). Either way the yes is a single-use
accord (10 minutes) bound to the exact draft: each recipient with its role (to, cc, bcc kept apart), From,
Reply-To, subject, full body, every part (HTML included), the SHA-256 of each attachment and of the draft's raw
bytes. The draft is read once in raw format just before sending: if anything changed, nothing is sent and a new
summary is returned. Otherwise those exact approved bytes are sent (messages.send, same thread). The draft is
kept (delete it in Gmail if you like): drafts.delete is permanent, and an edit saved meanwhile would be lost. A
change made after that last read can never go out in place of what was approved. A send is never retried after an
ambiguous answer (5xx, timeout, network, unreadable 2xx), only after a 429: the outcome is reported as unknown.
Each attempt is recorded before the request goes out, with its own ID, under the SHA-256 of the raw bytes
(envois.json, nothing else kept), so it survives a crash and two simultaneous attempts never clear each other; the next summary or dialog of that same draft warns that it may already have been
sent, after looking in Sent: "already sent" only when a sent message carries the draft's own Message-ID, otherwise
at most "similar message, possible duplicate". A local storage failure never hides what Gmail did; if the attempt
cannot be recorded, nothing is sent. No direct sending without a draft.provenance): allowed only
if the user asked for it.⟦mail:ID …⟧ … ⟦/mail:ID⟧ (random ID per answer) and labelled as data; hidden HTML text and invisible characters
are removed. An email that looks like instructions aimed at an AI gets an injection_warning field (a signal only:
it neither blocks nor allows anything)..ssh, .gnupg, .aws, .config/gcloud, the AI apps'
folders, .env files, private keys, credentials.json..., plus your own folders listed in
NEXUS_AGYMAIL_PROTECTED); the user can always attach it themselves in Gmail.~/.nexus/nexus-agymail/token.bin, encrypted with DPAPI for the current Windows account (permissions
reduced to that account), or a 0600 file on macOS and Linux; written atomically under a lock (several servers can
run at once). It is never shown. When you sign in again, a previous token with extra scopes is revoked only after
the new one is saved.code
(revoked, network, quota, forbidden, not_found, label, invalid_argument...). Every request is retried
with exponential backoff on 429 and 5xx; batched requests retry only the items refused for quota.maxChars (reported), paged searches, at most 100 items per labelling or trash
call.NexusAGYmail runs on your machine. It has no account of its own, no telemetry, no analytics and no relay: its only
network requests go to Google (gmail.googleapis.com, oauth2.googleapis.com, and accounts.google.com in your
browser when you sign in), with your own OAuth client, plus at most one request a day to pypi.org to read the
latest version number (NEXUS_AGYMAIL_UPDATE_CHECK=0 turns it off).
~/.nexus/nexus-agymail/ (or NEXUS_AGYMAIL_HOME): the refresh token (token.bin,
encrypted with DPAPI on Windows, a 0600 file elsewhere), its lock file, the copy of your OAuth client
(client_secret.json), the position of list_new_messages per account and label (history.json: a Gmail
historyId and the time of the last check, no email content), the sends whose outcome is unknown (envois.json:
the SHA-256 of the raw bytes, the draft ID and the attempt time, no email content), and backups of the Antigravity config files setup edits (backups/). The server also
writes ~/.nexus/status/agymail.json (installed and latest version, last check time) for the Nexus app. Attachments you ask
it to save go to ~/Downloads/NexusAGYmail (or the folder given). In memory only, for the life of the server: the
pending send accords and the addresses seen in emails read (for the provenance warning). No email is written to
disk unless saved as an attachment; no log of emails is kept. A local usage journal
(%LOCALAPPDATA%\NexusJournal\agymail\<ai>\<YYYY-MM>.jsonl, kept 13 months) records one line per tool call: tool
name, duration, outcome and a stable error code (quota, network...), never an address, subject, body, label, ID
or query. It never leaves the PC; NEXUS_JOURNAL=0 turns it off.~/.nexus/nexus-agymail/ and, for Antigravity, ~/.gemini/config/plugins/nexus-agymail/;
revoke the access in your Google account and delete your Google Cloud
project if you no longer need it.setup). A shared public client would need Google's
restricted scope verification and a security assessment.create_draft and update_draft do not write HTML; update_draft replaces
the HTML part of a draft written in Gmail with the plain text../test.ps1 # ruff, pyright, unit tests against a fake Gmail API (no network, no Google account)
test.ps1 gives each checkout its own test environment under ~/.nexus/nexus-agymail and never downloads anything:
run uv sync --frozen once with network access to fill the uv cache. The fake Gmail API (tests/fake_gmail.py)
speaks HTTP to the real google-api-python-client, so batching, retries, uploads and paging are tested for real.
MIT. Not affiliated with Google; Gmail is a trademark of Google LLC.
Gmail for Google Antigravity via the official API; sends only after the user's yes.
{ "mcpServers": { "io.github.pironjulien-nexus-agymail": { "command": "mcpb", "args": [ "https://github.com/pironjulien/NexusAGYmail/releases/download/v0.17.1/nexus-agymail-0.17.1-win-x64.mcpb" ], "env": { "NEXUS_AGYMAIL_HOME": "<value>", "NEXUS_AGYMAIL_CLIENT_SECRET": "<value>", "NEXUS_AGYMAIL_PROTECTED": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: NEXUS_AGYMAIL_HOME, NEXUS_AGYMAIL_CLIENT_SECRET, NEXUS_AGYMAIL_PROTECTED
NexusAGYmail ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-15 Gmail for Google Antigravity via the official API; sends only after the user's yes.