[BUG] All claude.ai-connected MCP integrations show ✓ Connected but expose zero tools in Claude Code session (terminal CLI, macOS, 2.1.126, Opus 4.7)

Summary

Every claude.ai-namespaced MCP connector reports ✓ Connected via claude mcp list but none of their tools register in the Claude Code session. ToolSearch returns no results for any of them. Custom stdio/HTTP MCP servers configured locally load fine in the same session — the breakage is specific to the claude.ai-managed remote connectors.

This is the inverse of #51736 (where stdio servers fail and claude.ai connectors work) and broader than #32450 / #30457 (which affect a single connector). In my case all 8 claude.ai connectors are silently absent from the tool registry.

Environment

• Claude Code: 2.1.126
• OS: macOS (Darwin 25.4.0, arm64)
• Shell: zsh
• Model: Opus 4.7 (claude-opus-4-7)
• Plan: Max subscription, personal/admin org (penguinModeOrgEnabled: true)

Steps to Reproduce

1. Connect 8 claude.ai integrations via Settings → Connected apps: Gmail, Google Drive, Google Calendar, Notion, Spotify, Linear, Intuit Credit Karma, Aiwyn Tax.
2. Confirm via claude mcp list — every connector reports ✓ Connected:

``
claude.ai Notion: https://mcp.notion.com/mcp - ✓ Connected
claude.ai Spotify: https://mcp-gateway-external-pilot.spotify.net/mcp - ✓ Connected
claude.ai Intuit Credit Karma: https://anthropic.mcp.creditkarma.com/mcp - ✓ Connected
claude.ai Gmail: https://gmailmcp.googleapis.com/mcp/v1 - ✓ Connected
claude.ai Google Calendar: https://calendarmcp.googleapis.com/mcp/v1 - ✓ Connected
claude.ai Linear: https://mcp.linear.app/mcp - ✓ Connected
claude.ai Aiwyn Tax (formerly Column Tax): https://mcp.columnapi.com/mcp - ✓ Connected
claude.ai Google Drive: https://drivemcp.googleapis.com/mcp/v1 - ✓ Connected
kb: ... - ✓ Connected
empower: npx -y @bank-mcp/server - ✓ Connected
context: https://context.era.app (HTTP) - ✓ Connected
doordash: node /Users/.../doordash-mcp/dist/index.js - ✓ Connected
``

1. Start a Claude Code session in the terminal.
2. Inspect the deferred tools registry the model sees: only mcp__context__*, mcp__doordash__*, mcp__empower__*, mcp__kb__* are present. No mcp__claude_ai_* tools surface.
3. ToolSearch queries return nothing for any of:

• +gmail
• +google drive
• +claude_ai
• +notion, +linear, +spotify, etc.

Expected Behavior

Tools from each connected claude.ai integration register as deferred tools at session start, prefixed mcp__claude_ai_<Name>__* (e.g. mcp__claude_ai_Gmail__search_threads, mcp__claude_ai_Google_Drive__read_file_content), and become callable via ToolSearch → invoke.

Actual Behavior

Zero claude.ai-namespaced tools are registered. Only locally configured stdio/HTTP MCP servers load. The connection check passes; the tool-list/schema fetch step appears to be skipped or filtered out for the claude.ai connectors.

Evidence this used to work

A pre-Opus-4.7 session (Apr 27 2026, session ID 41485b91-6e8b-4342-98d1-1e6273a78f5f) called these tools successfully under the same OAuth account with no config changes:

mcp__claude_ai_Gmail__create_draft
mcp__claude_ai_Gmail__get_thread
mcp__claude_ai_Gmail__search_threads
mcp__claude_ai_Google_Drive__download_file_content
mcp__claude_ai_Google_Drive__read_file_content
mcp__claude_ai_Google_Drive__search_files

The OAuth account, connector list, and ~/.claude.json topology are unchanged since then.

Investigation

• ~/.claude.json claudeAiMcpEverConnected lists all 8 connectors (matches what mcp list reports).
• ~/.claude.json mcpServers only contains kb (user scope); project-scoped mcpServers block contains context, doordash, empower. The claude.ai connectors aren't stored in ~/.claude.json and are presumably synced from the account level — consistent with #53656's description.
• enabledMcpjsonServers and disabledMcpjsonServers are both [].
• claude mcp get "claude.ai Gmail" errors with No MCP server found despite the same name appearing in claude mcp list output — suggests the get/list paths disagree about how these are addressed.
• No per-conversation toggle in /mcp is documented as a workaround for terminal CLI (#53656 explicitly notes none exists).
• Restarting the session does not register the tools.

Hypotheses

1. Opus 4.7 surface change. The 4.7 build may be filtering claude.ai-namespaced remote connectors out of the deferred-tool registry by default, separate from the connection check.
2. Tool-list step silently failing. The connect handshake succeeds but a subsequent tools/list against each remote connector errors out and is suppressed without surfacing in mcp list output.
3. Account-level gating. Possibly related to penguinModeOrgEnabled: true interacting with how account-level connectors are propagated to individual sessions.

Asks

• Surface any per-session error from the tools/list step against claude.ai remote connectors (currently invisible — mcp list says ✓ Connected with no detail).
• If there's an intentional gate behind 4.7, document the toggle / settings key and surface it in --mcp-debug output.
• If unintentional, treat as P1 — claude.ai connectors are unusable from Claude Code terminal CLI for this configuration.

Related

• #51736 — inverse symptom (custom stdio fails, claude.ai works) after 2.1.116
• #32450 — single-connector variant (Drive on VS Code/Windows)
• #30457 — Drive shows connected but no tools in Cowork
• #53656 — confirms claude.ai connectors are intended to activate globally; no per-project disable
• #20412 — confirms claude.ai MCPs are auto-injected by design