No way to suppress OAuth warnings for unconnected claude.ai integrations at startup

Summary

Every time Claude Code starts a new session, it connects to the claude.ai account and detects any integrations that are listed but not yet authenticated (e.g. Gmail, Google Calendar, Google Drive, Harvey, LegalZoom, Midpage Legal Research, MotherDuck). It then populates ~/.claude/mcp-needs-auth-cache.json with those entries and surfaces OAuth warnings at startup — even for integrations the user has no intention of using.

Steps to reproduce

1. Have a claude.ai account with any built-in integrations listed under "Not connected"
2. Open a new Claude Code terminal session
3. Observe OAuth warnings at startup for every unconnected integration

Expected behavior

Users should be able to dismiss or permanently suppress OAuth prompts for integrations they don't want to connect. Either:

• A "Don't remind me" / "Hide" option per integration in the claude.ai integrations UI, or
• A Claude Code setting (e.g. suppressMcpAuthWarnings: true) to silence these startup notifications

Actual behavior

The mcp-needs-auth-cache.json file is repopulated from the remote claude.ai account on every startup, and OAuth warnings are shown every session with no way to suppress them short of making the cache file read-only.

Workaround

Making ~/.claude/mcp-needs-auth-cache.json read-only stops the warnings, but is a hack and may cause side effects.

Environment

• Platform: macOS (darwin)
• Claude Code CLI