manage_emailLABSCO SUMMARY
A dozen tools instead of a hundred: one per service, with the operation named inside the call.
Each service tool takes an operation argument rather than splitting into a dozen entries, so the list stays short while the arguments carry the work — the mail tool alone covers search, read, send, forward and labels. The three infrastructure tools are what make it usable for anything longer than a one-liner: compose in the scratchpad, stage files in the sandbox, chain steps with result references. The most useful safety feature is the scope choice: authorize an account read-only and a write is refused before the request leaves, with the re-authorization command in the error.
What it is
A server over Google Workspace — Gmail, Calendar, Drive, Docs, Sheets, Tasks, Meet and Contacts — with one tool per service plus three that make multi-step work possible: a file sandbox, a compose-and-deliver scratchpad, and bulk execution. It runs on your machine with your own OAuth client, and holds a token per account.
What you get
- Gmail through its own search syntax: read, send, reply and reply-all, forward, triage, trash, labels, threads and attachments
- Drive searched, uploaded to, downloaded from, copied, moved, exported, shared with a person or a whole domain, and commented on
- Calendar events listed, created with attendees and a Meet link, added in natural language, and free-busy checked before a time is proposed
- Docs read, created, appended to and find-and-replaced; Sheets read and written by range with tab management; Google Tasks lists and their tasks
- Contacts looked up across your saved contacts, addresses you have only corresponded with, and your organization's directory
- Past Meet conferences with their participants, transcripts, recordings and smart notes
- A sandbox with nested paths that acts as the exchange point for attachments, downloads and exports
- Multi-line content composed and edited by line or JSON path then delivered to any target, and several operations chained in one call with $N.field references — or one operation applied to many items in a single Google request where Google publishes a method for it
- Per-account read-only authorization: ask for read scopes at consent time and the token itself cannot send, edit or delete
Requirements
Node 22.12 or newer, and your own Google OAuth 2.0 client of type Desktop app with the APIs you want enabled — Gmail, Calendar, Drive, Sheets, Docs, Tasks, Meet, and the People API for contacts. Its client id and secret go in the environment, and each account is then authenticated once through the account tool, which opens a browser. Tokens live on your own disk under your home directory; there is no hosted service in the middle. Meet transcripts and recordings need Workspace Business Standard or higher. Apache-2.0, with no paid tier held back.
Setup effort
One command plus credentials — npx -y @aaronsb/google-workspace-mcp, then supply credentials
USE CASES
01
Sending a long message you actually edited first
Compose the body in the scratchpad, edit it by line or by JSON path until it reads right, then deliver it as the email. The draft never has to be reconstructed from scratch on each revision.
02
Getting a Drive file back out as an attachment
Download the file into the sandbox, which is the exchange point the other tools read from, then attach it to the message going out.
03
Working across a personal and a work account in one session
Authenticate each account once, check which are still valid and what scopes they carry, then address the right one per call rather than switching clients.
04
Letting an agent read your mail but never send it
Re-authorize that account with read access for the services in question; the token Google issues cannot write, whatever the agent decides to try.
05
Catching up on a meeting you missed
Find the conference, then read what it left behind — participants, the transcript, the recording and the smart notes — instead of asking someone to summarise it for you.
06
Running a multi-step change without approving each call
Chain the operations in order and let each one refer to the previous result, so a find-then-file-then-remind sequence is a single round trip rather than four.
12 tools
Listed in project docs. Your client may show a different list.
manage_calendarmanage_drivemanage_sheetsmanage_docsmanage_tasksmanage_meetmanage_contactsmanage_accountsmanage_scratchpadmanage_workspacebulk_operationsBEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation. queue_operations is the older name for bulk_operations and still works as an alias. The 95 advertised operations run inside these tools; they are not separate tools.
Requires
- npx on PATH
- Node 22.12 or later
- GOOGLE_CLIENT_ID in your environment
- GOOGLE_CLIENT_SECRET in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @aaronsb/google-workspace-mcpMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add google-workspace \
-e GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID> \
-e GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET> \
-- npx -y @aaronsb/google-workspace-mcpAny MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"google-workspace": {
"command": "npx",
"args": [
"-y",
"@aaronsb/google-workspace-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "<YOUR_GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<YOUR_GOOGLE_CLIENT_SECRET>"
}
}
}
}
