Repository navigation
v0.2.0
Reply drafts, field-by-field draft updates, and a path for attachments too large to pass through tool arguments.
Staged attachments. stage_attachment_begin opens a staging area in the session and returns a one-time upload URL; curl -T <file> '<url>' carries the raw bytes straight to the Worker, so a 2MB file costs the assistant a few hundred tokens. stage_attachment_append takes base64 in chunks where no shell is available. Every attachments and inlineImages field accepts the resulting stagingId. A staging lives 24 hours; uploads are capped at 6MB and gated by a per-staging secret.
Reply drafts. create_draft takes replyToMessageId: the draft joins the original's thread, carries In-Reply-To and the References chain, quotes the original under the body, and derives the reply-all recipients, the send-as identity, and the Re: subject when they are not given. Threading holds in Gmail's own UI and in clients that thread on headers alone.
Draft updates keep what they are not given. update_draft changes only the fields passed. Recipients, subject, the body and its HTML alternative, files added by hand in the Gmail UI, inline images, and the thread the draft answers are read back and kept. A file that cannot be read back stops the update with an error.
27 tools · 250 unit tests. Each new flow also ran against live Gmail accounts, staging included, with a 1.9MB single-PUT upload.
Upgrading an existing deployment: git pull && bun run deploy. claude.ai caches connector tool schemas; reconnect the connector to see the staging tools.
日本語 https://github.com/mkpoli/gmail-mcp/blob/main/README.ja.md · 简体中文 https://github.com/mkpoli/gmail-mcp/blob/main/README.zh.md