Reference anthropic mcp google oauth bypass
Anthropic ships three Claude MCP connectors that ride on Anthropic's own CASA-audited OAuth app:
mcp__claude_ai_Gmail__authenticate— Gmail read/search/label/archive/send/draftmcp__claude_ai_Google_Calendar__authenticate— Calendar list/create/edit/delete/searchmcp__claude_ai_Google_Drive__authenticate— Drive search/read/write
Authorizing these takes ~30 seconds per service (one-time Google OAuth consent flow), and from then on Claude can access those Google services on Justin's behalf using Anthropic's verified client.
Why this matters: gmail.modify (the scope needed to read email bodies + write) is now classified Restricted by Google, requiring a CASA security audit (~$3K-$15K, 6-12 week cycle, annual renewal). By routing AI-driven Gmail/Calendar ops through Anthropic MCP instead of Forge's own OAuth client, Forge avoids verification entirely. Anthropic has already paid the CASA cost.
Cost model: Every Gmail/Calendar MCP action goes through a Claude API call, consuming tokens (roughly $0.01-0.10 per email touched for AI summarization). This is NOT free, but for use cases where AI reasoning is involved anyway, token cost is the same as calling Claude then calling Gmail separately.
Gaps: YouTube Data API, Contacts, and YouTube Analytics are NOT covered by Anthropic MCP connectors as of 2026-05. Those still need their own path (Apps Script, Pipedream, or full verification).
When to use: All AI-driven Gmail/Calendar/Drive ops (triage, summarize, draft, schedule from natural language). Not appropriate for pure procedural cron jobs with no AI reasoning (e.g., nightly archive-all-noreply — use Google Apps Script web app for those).
[Claude Code]
[auto-memory session 1a660aac-56d2-400d-8206-c59564bbff19, confidence 0.85, mode direct]