Google Drive connector works in chat but is invisible to list_connectors/cloud routine attachment
Summary
A Google Drive connector shows as Connected on the Connectors settings page and works correctly for direct tool calls in a chat session, but is completely invisible to the routine-creation connector list, so it can't be attached to a scheduled cloud routine.
Environment
- Claude Code CLI, connected via a persistent homelab session
- Connector: Google Drive, connected via claude.ai/customize/connectors
Steps to reproduce
- Connect a Google Drive connector at claude.ai/customize/connectors (shows checkmark/Connected)
- In a Claude Code chat session, confirm the connector works -- e.g. a Drive search tool call successfully returns real files owned by the connected account
- Attempt to list connectors for cloud-routine attachment (the flow used when creating a scheduled
/scheduleroutine that needsmcp_connections)
Expected: the connected Google Drive connector appears in the list and can be attached to a routine.
Actual: the connector list is empty, every time, across many retries over an extended period (spanning hours).
Troubleshooting already tried, no effect:
- Waiting (connector had already been connected for days, not a fresh-connect propagation issue)
- Full disconnect + reconnect (twice -- including once with a deliberate wait between disconnect and reconnect, since the first reconnect attempt showed a stale "still connected" state immediately after disconnecting)
- Confirmed same account both via the settings page and by the connector successfully returning real files owned by that account in chat
Key detail for triage: the connector is not broken -- it works for live chat tool calls. Only the routine-attachment path can't see it. That suggests the two paths read connector state from different places, and one of them isn't in sync.