The architecture: Business sam@hookstreetcapital.com already runs on the claude.ai Gmail connector (works in every Claude Code session, including remote-control). This adds personal ztreitel@gmail.com as a second, local MCP — a small Gmail MCP server running on your machine, authenticated only to your personal account.
Why this respects your privacy rule: the personal OAuth token lives in C:\Users\ztrei\.gmail-mcp\ — local to this computer, used only by Claude Code. It is completely separate from Mildred's delegate access to the business inbox. Personal mail never enters the business account. No forwarding, no Gmailify, no mixing.
Result: I'll have both inboxes in every session. Business tools = mcp__claude_ai_Gmail__*. Personal tools = mcp__gmail-personal__*.
This is the only part I can't do for you (no CLI for the consent screen). Go to console.cloud.google.com — sign in as ztreitel@gmail.com.
claude-gmail-mcp. Create, then select it.ztreitel@gmail.com. (Keeping it in "Testing" mode means no Google verification needed — fine for personal use.)gmail-mcp-desktop → Create.C:\Users\ztrei\.gmail-mcp\gcp-oauth.keys.json.gmail-mcp folder. Rename the downloaded file to gcp-oauth.keys.json.)Once the keys file is saved, run this from the workspace (PowerShell or via ! in Claude Code):
powershell -File scripts/setup-gmail-personal-mcp.ps1It will, in order:
~/.gmail-mcp/credentials.json.)gmail-personal at user scope (available in all your Claude Code sessions; NOT committed to git).claude mcp list to verify it connected.Restart this Claude Code session (or start a new one) so the new MCP loads. Then say "personal gmail is wired" and I'll confirm I can read both inboxes — I'll do a test search on the personal account to prove it.
This MCP gets read+write access to your personal Gmail (bank 2FA, password resets live there). The token is local-only and Mildred can't see it — but I will be able to read/search personal mail once it's wired. That's the point (you asked for it), just naming it plainly. If you'd rather I treat personal as read-only in practice, say so and I'll never send/delete/modify on that account — only read + search. Your 2FA stays SMS-to-phone regardless; nothing here touches that.
This replaces the ChatGPT↔Claude personal-inbox relay stopgap (the one in docs/ from session 38). Once personal is wired directly, Claude Code reads it natively — no relay, no copy-paste between assistants.
Noted and real. The durable version: a periodic capability scan — Claude reviews what connectors/MCPs/skills exist vs. the friction points in recent sessions, and proactively surfaces "here's a wiring that would remove this recurring pain." That's a small recurring routine, not a one-off. I'll propose it as its own thing once the Gmail wiring is done so we don't dilute this task — flag it back to me as "do the capability-scan routine" whenever you want it built.