How to Sync 6 Email Accounts into Claude Code Using Google Cloud OAuth

The official Claude MCP connector for Gmail only supports a single account. If you run multiple email addresses across different workstreams, that limitation locks you out of one of the most useful Claude Code workflows: unified inbox scanning across all your accounts. Logan walks through how she solved this by setting up a Google Cloud project with separate OAuth tokens per account, giving Claude Code read access to six different email inboxes at once.

The Problem with the Official MCP Connector

Anthropic's official Gmail MCP integration works well for a single Google account. You authenticate once, and Claude Code can read and interact with that inbox. But most people who run businesses, consult across multiple clients, or manage personal and professional lives have more than one email account. The official connector has no built-in support for multi-account access, so you are stuck choosing which one inbox Claude gets to see.

The Google Cloud OAuth Workaround

The solution is to set up a Google Cloud project and use OAuth 2.0 to generate separate tokens for each email account. Each token grants Claude Code read-only access to that specific inbox. A script then pulls from all accounts in sequence, feeding the combined email data into Claude Code's context. Logan reports that she has six accounts synced this way, and the system can read across all of them while also writing to separate calendars per account.

What This Unlocks in Practice

With multi-account email access, Claude Code can operate as a genuine chief of staff layer across your entire communication surface. Logan highlights three specific use cases that have changed her daily workflow:

Cross-account email scanning to surface what matters across every inbox without manually checking each one
Follow-up tracking where Claude flags conversations where you have not responded and reminds you to close the loop
High-urgency detection across different work streams so critical emails in a secondary account do not get buried

These are the kinds of tasks that fall apart when you can only see one inbox. The value compounds with every additional account you connect.

How the Architecture Works

The setup involves a few moving parts. You create a Google Cloud project, enable the Gmail API and Calendar API, and configure OAuth consent. Then you generate individual OAuth credentials for each email account, storing each token separately. A script (which Claude Code itself can help you write) iterates through the tokens and pulls recent emails from each account. The combined output becomes context that Claude Code can reason over, prioritize, and act on.

Logan notes that email access is read-only across all accounts, which is a reasonable security boundary. Calendar access includes write permissions, so Claude Code can create and update events on specific calendars as needed.

Key Takeaways

The official MCP Gmail connector only supports one account, so multi-account users need to build their own integration
Google Cloud OAuth with per-account tokens is the workaround that lets Claude Code read from multiple inboxes
Email access is read-only; calendar access supports writes, which gives you a useful security split
Follow-up tracking and urgency flagging across accounts are the highest-value use cases for this setup
Logan published a spec on her website detailing the full implementation alongside other free Claude Code resources