Summary
An agent can run a mailbox, not only read it.
What it takes off you is the handling: find the thread, label it, draft the reply, send it — and the parts nobody opens the settings page for, like a filter, a forwarding address or a vacation responder, are the same kind of call as the rest.
What it is
A Gmail server that follows the Gmail API surface closely rather than reducing it: the mailbox, and also the settings most integrations leave out — filters, forwarding, aliases, delegates, S/MIME.
What you get
- List, read, relabel, trash and permanently delete messages — one at a time or a batch in a single call
- The same over threads, and attachments fetched by message
- Drafts created, listed, read, deleted and sent
- Labels created, updated, patched and deleted, with colours and visibility
- Settings: filters, forwarding addresses and auto-forwarding, IMAP and POP, language, vacation responder, delegates
- Send-as aliases including signature and verification, and S/MIME configs per alias
- The account profile, and a mailbox watch that can be started and stopped
Requirements
Npx on your PATH, and a Google account authorized to it. Every tool checks the OAuth2 credentials before it reaches Gmail, so the authorization is what has to be in place first.
Setup effort
One command plus a key — npx @shinzolabs/gmail-mcp, then supply credentials