MCP servers issues on VS Code
Issues the maintainers labelled both platform:vscode and area:mcp.
176 issues · 33 open · 143 resolved (81%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is converging. 50 new reports in the last 90 days vs 71 in the 90 before — -30%. The open backlog peaked at 35 in 2026-04 and sits at 33 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
124 of these reports name the Claude Code build they were running, spanning 82 releases. Heaviest reporters:
- Claude Code v2.1.141
- Claude Code v2.1.165
- Claude Code v2.1.251
- Claude Code v2.1.263
- Claude Code v2.1.231
- Claude Code v2.1.168
- Claude Code v2.1.142
- Claude Code v2.1.119
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 143 closures. Of the 143 closures with a recorded reason, 19% were closed as completed and 116 as not-planned or duplicate. The most recent completed fix landed in 2026-09.
Workarounds reported by the community
61 of these issues post a workaround someone says worked. The highest-engagement ones:
- Google Drive claude.ai connector not loading in VS Code extension despite being connected in claude.ai
- …the active configuration controlling which connectors load. Workaround None found. Google Drive requires per-conversation opt-in in the claude.ai web interface, but there is no equivalent mechanism in Claude Code VS Code…
Found in the description of #32450 · resolved - [BUG] MCP elicitation: capability is declared but requests are auto-declined ("print mode") in interactive VSCode sessions
- …navailable” weakens real declines for other clients. Narrow workarounds while the handler is unwired 1. Do not gate solely on the capability flag. Treat a decline that arrives with no UI / sub-second latency (or with a k…
Found in the thread of #98256 · still open - [BUG] v2.1.68 (updated 2026-03-04) opens 3 blank VS Code windows when claude is started in the integrated terminal.
- …oss versions v2.1.68 and v2.1.69 and survive all documented workarounds: Bug 1: Three blank VS Code windows spawn on every Claude Code session start. Every time I start a Claude Code session from the integrated terminal,…
Found in the thread of #30848 · resolved - [BUG] mcp__ide__getDiagnostics available in CLI (integrated terminal) but missing from VSCode extension panel
- …the IDE MCP server; the extension panel cannot discover it. Workarounds attempted Approach Result --- --- shell script that reads lock file and exports env vars Env vars did not propagate — extension panel likely doesn't…
Found in the description of #40766 · resolved - [FEATURE] VSCode extension: render images inline in the chat panel instead of the "[Image]" placeholder
- …the tool return visual state. Alternative Solutions Current workaround: instruct the agent to open the saved image in a VSCode editor tab ( ) after capturing it. It works but breaks conversation flow and requires every M…
Found in the description of #79436 · 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–100
Ranked by community engagement (reactions weighted over comments).
- Google Drive claude.ai connector not loading in VS Code extension despite being connected in claude.ai
- [BUG] MCP elicitation: capability is declared but requests are auto-declined ("print mode") in interactive VSCode sessions
- [BUG] v2.1.68 (updated 2026-03-04) opens 3 blank VS Code windows when claude is started in the integrated terminal.
- [BUG] mcp__ide__getDiagnostics available in CLI (integrated terminal) but missing from VSCode extension panel
- [BUG] [VSCode Extension] MCP Authenticate button does not open browser on macOS
- [FEATURE] VS Code extension: show images inline in the chat panel (re-file of stale-closed #79436)
- MCP elicitation: capability is declared but requests are auto-declined ("print mode") in interactive VSCode sessions
- [BUG] MAX100 subscription - abnormal quota consumption and rate_limit_error with multi-session Claude Code
- Linear MCP plugin: create_issue tool advertised but returns 'Tool not found'
- [BUG] VS Code extension: startup() handshake timed out 30000ms despite CLI working (v2.1.101 Windows)
- [BUG] API Error 500 - Internal server error
- [FEATURE] VSCode extension: render images inline in the chat panel instead of the "[Image]" placeholder
- [FEATURE] Allow Claude Code VS Code extension to read MCP servers from VS Code's mcp.json
- Support claude config in all workspace folders and workspace file directory (multi-root workspaces)
- Telegram channel plugin: MCP connection silently drops, zombie processes pile up
- [BUG] VSCode extension doesn't load MCP servers on Windows due to drive letter case mismatch in .claude.json project key lookup
- [BUG] Windows: case-sensitive `.claude.json` project-key lookup silently drops MCP servers across CLI/VS Code — recurring bug, repeatedly auto-closed unfixed
- [BUG] VS Code panel sessions never get mcp__ide__getDiagnostics: the IDE server is only advertised to integrated terminals
- [BUG] VSCode extension silently declines MCP URL elicitation requests
- VS Code extension: streams end with sdk_stream_ended_no_result after first chunk, on one machine only
- [BUG] HTTP MCP server without auth triggers OAuth probe in VS Code extension, fails with 404
- VSCode Extension v2.1.141: 'Unhandled case: [object Object]' notification with no actionable details
- MCP destructive tools silently denied without prompt in acceptEdits mode — misleading error message
- VSCode /mcp shows 'No servers configured' when slow-starting stdio MCP servers are added to .mcp.json
- Plan Mode re-prompts on every call for parameterized MCP tools, even when covered by a permissions.allow wildcard
- [FEATURE] Support MCP prompts as "slash" commands in VS Code extension
- [BUG] Title: CLAUDE.md project rules overridden by MCP server instructions — runaway token consumption
- [BUG] Tool restrictions from claude.ai are ignored by the CLI / VS Code extension
- allowedMcpServers cannot include Claude.ai Cowork connectors — name format conflict with schema validation
- [FEATURE] Support VS Code-style ${input:id} secret prompts in .mcp.json for VS Code extension
- [BUG] Vercel MCP OAuth token not persisted — empty accessToken after every auth
- [BUG] Claude in Chrome (VS Code 2.1.160): `mcp_set_servers` publishes only SDK tools to the model and gates even that on `sdkServersChanged` — so a dynamically-added stdio server connects (status/pill shows its tools) but the model never receives them
- Claude in Chrome (VS Code extension, macOS): @browser prompt injects + tab created, but mcp__claude-in-chrome__* tools never register (no native-messaging manifest / native host / bridge socket)
- [BUG] MCP server error notifications render as "[object Object]" instead of the error message
- [BUG] MCP server child processes not terminated on Windows after session exit, causing process accumulation
- MCP OAuth token exchange omits client_id in body, breaks public PKCE clients (Wrike)
- [BUG] mcp headersHelper not re-invoked when access token expires on long-lived HTTP transport
- [BUG] MCP OAuth support for HTTP servers (e.g. Atlassian official MCP)
- [BUG] Microsoft 365 connector unusable in Claude Code (works in Claude Desktop)
- [BUG] Selection injection from `ide` MCP server has no documented suppression mechanism, leaks env file contents to conversation transport
- [BUG] MCP server tools unavailable after /clear in VS Code extension
- VS Code extension should inherit MCP servers from ~/.claude.json
- MCP servers using npx fail to connect in VS Code 1.112
- [BUG] MCP servers fail on startup due to race condition — connections dropped before REPL mounts (AlmaLinux 8 / RHEL 8)
- [BUG] VS Code: plugin MCP server silently dropped when a claude.ai connector has the same URL (CLI keeps the plugin)
- VSCode extension does not surface claude.ai account connectors (MCP) that the CLI exposes — same version 2.1.156
- VS Code extension's MCP OAuth flow sends malformed resource parameter (double-encoded, params leak into outer URL)
- Claude repeatedly asked user to verify changes instead of self-verifying via available browser MCP
- [BUG] VS Code extension hangs on WSL2 — PendingMigrationError (navigator global) prevents MCP server from starting
- [BUG] VS Code extension spawns duplicate MCP servers (still present in v2.1.71)
- [BUG] MCP OAuth discovery (.well-known) fails with InvalidHTTPResponse across multiple servers
- Railway MCP custom domain: Claude concludes no TXT record is needed, domain never verifies
- [Feature Request] MCP tool rendering API to control request panel collapse state
- [BUG] Valid MCP tool silently dropped: API schema validation rejects property names containing `[]`
- MCP server connects successfully but its tools are never exposed to the model
- [BUG] Claude Code VS Code extension does not read MCP server config from Claude Desktop MSIX virtualized path
- v2.1.142 disconnects on remote-SSH after extension update — claude binary accumulation + MCP server flapping
- [Cowork UI] "Unhandled case: [object Object]" banner — MCP tool-result envelope + SDK stream-end-with-error renderer paths
- [Bug] Excessive API calls causing unexpected billing on failed requests
- [Bug] /mcp command produces no dialog or output
- [BUG] Claude ignores user's MEMORY.md and auto-memory files during debugging — treats external memory as disposable
- Persistent 502 Bad Gateway from mcp-proxy.anthropic.com — Gmail connector works in claude.ai chat but fails in Claude Code (VS Code extension)
- [Bug] VS Code extension startup hangs when MCP servers lack OAuth tokens
- [Feature Request] VS Code extension: share MCP servers across conversation tabs instead of spawning per-tab
- [BUG] Supabase MCP OAuth fails in VSCode extension but works in terminal
- [BUG] Disconnected cloud MCP connectors (e.g. Atlassian) still trigger browser OAuth prompt on every session start
- [BUG] VS Code extension double-encodes MCP OAuth resource parameter when server URL has a query string (still present in 2.1.280)
- Expand/view full MCP tool inputs in the VS Code extension
- [BUG] Stdio MCP servers still connecting (or queued) at session end are never terminated and are left orphaned
- [BUG] MCP servers connect successfully but tools don't surface as callable, even after full restart
- [Bug] MCP connectors timeout at 30s despite fast endpoint response; claude.ai-scoped connectors fail while functioning in Claude app
- [BUG] Regression (v2.1.212): VS Code extension hangs at "Connecting…" for a healthy stdio MCP server on Windows 11 — cmd /c fixes it
- MCP server 'supabase' sendo removido/adicionado repetidamente com comando malformado (openssl rand -hex 32 não interpolado)
- [BUG] Don't surface never-connected first-party connectors (Gmail/Calendar/Drive) as startup action items in Claude Code
- [BUG] Persistent MCP server diagnostic alert after removing configuration
- [BUG] MCP stdio server notifications/tools/list_changed does not refresh the tool catalog mid-session
- [FEATURE]
- VSCode extension v2.1.141 renders 'Unhandled case: [object Object]' instead of MCP server error messages
- GitLab MCP OAuth fails with "The requested scope is invalid, unknown, or malformed"
- [Bug] GitHub token authentication error persists after configuration
- Microsoft 365 MCP connector shows 'Needs Auth' in VS Code despite being connected in desktop app
- [BUG] VS Code extension: claude.ai MCP connectors connected in CLI but not injected into extension sessions
- [Bug] Anthropic API Error: Token Exhaustion and Inconsistent Model Behavior
- [BUG] Claude Code cannot interact with VSCode (no IDE tools available - can't openDiff, getDiagnostics...)
- [Bug] Claude Code deleted Looker dashboards without confirmation or safety check
- [BUG] VS Code extension ignores cwd field when launching MCP servers, causing module path collisions
- [Bug] Notion MCP server configured but not appearing in MCP list
- MCP push notifications (claude/channel) not received in VS Code extension
- [BUG] claude.ai Slack Connector missing from VSCode /mcp panel despite showing as Connected in CLI
- Chrome MCP never starts in VS Code extension — experimentGates.tengu_quiet_fern not populated
- [BUG] "Allow for all projects" permission not applied to pending MCP requests in same session
- [BUG] Plugins and MCP servers become invisible after alternating between Claude Code CLI and Antigravity IDE (VS Code extension)
- [DOCS] VS Code docs are outdated for session list spark icon, plan markdown comments, and `/mcp` management dialog
- [BUG] Running claude code in VS Code integrated terminal spawns 3 blank VS Code windows on Windows
- [BUG] VSCode extension: MCP server env vars from global mcp.json not passed to server process
- [BUG]Gmail / Google Calendar / Google Drive MCP connectors unreachable (NXDOMAIN)
- /mcp reconnect <server> fails with CLI-only "terminal is still starting up" error in VS Code extension
- [BUG] Meta Ads MCP connector consistently times out (30000ms) when accessed from Claude Code IDE extension, but works fine everywhere else
- /mcp reconnect (all or single-server) always fails with "MCP controls aren't available right now" — persists across window reload, full VS Code restart, and OS reboot
- [BUG] MCP write-operation confirmation ("yes") not honored in UI -- works fine in terminal