## Description The first-party Google Drive MCP integration re-authenticates via browser OAuth on every new Claude Code session. The token is not persisted to macOS Keychain. ## Steps to reproduce 1. Start Claude Code session 2. Complete Google Drive OAuth in browser 3. Use Google Drive MCP tools successfully 4. Exit session, start a new one 5. Browser opens again asking to re-authenticate ## Expected behavior OAuth token should persist across sessions (e.g., stored in macOS Keychain). ## Ver

Google Drive MCP OAuth token not persisted across sessions

Status Closed — duplicate

Reported on v2.1.104

Maintainer reply None cached

Activity 3 comments · opened Apr 17, 2026 · closed Apr 20, 2026

Description

The first-party Google Drive MCP integration re-authenticates via browser OAuth on every new Claude Code session. The token is not persisted to macOS Keychain.

Steps to reproduce

Start Claude Code session
Complete Google Drive OAuth in browser
Use Google Drive MCP tools successfully
Exit session, start a new one
Browser opens again asking to re-authenticate

Expected behavior

OAuth token should persist across sessions (e.g., stored in macOS Keychain).

Verification

security find-generic-password -s "claude" -a "google-drive" returns "specified item could not be found in the keychain."

Environment

macOS Darwin 25.2.0
Claude Code 2.1.104 → 2.1.112
Installed via npm i -g @anthropic-ai/claude-code
Two Google Drive MCP servers configured (google-drive + google-drive-llc)

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗