claude.ai-scoped connectors (Slack/HubSpot/Gmail/Calendar/Drive) show 'Connected' via claude mcp list but are never loaded as tools in a CLI session

Summary

MCP servers that come from claude.ai account-level connectors (shown by claude mcp list with the claude.ai <Name> prefix, e.g. claude.ai Slack, claude.ai HubSpot, claude.ai Gmail, claude.ai Google Calendar, claude.ai Google Drive) report ✔ Connected and Scope: claude.ai config, but their tools are never actually registered/loaded into a normal Claude Code CLI coding session. This makes the "Connected" status misleading — it appears to reflect only a claude.ai-side health check, not actual availability inside Claude Code.

Steps to reproduce

1. Have several connectors enabled/authorized in claude.ai account settings (Slack, HubSpot, Gmail, Google Calendar, Google Drive in my case — Ramp, QuickBooks, Pylon, AWS Marketplace also show Connected and are presumably affected the same way).
2. Run claude mcp list in Claude Code CLI — the connectors show ✔ Connected.
3. Start a normal Claude Code session and try to use any Slack/HubSpot/Gmail/Calendar/Drive tool, or search for one via the tool-search mechanism — no matching tool exists.
4. Run claude --debug -p "list every distinct MCP tool name you currently have access to, one per line, nothing else" and inspect the debug log — there is zero mention of slack/hubspot/gmail/drive/calendar anywhere in the MCP handshake log. The CLI never even attempts to connect to these servers for tool loading during a session; claude mcp list's health check appears to be a separate code path from the session's actual MCP client bootstrap.

Attempted workaround (also worth fixing/documenting)

I tried registering the same services as ordinary local user-scoped HTTP MCP servers to route around this:

claude mcp add --transport http slack "https://mcp.slack.com/mcp" -s user
claude mcp add --transport http hubspot "https://mcp.hubspot.com/anthropic" -s user
claude mcp add --transport http gmail "https://gmailmcp.googleapis.com/mcp/v1" -s user
claude mcp login slack

This fails at the OAuth step with:

Couldn't complete authentication for "slack": SDK auth failed: Incompatible auth server: does not support dynamic client registration

Same error for hubspot and gmail. So these hosted MCP endpoints only accept Anthropic's own pre-registered OAuth client (the one presumably used by claude.ai's connector flow), not a generically-added Claude Code MCP client via claude mcp add + claude mcp login. There's currently no supported way for a Claude Code CLI user to get a working, tool-call-capable connection to these same services, despite claude.ai showing them as fully connected under the same account.

Expected behavior

Either:

• Connectors authorized at the claude.ai account level should have their tools actually loaded into Claude Code CLI sessions (so "Connected" in claude mcp list means what it appears to mean), or
• claude mcp list/claude mcp get should clearly indicate that claude.ai-config-scoped servers are informational only and not usable from CLI sessions, so users don't spend time debugging a connection that was never wired up to begin with.

Environment

• Claude Code version: 2.1.197
• macOS (Darwin 25.5.0)
• claude mcp list shows the affected servers with Scope: claude.ai config