multi-google-calendar-gmail-mcp
This server provides multi-account access to Google Gmail and Calendar services, allowing an MCP client (like Claude) to manage emails and calendar events across multiple Google accounts simultaneously.
Account Management
List connected accounts (
accounts_list): See all connected Google accounts and their aliases/nicknamesDiagnose setup (
check): Verify credentials, connected accounts, and API connectivity
Gmail
Search emails (
gmail_search): Use full Gmail query syntax (e.g.,from:,subject:,is:unread,has:attachment) across one or all connected accountsRead emails (
gmail_read): Fetch the full body of a specific message by IDList labels (
gmail_labels): View all label names for a given accountBatch-modify messages (
gmail_modify): Add/remove labels, archive, or mark up to 500 messages as read in one call (non-destructive — no deletion or trash)Create drafts (
gmail_draft): Compose a draft email without sending itSend emails (
gmail_send): Send an email from a connected account (with CC support; confirm with user first)
Google Calendar
List calendars (
calendar_list): View all calendars across one or all connected accountsList events (
calendar_events): Retrieve events within a date/datetime range across one or all accountsCreate events (
calendar_create_event): Create calendar events with optional location, description, attendees, and real email invitations (confirm with user first)
Configurable Access: Optionally restrict tool access or account visibility by editing a config.json file. Multiple accounts can be addressed by nickname or swept all at once using an "all" command.
Provides tools for searching, reading, labeling, modifying, drafting, and sending emails across multiple Gmail accounts.
Provides tools for listing calendars, retrieving events, and creating events with attendee invitations across multiple Google Calendar accounts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@multi-google-calendar-gmail-mcp find unread emails across all my accounts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
multi-google-calendar-gmail-mcp
One small Python file that gives Claude (or any MCP client) Gmail and
Google Calendar across as many Google accounts as you want — a personal
Gmail, three Workspace domains, whatever. Each account gets a nickname;
every tool takes a nickname or "all" to sweep the whole fleet in one call.
"find every unread invoice across all five inboxes and label them Bookkeeping" — one tool call.
Why this one
Multi-account is the whole design, not a bolt-on. Most self-hosted Gmail MCPs authenticate one account. Here, connecting another account is one command + one browser click, and cross-account operations are native.
Minimal. One readable
server.py, three dependencies. If you want to know what it does, you can just read it.Bring your own credentials. Nothing is hosted, nothing phones home. You create your own (free) Google Cloud OAuth client, and your account keys live in a git-ignored folder on your machine. This repo never sees them.
Pairs naturally with apple-suite-mcp: that one reads whatever your Mac's built-in apps already see (zero setup, macOS only); this one speaks Google's APIs directly (real labels, batch operations up to 500 messages, drafts, calendar invites with attendees) and runs anywhere Python runs — including a headless Linux box.
Related MCP server: gmail-mcp
Setup
Easy mode — let your AI install it
If you use Claude Code (or any coding agent), paste this and let it drive:
Read https://github.com/travisthetrashpanda/multi-google-calendar-gmail-mcp and install it for me: clone it, walk me through the one-time Google Cloud credential setup in its SETUP.md, help me connect my accounts with its
connectcommand, and register it with my MCP client.
The agent handles the fiddly parts and can diagnose failures with the
built-in check command; you just click Allow in the browser when Google
asks. (Sensible to read what you're installing first — it's one Python file.)
Manual mode
Requires uv (brew install uv on macOS).
git clone https://github.com/travisthetrashpanda/multi-google-calendar-gmail-mcp.git ~/multi-google-calendar-gmail-mcpOne-time Google Cloud setup (~15 min, free): follow SETUP.md — create a Cloud project, enable the Gmail and Calendar APIs, publish the consent screen (avoids 7-day token expiry), create a Desktop-app OAuth client, and drop
credentials.jsonin this folder. Heads-up: Google rejects app names containing the word "Google".Connect the accounts you choose (repeat per account, any alias you like — only accounts you connect are ever visible):
cd ~/multi-google-calendar-gmail-mcp uv run python server.py connect work uv run python server.py connect personalChanged your mind?
uv run python server.py disconnect workdeletes that account's key.Verify:
uv run python server.py checkRegister with your MCP client — e.g. Claude Code:
claude mcp add --scope user google -- uv run --directory ~/multi-google-calendar-gmail-mcp python server.pyor in a JSON MCP config:
{ "mcpServers": { "google": { "command": "uv", "args": ["run", "--directory", "/Users/YOU/multi-google-calendar-gmail-mcp", "python", "server.py"] } } }
Tools
Area | Tools |
Accounts |
|
Gmail |
|
Calendar |
|
Test any tool from the command line:
uv run python server.py test gmail_search '{"query": "is:unread", "account": "all", "limit": 5}'Scoping access (optional)
You already control access by choosing what to connect — but if you want a
client to see only a subset of connected accounts (or to remove tools
entirely), copy config.example.json to config.json:
{
"accounts": ["work", "personal"],
"disabled_tools": ["gmail_send"]
}Accounts not listed become invisible to every tool; tools in
disabled_tools are never even registered with the MCP client. Omit a key
(or the whole file) to allow everything. check reports active scoping.
Safety notes
There is deliberately no delete/trash tool — the most destructive operation is archiving (removing from inbox), which is reversible.
gmail_sendand attendee invitations send real email; MCP clients should confirm with the user first.credentials.jsonandtokens/are git-ignored. Treat thetokens/folder like passwords — don't put it in cloud-synced directories.
Credits
Sibling project of apple-suite-mcp; the two split the work of giving an AI assistant a complete view of your accounts — locally-visible vs. API-native.
Say thanks
This project is free to use, no strings attached. If it's useful to you, a ⭐ on this repo or a shout-out to @travisthetrashpanda is always appreciated — and if you build something on top of it, a link back here helps others find it.
License
MIT
Available Tools
11 toolsaccounts_listA
List connected Google accounts (alias -> email).
Inputs: no named parameters.
calendar_create_eventA
Create an event, optionally inviting attendees by email (Google sends real invitations — confirm with the user first when inviting).
Inputs: end (required), start (required), title (required), account (required), +5 more.
calendar_eventsA
List events between two ISO dates/datetimes across one or all accounts. calendar_id defaults to each account's primary calendar.
Inputs: end (required), start (required), account, calendar_id. Returns: result
calendar_listC
List calendars for one or all connected accounts.
Inputs: account. Returns: result
checkA
Diagnose setup: credentials file, connected accounts, and whether each account's Gmail API actually responds.
Inputs: no named parameters.
gmail_draftA
Create a draft (does NOT send). Safer default than gmail_send.
Inputs: to (required), body (required), account (required), subject (required), +1 more.
gmail_labelsC
List label names for one account.
Inputs: account (required). Returns: result
gmail_modifyA
Batch-modify up to 500 messages in one account: add/remove labels (created automatically if new), archive (leave the inbox), mark read. Reversible — nothing is deleted.
Inputs: account (required), message_ids (required), archive, mark_read, +2 more.
gmail_readC
Read one message's full body by the id from gmail_search.
Inputs: account (required), message_id (required), max_chars.
gmail_searchA
Search mail with Gmail's full query syntax (from:, subject:, is:unread, older_than:1y, has:attachment, ...). account is an alias, an email, or "all" for every connected account.
Inputs: query (required), limit, account. Returns: result
gmail_sendC
Send an email from one account. Always confirm with the user first.
Inputs: to (required), body (required), account (required), subject (required), +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clear, distinct purpose. Calendar and Gmail tools are separated by prefixes (calendar_, gmail_), and actions like create, list, search, read, send are unique. No two tools overlap in functionality.
Most tools follow a (prefix)_verb_noun pattern (e.g., calendar_create_event, gmail_search). However, 'accounts_list' and 'check' break the pattern by lacking a service prefix, creating a minor inconsistency.
11 tools is well-scoped for a combined Calendar+Gmail server. It covers essential operations for both services without being excessive or too sparse.
Gmail side is fairly complete (search, read, send, draft, modify labels). Calendar side has significant gaps: it lacks update and delete for events, which would be needed for full lifecycle management.
Related MCP Connectors
Multiple Google accounts (Gmail, Calendar, Drive, Contacts, Tasks) in one Claude connector.
Multiple Google accounts (Gmail, Calendar, Drive, Contacts, Tasks) in one Claude connector.
Multiple Gmail accounts, editable Google Sheets & Docs for AI agents. Deny-by-default access rules.
One MCP connector with one shared Memory for all your AI assistants (encrypted at rest, on by default, managed in the Fezola app), plus every account you own: Gmail, Outlook.com, iCloud and any IMAP mailbox, Google Chat, Telegram (read-only), Google Calendar (read and write), Notion, and three ad platforms: Google Ads, Microsoft Advertising and OpenAI Ads. Several accounts per tool, one connector for Claude and ChatGPT, nothing to install. Email is saved as drafts by default; ad changes are checked first where supported and new campaigns start paused.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Gmail and Google Calendar using the MCP protocol, supporting multiple Google accounts, email management, and calendar operations through natural language.33MIT
- FlicenseNot gradedqualityBmaintenanceEnables interacting with multiple Gmail accounts through a single MCP server, supporting search, labels, drafts, and thread management with per-account OAuth.1-
- AlicenseNot gradedqualityFmaintenanceEnables connecting Claude to multiple Gmail accounts at once, allowing each tool call to target a specified mailbox for reading, sending, and managing email.MIT
- AlicenseNot gradedqualityBmaintenanceEnables simultaneous management of multiple Gmail accounts through MCP, allowing per-account reads and writes with verified labels and parallel search across all mailboxes.13 npmMIT