MCP servers issues on VS Code — page 2
Issues the maintainers labelled both platform:vscode and area:mcp.
146 issues · 27 open · 119 resolved (82%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is converging. 58 new reports in the last 90 days vs 80 in the 90 before — -28%. The open backlog peaked at 35 in 2026-04 and sits at 27 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
100 of these reports name the Claude Code build they were running, spanning 66 releases. Heaviest reporters:
- Claude Code v2.1.141
- Claude Code v2.1.165
- Claude Code v2.1.231
- Claude Code v2.1.168
- Claude Code v2.1.142
- Claude Code v2.1.119
- Claude Code v2.1.76
- Claude Code v2.1.229
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 29 days across 119 closures. Of the 119 closures with a recorded reason, 22% were closed as completed and 93 as not-planned or duplicate. The most recent completed fix landed in 2026-06.
Workarounds reported by the community
51 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] 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 - [BUG] VSCode extension doesn't load MCP servers on Windows due to drive letter case mismatch in .claude.json project key lookup
- …em Windows Terminal/Shell PowerShell Additional Information Workaround Manually duplicate the project entry in ~/.claude.json with both C:/... and c:/... as keys. Note: these entries will drift out of sync when MCP serve…
Found in the description of #45195 · resolved - [BUG] Windows: case-sensitive `.claude.json` project-key lookup silently drops MCP servers across CLI/VS Code — recurring bug, repeatedly auto-closed unfixed
- …osing this as a duplicate of an already-stale-closed issue. Workaround (drifts, not a fix): duplicate the project entry in under both and keys, each carrying the block, so it resolves regardless of launch surface. These…
Found in the description of #67749 · still open
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 101–146
Ranked by community engagement (reactions weighted over comments).
- [BUG]
- [BUG] VS Code extension: MCP cloud connector OAuth flow doesn't open browser
- [BUG] User-scope plugin MCP server cannot access project directory — no cwd or env var pointing to project root
- mcp-proxy.anthropic.com returns 502 after initial handshake — tool calls never reach backend server
- [Bug] MCP/Plugin Implementation Failures Resulting in Non-Functional Code Generation
- [BUG] VSCode Extension: Power BI MCP server write confirmation prompts are silently declined instead of surfaced to user
- VSCode extension injects MCP venv activate command as user message
- [Bug Report] Unable to process issue - no bug report provided
- VS Code: deny in settings should prevent MCP tools from loading into context, not just block execution
- [FEATURE] Show MCP tool name and arguments in VSCode extension chat
- [BUG] SubAgent MCP tool calls(configured via mcpServers yaml frontmatter in subagent.md) show as blank line in Ctrl+O view
- [BUG] Windows/PowerShell 5.1: bare -- in 'claude mcp add' is stripped by the shell, producing a misleading "missing required argument 'commandOrUrl'"
- /mcp reconnect <server> fails with CLI-only "terminal is still starting up" error in VS Code extension
- [BUG] MCP servers connect successfully but tools don't surface as callable, even after full restart
- [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] Claude Code VS Code extension itself: it doesn't currently load "Local MCPs" (servers added via claude mcp add, stored in .claude.json) into its own chat panel session — only the built-in claude.ai connectors come through.
- [BUG] MCP write-operation confirmation ("yes") not honored in UI -- works fine in terminal
- [FEATURE] Display MCP tool name and arguments in the VS Code extension chat
- [BUG] Hosted MCP connectors (Slack/M365) no longer inject into VS Code extension chat after v2.1.195
- [BUG] GitHub MCP tool calls fail with ByteString error when session contains non-ASCII (Cyrillic) content
- VS Code mcp.json MCP servers not accessible to Claude Code extension tools
- claude.ai connector (Slack) shows Connected in VS Code extension but exposes zero tools to the model
- [BUG]
- VSCode mcp.json gallery and settings.json mcpServers silently launch duplicate MCP server processes for the same name
- [BUG] VS Code extension: deleting a conversation from history does not terminate its stdio MCP server (process orphans until full window restart)
- Windows: VS Code/VSCodium extension fails to spawn stdio MCP servers ("The system cannot find the path specified.") while CLI works
- [BUG]
- [BUG] Claude Code logs "needs-auth / skipping" for account connectors user never enabled, on every session, with no opt-out
- MCP servers added via CLI don't sync to VS Code terminal UI
- [BUG] GitHub MCP server fails with 400 "Authorization header is badly formatted" in VS Code extension, but works fine in terminal
- HTTP MCP server registers as Connected with zero tools when it issues no Mcp-Session-Id
- No way to reauthorize a claude.ai connector (e.g. Datadog) from within the VS Code extension
- [BUG] MCP server shows "Needs Auth" after VSCode restart despite valid token
- [Bug] Increased false positive flagging in MCP Server development workflows
- [BUG] Microsoft Dataverse MCP connector fails with "missing required resultType" on every call in Claude Code (works fine in claude.ai chat)
- [BUG] tool_search_tool_result references a claude.ai connector that was never enabled on the account — session 400s permanently and cannot compact
- [BUG] VS Code extension hardcodes CLAUDE_CODE_ENTRYPOINT=claude-vscode, which suppresses all local stdio MCP servers
- [BUG] MCP servers connect successfully then get torn down with no reconnect on resumed sessions
- [FEATURE] VS Code extension: render MCP `claude/channel` push notifications in the native panel (parity with the terminal TUI)
- claude.ai connector MCP session silently wedges after ~15 min idle — no drop detected, no reconnect; fresh process succeeds on the same call simultaneously
- VS Code extension crashes (exit code 3221225477) when MCP server reports hasResources: true — CLI works fine in terminal
- Conector MCP do ClickUp permanece "não conectado" no Claude Code (extensão VS Code), mesmo autorizado na conta claude.ai e nas configurações da organização
- VS Code extension only exposes tools from locally-configured MCP servers, not claude.ai account connectors
- MCP tool-result images not rendered in VS Code extension chat transcript
- Gmail MCP connector: get_thread fails with "session expired" while search_threads succeeds