Google Drive MCP connector: /mcp reports successful re-auth but tool calls still fail with 'token expired'

Description

The built-in claude.ai Google Drive MCP connector gets stuck in a state where /mcp reports a successful reconnect/re-authorization, but subsequent tool calls against the connector (e.g. list_recent_files) continue to fail with a token-expired error.

Steps to reproduce

1. In Claude Code, run /mcp and disconnect the claude.ai Google Drive connector.
2. Run /mcp again to reconnect — output: Reconnected to claude.ai Google Drive.
3. Call any Google Drive MCP tool (e.g. list_recent_files).
4. Observe error: MCP server "claude.ai Google Drive" requires re-authorization (token expired)
5. Run /mcp again to explicitly re-authenticate — output: Authentication successful. Connected to claude.ai Google Drive.
6. Immediately retry the same tool call.
7. Still get: MCP server "claude.ai Google Drive" requires re-authorization (token expired)

Steps 5–7 were repeated multiple times (including after a delay) with the same result each time — /mcp consistently reports a successful auth, but the tool-calling session still sees an expired token.

Expected behavior

After /mcp reports Authentication successful. Connected to claude.ai Google Drive., subsequent Google Drive MCP tool calls should succeed using the refreshed token.

Actual behavior

Tool calls continue to fail with requires re-authorization (token expired) even immediately following a reported-successful re-auth, suggesting the refreshed token from the /mcp auth flow isn't being propagated to (or picked up by) the active MCP tool session.

Environment

• OS: Windows 11 Pro 10.0.26200
• Shell: PowerShell (primary)
• Connector: built-in claude.ai Google Drive MCP server