Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Starting on or around April 23–24, 2026, all account-level claude.ai MCP connectors stopped being available in interactive Claude Code Web sessions (claude.ai/code, and the "Code" tab in Claude Desktop on Windows). The repo-scoped GitHub MCP server (mcp__github__*) is the only MCP server present at session start. All other connectors (Atlassian Rovo, Hugging Face, Google Drive, etc.) are absent. Connectors remain findable and functional for Claude CHAT and Claude Code ROUTINES.

The asymmetry that distinguishes this from prior reports

• Interactive sessions on claude.ai/code: only mcp__github__* is wired up. ToolSearch sweeps across keywords like atlassian, rovo, jira, confluence, huggingface, slack, linear, notion, sentry, and a broad mcp query all return zero matches beyond GitHub. Direct invocation of a connector tool ("Use the Atlassian Rovo MCP to find Jira issues assigned to me") fails with no Atlassian Rovo MCP connector available in this session.
• Routines launched from the same UI on the same account: connectors resolve correctly. Atlassian Rovo, Hugging Face, etc. work as expected inside routine sessions.
• Claude Chat from the same UI on the same account: connectors can be attached via the "+" UI option (which Code does not have), after which they are discoverable and usable normally too.
• Same symptom on Claude Desktop's "Code" tab on Windows.

Things tried, no effect on interactive sessions

• Disconnect + reconnect of Atlassian Rovo and Hugging Face at claude.ai/customize/connectors
• Remove + reinstall of the same connectors
• Multiple fresh sessions, across both Claude Desktop and Claude Web
• Multiple explicit ToolSearch prompts across many keywords
• Closing and reopening Claude Desktop

Related issues (none describe this exact inverted symptom)

• [BUG] Cloud scheduled tasks cannot access MCP connectors — tools not loaded into session #43397 -Cloud routines cannot access MCP connectors. Directional inverse of this report. The sub-agent-dispatch workaround documented there does not apply here.
• [BUG] Cowork mode never requests user:mcp_servers OAuth scope — Claude.ai connectors (GitHub etc.) permanently blocked #28695 - Cowork tokens lacking user:mcp_servers scope. Closest mechanical precedent - possibly the same class of bug surfacing in a different surface.
• [BUG] Claude Code web inconsistently provides GitHub MCP tools for private repos #42243 - Claude Code Web inconsistently provides GitHub MCP tools for private repos. Same surface, narrower scope.
• [BUG] Connectors not found #49203 - "Connectors not found" on new desktop/mobile sessions. Same symptom shape, predates this regression.
• Custom MCP server tools not discovered after update to 2.1.116 #51736 - After v2.1.116, ToolSearch returns No matching deferred tools found. Symptom-shape match.
• [BUG] Cloud MCP connectors bulk-lose authentication simultaneously with no local recovery path #47485 - Cloud connectors bulk-lose authentication simultaneously. Possible related infrastructure event.

Possible triggers in the April 20–24 release/incident wave

• April 23 status incident: "MCP applications on Claude.ai unavailable" 00:41–02:09 UTC
• v2.1.119 (April 23): changelog includes "Fixed plugin MCP servers stuck 'connecting' on session start when they duplicate a claude.ai connector that is unauthenticated" - directly touches the dedup logic between local and cloud connectors
• v2.1.120 (April 24): force-rolled back by Anthropic within ~24 hours

Requested diagnostics from Anthropic

Note: The diagnostic below was generated by AI (Claude Opus 4.7 in Research Mode) in an attempt to be helpful. Please take it as such.

To narrow whether this is a gate, scope, or --mcp-config synthesis regression:

• Verify the tengu_claudeai_mcp_connectors GrowthBook gate value for affected accounts in interactive Web sessions vs routine sessions on the same account
• Verify the user:mcp_servers scope claim on the bearer token minted for interactive Web sessions vs routine sessions
• Inspect the --mcp-config synthesis for interactive Web session VM spawns post-April 23 - specifically whether the connector list returned from /v1/mcp_servers is being silently filtered to GitHub-only before being passed to the VM

Suggested labels: area:claude-code-web, area:mcp, platform:web - please add if appropriate.

What Should Happen?

Interactive Claude Code Web sessions should inherit the user's account-level claude.ai MCP connectors at session start, mirroring the routines pipeline. Until ~April 23, 2026 this worked correctly.

Specifically: a fresh ad-hoc session on claude.ai/code (or the Code tab in Claude Desktop) should expose all connectors that show as "connected" at claude.ai/customize/connectors, not only the repo-scoped mcp__github__* server.

Error Messages/Logs

N/A

Steps to Reproduce

1. Confirm on claude.ai/customize/connectors that connectors (e.g. Atlassian Rovo, Hugging Face) are connected and authenticated.
2. Open claude.ai/code (or the Code tab in Claude Desktop on Windows). Start a fresh interactive session against any GitHub repo.
3. Ask the model to list available MCP servers, or to search for tools matching connector keywords (atlassian, huggingface, rovo, etc.), or to directly invoke a connector tool such as: "Use the Atlassian Rovo MCP to find Jira issues assigned to me."
4. Observe: only mcp__github__* is listed. ToolSearch returns no hits beyond GitHub. Direct invocations fail with 'no MCP connector available in this session'.
5. From the same UI, create or run a Routine that uses the same connectors.
6. Observe: connectors resolve correctly inside the Routine session.

Things tried, no effect on interactive sessions:

• Disconnect + reconnect of Atlassian Rovo and Hugging Face at claude.ai/customize/connectors
• Remove + reinstall of the same connectors
• Multiple fresh sessions, across both Claude Desktop and Claude Web
• Multiple explicit ToolSearch prompts across many keywords
• Closing and reopening Claude Desktop

Environment:

• Claude Code Web (claude.ai/code, research preview) AND Claude Desktop on Windows 11 "Code" tab - same symptom on both surfaces.
• Account: Pro/Max tier.
• Connectors verified connected at claude.ai/customize/connectors: Atlassian Rovo, Hugging Face, Google Drive, others.
• Onset: ~April 23–24, 2026.
• Repo used in repro: a private repo.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

~Apr 22, 2026 (Claude Code Web / Desktop - no CLI version exposed)

Claude Code Version

N/A - Claude Code Web and Claude Desktop "Code" tab; no claude --version exposed to me on these surfaces. Claude Desktop app version: Claude 1.4758.0 (fb266c)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

The TLDR:

• connectors show as connected at claude.ai/customize/connectors
• Claude Code Routine sessions see them and use them correctly
• Claude Chat "+" UI recognizes them, allows me to select them, session can discover and use them
• ad-hoc interactive sessions on Claude Code Web and Claude Desktop's "Code" tab see only the repo-scoped GitHub MCP, even after repeated discovery requests (not simply a deferred issue)