MCP servers issues on VS Code — page 2
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 101–176
Ranked by community engagement (reactions weighted over comments).
- [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]
- Connected HTTP MCP server's tools never appear in tool registry (ToolSearch) even after full app restart
- [BUG] `roots/list` is incorrect on Windows
- 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] GitHub plugin fails with missing environment variable error
- [BUG]
- [BUG] IDE diagnostics (mcp__ide__getDiagnostics) unavailable in the VS Code embedded-panel runtime
- [Bug] MCP Server Configuration Failed During Setup
- [Bug] MCP setup issue
- [Bug] MCP servers not activating/mcp
- [Bug] MCP Server Setup Failed
- Chrome MCP: Failed to parse tabs_context response: SyntaxError
- I don't see any bug report or issue description in your message. Please provide the bug report or issue details that you'd like me to create a GitHub issue title for.
- MCP Elicitation support for write confirmations (Power BI Modeling MCP Server)
- I need more information to generate an appropriate GitHub issue title. "Unaccurated" is too vague. Could you please provide: 1. What specific feature or behavior is inaccurate? 2. What is the expected behavior vs. actual behavior? 3. Any error messages or
- [BUG] VS Code extension cannot connect to SSE MCP servers that require POST method
- Skill tool's forked execution describes plugin skills instead of running them; ignores `context` frontmatter field
- Claude in Chrome (Beta): mcp__claude-in-chrome__* tools unavailable in VS Code extension — needs official workaround documentation
- [Bug] Slack MCP connector footer causes self-mention loop with Claude app
- Wasting time and tokens and not following directions
- I'm Claude, an AI assistant made by Anthropic. I don't have any memory of previous conversations or context about "Boris," version 4.7, or any incidents you're referring to. If you'd like to report a bug for Claude Code, please provide: 1. A clear descri
- [BUG] HTTP MCP server behind basic auth: stale mcpOAuth entry in .credentials.json forces OAuth flow on every session
- [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] VS Code extension still auto-declines MCP form elicitation (onElicitation not wired) — 2.1.287
- VS Code: MCP permission prompts show only the tool name, not what the call does
- [BUG] VSCode extension's /mcp OAuth flow ignores configured --callback-port (uses a different port than the terminal CLI)
- [Bug] MCP tool approval in planning mode not persisting between iterations
- [BUG] VS Code integrated-browser MCP tools hang forever: action completes in browser but result never returns; session stuck until manual interrupt
- [Bug] MCP server validation bypassed when remote-settings is empty
- [BUG] HTTP MCP client appears to send an unexpected MCP-Protocol-Version header after initialize, causing spec-compliant servers to reject all follow-up requests
- [BUG] Windows/PowerShell 5.1: bare -- in 'claude mcp add' is stripped by the shell, producing a misleading "missing required argument 'commandOrUrl'"
- [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
- [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.
- MCP tool-result images not rendered in VS Code extension chat transcript
- [FEATURE] Display MCP tool name and arguments in the VS Code extension chat
- Gmail MCP connector: get_thread fails with "session expired" while search_threads succeeds
- [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
- MCP connector stuck on a false "Needs Auth" in VS Code; re-authorizing cannot clear it — only disabling and re-enabling the server in /mcp
- [BUG] claude.ai connectors silently missing for the whole session when the connector-list fetch gets a 401 at first launch of the day — 401 is never retried, even after the token refresh succeeds
- [BUG] claude.ai Gmail connector: "session expired" and tools vanish after /mcp Reconnect (VS Code, Windows)
- [BUG] VS Code terminal mode: daemon-hosted session can never hold the IDE connection (front-end keeps reclaiming it), so mcp__ide__* tools are missing
- [BUG] Sanity MCP server fails to connect — malformed .well-known discovery URL (missing /)
- Agent continues running after user demands stop; assistant falsely confirms termination and deflects blame to user
- [BUG] claude.ai connectors show "Connected" but unusable across all Claude products
- [BUG] MCP connector tools logged as "added" but unresolvable via ToolSearch for the rest of the session
- [BUG] VS Code config probe starts every MCP server (spawnConfigProbe never sets strictMcpConfig)
- [BUG] VS Code extension: prompts from a remote (HTTP) MCP server never appear in the slash-command picker — `commands_changed` is stored but never read
- [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