The Gmail API lets you view and manage Gmail mailbox data like threads, messages, and labels.
Walkthrough · illustrative mockups
Every path starts on this GitHub repo and ends the same place: someone typing “what's unread in both my inboxes?” and getting both. What changes is how much of the setup you do yourself.
Path A Planned
Download one file, drag it onto Claude Desktop, sign in to Google in chat. No terminal, no Google Cloud.
Path B Planned
Same install, but they create their own Google Cloud app first and hand the installer its key file.
Path C Available now
Clone, npm install, run the login script in Terminal, register with Claude Code or Desktop. The developer path — and the one that works today.
Side by side
| A · One-click | B · Own Google keys | C · From source | |
|---|---|---|---|
| Who it's for | Anyone with Claude Desktop | Privacy-minded users, or anyone past your cap | Developers and Claude Code users |
| Time | ~3 min | ~25 min (20 is Google Cloud) | ~45 min |
| Terminal | Never | Never | Yes — clone, install, auth, register |
| Google Cloud | No | Yes, one time | Yes, one time |
| Whose OAuth app | The maintainer's, bundled in the file | Theirs | Theirs |
| User cap | 100 total, shared across everyone on the maintainer's app | None | None |
| Exists | Planned · v1.0 | Planned · v1.0 | Today |
Search, read and draft across more than one Gmail account. Every tool asks which account.
The app is requesting access to sensitive info in your Google Account. Until the developer verifies this app with Google, you shouldn't use it.
Continue only if you understand the risks and trust the developer.
Go to gmail-multi (unsafe)The Gmail API lets you view and manage Gmail mailbox data like threads, messages, and labels.
Your app will be available to any user with a Google Account.
~ % git clone https://github.com/DavidOloyede/gmail-multi-mcp.git ~/gmail-mcp-server Cloning into '/Users/you/gmail-mcp-server'... ~ % cd ~/gmail-mcp-server gmail-mcp-server % npm install added … packages, and audited … packages in 4s found 0 vulnerabilities gmail-mcp-server % node --version v22.x gmail-mcp-server % ▍
~ % mkdir -p ~/.gmail-mcp && chmod 700 ~/.gmail-mcp ~ % mv ~/Downloads/client_secret_*.json ~/.gmail-mcp/credentials.json ~ % chmod 600 ~/.gmail-mcp/credentials.json ~ % ls -la ~/.gmail-mcp drwx------ you staff . -rw------- you staff credentials.json
gmail-mcp-server % node src/auth.js work Authorizing "work" 1. Open this URL (use an incognito window for the 2nd account): https://accounts.google.com/o/oauth2/v2/auth?access_type=offline&scope=… 2. You will hit "Google hasn't verified this app" — click Advanced → Continue. Waiting for you to finish in the browser... ↳ browser: choose account → Advanced → Continue (screens A5–A7) Saved token to ~/.gmail-mcp/token-work.json (chmod 600). gmail-mcp-server % node src/auth.js personal # incognito this time
gmail-mcp-server % claude mcp add --scope user gmail-multi -- node "$(pwd)/src/index.js"
Added stdio MCP server gmail-multi with command: node /Users/you/gmail-mcp-server/src/index.js to user config
> /mcp gmail-multi ✔ connected 4 tools gmail_search · gmail_get_message · gmail_list_labels · gmail_create_draft > what's unread in both inboxes this week? ⏺ gmail-multi · gmail_search account: "work" is:unread newer_than:7d ⏺ gmail-multi · gmail_search account: "personal" is:unread newer_than:7d Work — 3 unread, one needs a reply today. Personal — 7 unread, mostly promotions; one from your landlord. (example output)
Where this is going
| Version | What it adds | Install path | Status |
|---|---|---|---|
| v0.1 | Search, read and list labels across named Gmail accounts — two by default, more by editing one file. Drafting needs one extra scope. | C · from source | Available |
| v0.2 | Send mail from a chosen account; account list moves from code into a config file | C · from source | Planned |
| v0.3 | Reply, forward, labels, trash, spam — parity with Claude's built-in Gmail tools | C · from source | Planned |
| v1.0 | Sign in from chat instead of Terminal; packaged as a single .mcpb file | A and B | Planned |
Screens in this walkthrough are illustrative mockups of Google, GitHub and Claude Desktop, not screen captures. Wording on the real screens may differ.
Arrow keys to step · each screen replays its clicks when it opens