Projects / mcp-gsuite
Connect an agent to Google Workspace, with outbound mail confined to drafts.
Gmail search, triage, threading, and label management over the full Gmail query syntax, with batch relabelling in a single API call. Outbound mail is deliberately drafts-only — the server composes, the person reviews in Gmail and clicks Send. Deletion is restricted to recoverable trash; the permanent-delete endpoints are not exposed at all. Calendar and Drive tools follow on the same client, scopes, and access gate.
Public mcp repository · source
The problem
What this is for.
Giving an agent your mailbox is easy. Giving it your mailbox without also giving it the ability to send mail in your name, or to destroy it, is the part that usually stops people — so this server draws that line in the tool surface itself rather than in an instruction the agent might not follow.
Whose problem
Whether it is yours.
You want this if you want an agent searching, triaging and drafting in Gmail, and you are not willing to let it press Send. If you want autonomous outbound mail, this is deliberately the wrong server.
Capabilities
What it actually does.
- Search and read at message and thread level, over the full Gmail query syntax rather than a simplified subset.
- Triage: label, unlabel, archive, mark read or unread, with batch relabelling done in a single API call.
- Labels: list, create, update and delete.
- Drafts: create, read, update, list and delete — which is the entire outbound surface.
- Attachment metadata and download, and raw message access when the parsed form is not enough.
- An access gate derived from each tool's MCP annotations, so the default registration exposes read-only tools and nothing else.
State
How finished it is.
Public source, not published to any package registry. Gmail is fully implemented; calendar and Drive tools follow on the same shared client, scopes and access gate. Clone it, build it, supply your own Google Cloud OAuth credentials, and register the built server with your MCP client.
Using it
How to start.
Not yet published to a registry. Clone the repository, supply your own Google Cloud OAuth credentials, and register the built server with your MCP client.
Boundaries
What it deliberately does not do.
Outbound mail is deliberately drafts-only: the server composes, you review in Gmail and click Send. Deletion is restricted to recoverable trash, and the permanent-delete endpoints are not exposed at all. Access level is a boot-time decision, so raising it is an explicit act rather than something an agent can talk its way into.
Authority
What this repository owns.
A Google Workspace adapter with a deliberately narrowed write surface.
That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.
Nearby
Other projects of the same kind.
mcp-ki-kb-fs— Give an agent scoped read and write access to local knowledge-base directories.mcp-git-audit— Audit a whole tree of Git repositories, read-only until an operator says otherwise.mcp-housekeeping-claude— Audit and safely clean the filesystem state Claude applications accumulate.mcp-m365— Connect an agent to Outlook and OneDrive through the Microsoft Graph API.
See every public project, or go straight to the released command-line tools.