MCP servers issues on the web app
Issues the maintainers labelled both platform:web and area:mcp.
95 issues · 20 open · 75 resolved (79%) · first seen Mar 24, 2026
Is this getting better or worse?
This class of problem is converging. 26 new reports in the last 90 days vs 56 in the 90 before — -54%. The open backlog peaked at 20 in 2026-09 and sits at 20 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
27 of these reports name the Claude Code build they were running, spanning 19 releases. Heaviest reporters:
- Claude Code v2.1.146
- Claude Code v2.1.195
- Claude Code v2.1.143
- Claude Code v2.1.260
- Claude Code v2.1.251
- Claude Code v2.1.247
- Claude Code v2.1.234
- Claude Code v2.1.41
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 30 days across 75 closures. Of the 75 closures with a recorded reason, 28% were closed as completed and 54 as not-planned or duplicate. The most recent completed fix landed in 2026-10.
Workarounds reported by the community
32 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Scheduled routines fail every MCP tool call with "MCP tool call requires approval" on custom connectors (regression ~2026-05-20)
- …naling/dispatch system that's been broken for two days. The workaround is to move the workload off claude.ai routines entirely and run it as local cron against the same connector — which works fine, but defeats the point…
Found in the description of #61015 · resolved - [BUG] Routines: MCP connector tool calls fail with "requires approval" despite connectors being added to routine
- …d prompt via (preserves model/connectors/cron) 4. Community workaround from u/e lizzle in this thread (no-op sub-agent dispatch at prompt start to warm registry) — dispatch returns READY successfully, but MCP tools remai…
Found in the thread of #61027 · resolved - [BUG] Cloud scheduled tasks cannot access MCP connectors — tools not loaded into session
- …scheduled tasks don't execute until user focuses the task. Workaround Found ! Reddit user [/u/e lizzle]( was able to identify a workaround that worked for me - it'll cost a few extra tokens but if you start the schedule…
Found in the description of #43397 · resolved - CRITICAL: claude.ai MCP connector OAuth completes but Bearer token never sent to server
- Workaround found — noauth on fresh domain While waiting for the OAuth proxy fix, we found a working workaround: Use a fresh domain that has never exposed OAuth endpoints. Claude.ai connects directly — same pattern as any…
Found in the thread of #46140 · resolved - [BUG] MCP tool calls in CCR Routines fail with "requires approval" — no approval UI shown, reconnect does not resolve
- …s impact: Production daily routine is broken. No direct-API workaround available in our environment due to deployment constraints. Currently running the routine manually each morning as a holding pattern. Happy to share…
Found in the thread of #61044 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–95
Ranked by community engagement (reactions weighted over comments).
- [BUG] Scheduled routines fail every MCP tool call with "MCP tool call requires approval" on custom connectors (regression ~2026-05-20)
- [BUG] Routines: MCP connector tool calls fail with "requires approval" despite connectors being added to routine
- [BUG] Cloud scheduled tasks cannot access MCP connectors — tools not loaded into session
- Routines in Claude Code can't use Claude.ai Connectors (e.g., Composio, Gmail, LinkedIn)
- CRITICAL: claude.ai MCP connector OAuth completes but Bearer token never sent to server
- [BUG] MCP tool calls in CCR Routines fail with "requires approval" — no approval UI shown, reconnect does not resolve
- [BUG] Claude Code Web interactive sessions lost all claude.ai MCP connectors ~April 23, 2026 while routines retain them
- [BUG] Remote Control: MCP permission prompts for non-read tools never surface in claude.ai/code web UI
- Claude Code on the web: cloud sessions don't load user-configured MCP servers (only first-party GitHub works)
- CCR: MCP connector OAuth re-authorization returns 'Server Turned Down' on api.anthropic.com/authorize
- [BUG] permissions.allow in settings.json is not honored in Claude Code web remote execution — MCP tools still blocked
- claude.ai MCP-Apps host silently drops `_meta.ui.csp.frameDomains`, blocking all third-party inline iframe embeds (YouTube, Salesforce, etc.)
- [BUG] MCP tools ignore permissions.allow — every call requires manual approval
- MCP connections return 503 DNS cache overflow from sandbox egress proxy (web/mobile)
- [BUG] BigQuery MCP connector on claude.ai/code fails with redirect_uri_mismatch for Google Workspace accounts
- [BUG] Custom MCP connectors on scheduled tasks don't load until a human sends a message
- [BUG] Cloud routines / Claude Code on the web have no non-interactive way to trust a project-scoped `.mcp.json` MCP server - daily routine broke after the untrusted-workspace gate
- GitHub MCP returns 403 "not authorized to use this Copilot feature" on Claude Code web; OAuth fallback renders misleading "Server Turned Down → Google Drive" page
- [BUG] MCP tool write operations fail silently with "requires approval" - no prompt shown (remote execution environment)
- MCP connector tools fail with "requires approval" in routine remote execution sessions
- [BUG] Remote routine fails with "MCP tool call requires approval" despite remote routine settings and MCP tools marked always allow
- [BUG] GitHub MCP server repeatedly disconnects during web sessions, wasting tokens with no output
- [BUG] Claude Code web inconsistently provides GitHub MCP tools for private repos
- [BUG] Routine reports connectors as enabledInChat: false despite being connected globally and attached to the routine
- [BUG] elicit MCP
- Hosted GitHub MCP OAuth flow broken in claude.ai/code web sessions
- [BUG] Scheduled Claude Routine stalls on deferred tool schema loading — requires manual input to continue
- [BUG] Notion OAuth connector fails with "Internal Server Error" on authorization step
- [BUG] Routine cloud sessions resolve a different Gmail MCP server registration than interactive sessions on the same account, causing 100% draft-creation failure since ~2026-05-20 23:00 UTC.
- [BUG] Scheduled routines fail all MCP connector calls with "MCP tool call requires approval"
- [BUG] Claude Code on the web: git push and GitHub MCP refuse changes under .github/workflows/ — proxy OAuth token missing workflow scope
- [BUG] mcp__github__authenticate emits an OAuth URL that redirects to a turned-down Google Drive MCP install page
- Routines UI should auto-allow MCP tools when MCP servers are connected
- [BUG] Routines: claude.ai MCP connectors (Gmail, Slack, Notion) not injected in remote session
- [BUG] Routine sessions: Slack MCP tools fail with "MCP tool call requires approval" despite "Always allow" being set
- [BUG] Cowork HTTP MCP plugins: silent connection drops, Authorization header dropped on tools/call, and GitHub-disconnect "fix" wipes plugins for the whole workspace
- [BUG] Scheduled/automated Claude Code sessions don't load write-capable Slack MCP tools, even when the connector is connected and enabled
- MCP gateway WAF blocks legitimate tool-call bodies (SQL/shell/config text)
- Remote triggers with MCP connections prompt for tool approval despite always-allow setting
- Routine MCP Connectors permission grant not honored at scheduled cron-fire
- Gmail MCP connector: write operations (label_thread/archive/trash) fail in remote routines due to JIT scope upscoping
- [BUG] Slack-initiated Claude Code sessions missing account-level MCP connectors
- [BUG] claude.ai custom MCP connectors send stale session IDs after service restart — tools load but all calls fail, disconnect/reconnect does not fix
- [BUG] Repeated task failure (MCP server integration)
- Routines: MCP tool call (Gmail send_message) silently no-ops but run reports SUCCEEDED
- [BUG] Claude Code cloud session — Google Calendar connector enabledInChat intermittently false despite connected: true
- [BUG] Private repo 404 via GitHub connector after org↔personal transfer — backend index never re-syncs
- [BUG] Cloud routines (CCR) cannot use Slack MCP write tools — "Always allow" option unavailable
- Claude Cowork: scheduled task gets HTTP 500 from a custom MCP (OAuth) connector, while Claude Desktop + Claude Code succeed on the same server
- Custom MCP connectors not attachable to scheduled routines — no UUID discovery path
- [BUG]
- Remote routines cannot bypass MCP tool approval gate (CreateSessionRequest has no permission_mode field)
- [BUG] Supabase MCP missing from web/desktop Code workspace + stream timeouts
- [BUG] Scheduled tasks cannot access MCP connectors until a user message warms the session (request to reopen of auto closed #35899)
- [BUG] Scheduled task MCP connector tools unavailable in execution environment (Slack, Notion, Gmail, Calendar all fail)
- [BUG] Child sessions: claude-code-remote MCP "Allow once" approvals are orphaned — calls fail before the prompt renders, grants never bind (11 calls, every prompt approved, 0 executions)
- [BUG] "MCP tool call requires approval" in an INTERACTIVE remote session — the approval is clicked and ignored, and the refusal is per-tool on one connector
- [BUG] Cloud session resume after MCP disconnect re-prompts for MCP tools already allowed in committed .claude/settings.json (unattended routine runs hang forever)
- [BUG] Indeed connector — errori di connessione ricorrenti lato provider (3 giorni consecutivi)
- [BUG] MCP OAuth re-auth UI not shown for page reload/background Streamable HTTP auth failure
- Opus 4.8 - Session failure audit — repeated tool-avoidance, premature "impossible" verdicts, work offloaded to user
- [Bug] MCP Tools not loading completely from claude.ai
- [FEATURE] Allow connecting the same MCP server multiple times
- Cowork creates a broken @<plugin>-local connector for a plugin-bundled HTTP MCP server, despite the endpoint supporting DCR
- [BUG] GitHub MCP missing release/tag write tools; git push origin <tag> 403's via sandbox proxy
- [BUG] Linear MCP OAuth /authorize endpoint redirects to deprecated gdrive install URL
- [BUG] Bug: MCP tools require approval despite being in settings.json allowlist
- claude.ai/code: head branch not deleted after MCP-driven PR merge despite agent instructions
- [BUG] Claude Agent View: localhost URLs returned by tools are not surfaced as previews / no browser handoff
- [BUG] Claude says MCP cannot be used in Claude Code on the Web
- [BUG] OAuth token refresh never attempted for custom connectors via mcp-proxy.anthropic.com
- [BUG] Stitch generate_screen_from_text never queues via MCP
- [BUG] Scheduled jobs fail to access deferred MCP tools — timing race at session start
- Auto mode classifier blocks editing an email draft the user approved in the same conversation ("Unrequested Commit in a Connected App")
- [BUG] Claude Code on the web (claude.ai/code): MCP connector prompts offer only "Allow once", so read-only tools ask on every call
- [BUG] Custom remote MCP connector: tools/call result with embedded binary resource (`type: "resource"` + `blob`) fails schema validation
- [BUG] hangs indefinitely
- [BUG] Slack connector shows "Connected" in Settings but is invisible to routines/MCP authorization
- [BUG] Bug report: Cloud Routines cannot attach first-party Google Workspace connectors
- [BUG] Resumed cloud routine session: connector tools de-registered and never restored (the MCP half of #81822)
- Remote MCP connector: concurrent conversations share one MCP session, causing responses to cross between them
- Claude Code on the web: no way to supply plugin `userConfig` (secrets) to cloud sessions
- [Bug] Scheduled routines hang on Slack MCP connector approval prompt in headless mode
- [BUG] Cowork scheduled tasks fail when Slack is the first (or only) connector called
- Auto mode classifier blocks a user-directed procedure on the user's own server as "Auto-Mode Bypass"
- [GitHub integration]
- [FEATURE] Support GitHub Projects v2 (add items, set fields/Status) in Claude Code web + Claude GitHub App
- [BUG] Routines: GitHub MCP search_issues returns total_count 0 for any free-text term in a private repo (qualifier-only queries work)
- Connector tool results return unusable payloads: Browserbase navigate dumps the internal page object, Claude Code Remote list_triggers returns 180 KB on one line
- Cowork: a custom MCP connector fails to connect with 502 CLIENT_HTTP_NOT_IMPLEMENTED from the MCP proxy, and only that connector, for a whole session
- claude.ai Gmail MCP create_draft: the google.com/url wrapper is emitted CORRUPTED (raw 0x17 in place of "=1"), and the substituted signature carries no gmail_signature marker
- [BUG] Cloud Routine cannot access connected MCP connectors (Slack, Microsoft 365, Atlassian, Coralogix) — connector registry errors, PushNotification tool disabled
- [BUG] Notion MCP connector toggle doesn't persist — reverts to enabledInChat:false repeatedly
- [BUG] Claude Code on the web: Claude Design handoff session can push a branch but has no GitHub MCP tools, so it cannot open the PR for the branch it just pushed
- [BUG] Custom remote MCP connector - all tools show "Auto-Allow disabled by your admin" in routine, despite org-wide Always Allow