MCP server
Gmail
High-risk mailbox access that should begin only with a new test account and sending disabled.
Published by the company that makes the product.
What it can access
OAuth can expose message bodies, attachments, contacts, and metadata. Write permission can create drafts or send mail.
Security note
Developer Preview and high impact. Do not connect a mailbox used for source, legal, or personnel correspondence. Start with a new test account and disable sending.
Do you need it?
Usually no. Search or draft manually unless email volume is a proven operational problem and an administrator can supervise access.
Capability and permissions
Gmail access can expose message bodies, attachments, contacts, metadata, and years of correspondence. Write tools can create drafts or send messages.
Least-privilege setup
As of 2026-09-01, Google’s Workspace MCP service is Developer Preview. Use a new workshop Gmail account containing two invented messages. Do not connect a staff mailbox. Keep send actions disabled or unavailable.
Harmless success test
Ask the client to find the invented message with subject MCP TEST and draft, but not send, a reply to the same test account. Confirm the draft is correct and unsent.
Disable, revoke, remove
Disconnect in the AI client, revoke Google Account access, delete the draft and test messages, then remove the workshop account if it is no longer needed.
When not to connect
Never connect a mailbox used for sources, survivors, legal matters, personnel, safeguarding, passwords, recovery codes, or confidential donor communication.