Google MCP
# Google MCP
A local MCP server for a personal Google account: Gmail, Google Calendar, and Google Drive through Google's public APIs. The code and OAuth tokens stay on your computer; requests go directly to Google over HTTPS.
> [!NOTE]
> This is a personal project, shaped around the author's own use: a small, fixed set of tools with deliberately narrow permissions. For broader coverage, see [Google Workspace CLI](https://github.com/googleworkspace/cli), which uses a similar local OAuth setup but exposes every Google Workspace API through Google's Discovery Service.
What it can change:
- **Gmail** messages are read-only. Drafts can be created and edited, with attachments, but are never sent; you send them from Gmail. Google has no drafts-only permission, so the authorization technically allows sending, but no tool does it.
- **Unsubscribe**: one-click unsubscribe from mailing lists that support it sends a request to the sender's server, the only request that does not go to Google.
- **Calendar** tools create, update, delete, and RSVP to events. Changes to shared events and RSVPs can notify other people.
- **Drive** reads cover your whole Drive; uploads and updates only touch files this app created.
## Tools
- Gmail: `list_emails`, `read_email`, `read_thread`, `download_attachment`, `list_senders`, `unsubscribe_one_click`, `list_drafts`, `read_draft`, `create_draft`, `update_draft`
- Calendar: `list_calendars`, `list_events`, `get_event`, `create_event`, `update_event`, `delete_event`, `respond_to_event`
- Drive: `search_files`, `get_file`, `download_file`, `upload_file`, `update_file`
## More
- [INSTALL.md](INSTALL.md): Google Cloud setup, install, authorization, updates, local files, removal.
- [DESIGN.md](DESIGN.md): tool behavior, scopes, API calls, and security.
- [CHANGELOG.md](CHANGELOG.md): releases, including which ones add scopes.
TDQS
Scored across 20 tools
The tools are mostly cleanly separated by service and action: Gmail read/list/draft tools, Calendar event tools, and Drive file tools each have distinct targets. Minor overlap exists between read_email and read_draft because read_email also works on a draft message_id, and download_attachment vs download_file could be briefly confused, but descriptions clarify the boundaries.
All tools use clear snake_case with a verb_noun pattern: list_emails, read_thread, create_draft, update_event, search_files, download_file, etc. The single phrase-style name respond_to_event is still readable and consistent with the overall convention.
Twenty tools is reasonable for a server spanning Gmail, Calendar, and Drive, where each service needs multiple read/write operations. It is slightly heavy compared with a single-domain server, but the count is justified by the three distinct Google Workspace areas.
Calendar coverage is strong, and Gmail/Drive cover the core read, draft/upload, update, and download workflows. There are some notable gaps such as no Gmail draft deletion, no Drive deletion or move/rename, and limited listing outside search, but agents can work around most of these for the stated draft-and-file-transfer focus.