Gmail MCP for Claude Code: Multi-Account Setup + 5 Workflows
The multi-account Gmail MCP setup, prompts, and workflows behind my 40-second morning brief.
If you want to use Gmail with Claude Code, the hard part is not connecting one inbox. It is setting up multiple Gmail accounts without constant re-auth, account mixups, or broken routing. This guide shows the multi-account Gmail MCP setup, the exact install flow, and the workflows I use for receipts, inbox triage, subscriber alerts, daily email briefs, and more.
How many Gmail accounts do you have? And how many unread emails are in there?
I have four. Personal, newsletter, business, payments.
This morning I asked Claude Code to scan all four and return only what needed my attention. It came back with 7 items. Two Ahrefs alerts. An n8n workflow that had been in a crash loop for two days. A Stripe payout. A reader question. Two emails that needed replies.
That 7 came out of 918 unread sitting in inboxes, and 3,353 when you count everything that bypasses the inbox through filters.
Screenshot of my unread-email totals across four Gmail accounts.
The brief took 40 seconds.
Before I explain why this became necessary, I’m curious where you sit:
The reason I needed this is tax season. I have income from Medium, Substack, Gumroad, my own apps, Stripe, and occasional affiliates. Some business deductions come through personal purchases too: Amazon orders, hosting bills, app development tools, random software receipts. It all adds up, and it all lands in different accounts for different reasons.
Getting everything in one place used to mean logging into each account separately, searching, exporting what I could, and cross-referencing dates. Hours of work that was really just moving data between tabs.
A single Gmail MCP connection didn’t solve that. (If you’re new to MCP, I have written about the Best MCP Servers for Claude Code to help you get the bigger picture.)
The problem here wasn’t access. It was switching. If I had to query one account, jump to another to match it up, then verify in a third, I was still doing the context switching myself. What I wanted was Claude moving through each account in sequence, fetching what I needed, storing it locally, and matching across all of them without me leaving the session.
Getting Gmail into Claude Code for one account is straightforward. The multi-account case is where it quietly breaks, and the fix isn’t obvious until you’ve hit each failure mode once.
Once that full multi-account MCP setup is working, a much bigger set of workflows opens up. That’s what I’ll show you next.
What’s inside:
What can you automate with Gmail MCP? — receipt extraction, inbox triage, subscriber monitoring, 40-second morning brief
When Gmail MCP needs multiple accounts — account bleed, re-auth friction, false confidence
5 Gmail MCP workflows worth running first:
Receipt extractor → $986.41 pulled in one run
Collab pitch triage → inbox to decision in one prompt
Inbox zero → classify, archive, draft in sequence
Subscriber surge detector → 28 new subs caught before I noticed
Morning brief → all 4 accounts, 7 items, 40 seconds
How to automate a Gmail MCP nightly digest — the scheduled version that runs without a manual prompt
Gmail MCP multi-account setup for Claude Code — one Google Cloud project, 4 named inboxes, the fork that made it reliable
Gmail MCP config template + 5-prompt pack + 12 more automation ideas — grab it at the end
_Hi, I’m Jenny 👋
I help non-technical people turn friction into working AI systems through the Practical AI Builder Program, a 12-month program for people already using AI who want to build and ship real systems. _
If you’re new here, welcome! Here’s what you might enjoy:
This article continues for members
Join Build to Launch to read the full article, access all cohort content, and connect with other AI builders.