claude-code - 💡(How to fix) Fix first-party Google Workspace connectors for Claude Agent SDK

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Feature request: first-party Google Workspace connectors (Gmail, Sheets, Tasks, Calendar) available to Claude Agent SDK / Claude Platform agents — not only to claude.ai chat.

Context: I run 5 managed agents in production across finance, comms, scheduling, and orchestration. The Notion, Supabase, and Lucid first-party connectors work beautifully inside these agents. Google Workspace is the obvious gap.

What I've tried: Composio (works, but adds a third party to the trust chain), Google Workspace CLI, and self-hosted MCP. All functional, all add maintenance and credential-custody surface area I'd rather not own.

What first-party would unlock: OAuth handled by Anthropic, consistent UX with existing connectors, no key custody for downstream users of my agents, and a smaller surface area for credential handling in the runtime.

Specific scope that would cover ~90% of my use cases: Gmail (read/send/label/search), Sheets (read/write/append/format), Tasks (CRUD), Calendar (already exists in chat — please expose to Agent SDK).

Background for context: developer building Claude Skills and agents for my business startup. Former media production manager, live film director, and long-form TV editor running teams of 7–10. Currently studying as a personal trainer in Australia. I build for the same reason I directed: I want the system to do the right thing without me holding every wire.

Proposed Solution

Native first-party connectors in the Claude Agent SDK, matching the connector model already used by Notion, Supabase, Lucid, and Google Drive in claude.ai. Specifically:

Gmail: OAuth-authenticated read/send/draft/label/search Sheets: read range, write range, append row, list tabs, create sheet Tasks: list, create, update, complete, delete Calendar: read events, create events, update/move events, delete events — already partially exists for claude.ai chat, needs full read/write exposure to Agent SDK

Alternative Solutions

Tried: Composio (adds third party to credential chain), Google Workspace CLI (bash dependency, doesn't generalise to hosted agents), self-hosted MCP on Railway (maintenance and token refresh overhead). All workable, none as clean as native.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Finance agent needs to read a household budget Google Sheet and append parsed bank transactions Comms agent needs to triage Gmail, label emails, and draft replies Scheduling agent needs to read, write, create, and move Google Calendar events, and manage Google Tasks — currently requires separate third-party credential chains for eachCurrently all three require separate third-party credential chains — one native Google Workspace connector would cover all of them

Additional Context

The long-term goal is perpetual learning — each agent observes and acts within its domain (finance, comms, scheduling, orchestration) in real time, learning from both its own actions and by watching me operate in those same Google Workspace environments. This requires live, bi-directional, persistent access to Gmail, Sheets, Tasks, and Calendar — not batch syncs or one-off reads. First-party connectors with persistent OAuth are the only architecture that makes this viable at the agent level without introducing third-party fragility into what is essentially the agent's nervous system.