[BUG] Chrome MCP tools never load in VS Code — claude-vscode MCP fails with -32601: Method not found (Windows 11)

Resolved 💬 5 comments Opened Feb 7, 2026 by FaustianAGI Closed Mar 15, 2026

Description

Chrome browser tools (mcp__claude-in-chrome__*) never load into VS Code extension sessions on Windows 11. The /chrome command in CLI shows Status: Enabled, Extension: Installed (both green), but browser tools are never available in either CLI or VS Code sessions.

Root cause identified: the claude-vscode MCP server (the bridge between the VS Code extension and the Claude process) fails during startup with MCP error -32601: Method not found. Since Chrome tools are injected through this channel, they never register.

Environment

  • OS: Windows 11
  • Claude Code CLI (npm global): 2.1.19
  • Claude Code VS Code Extension: 2.1.34 (anthropic.claude-code-2.1.34-win32-x64)
  • Chrome: Latest stable
  • Chrome Extension: Claude in Chrome (Beta), installed from Chrome Web Store
  • Node.js: v20.20.0 (via nvm-windows)

Key diagnostic findings

1. claude-vscode MCP fails at startup

From VS Code Output > Claude VSCode logs:

[ERROR] MCP server "claude-vscode" Failed to fetch tools: MCP error -32601: Method not found

This is the only MCP server that fails. Trello connects fine. GitLab fails on expected auth issue. No Chrome/browser-related log lines appear at all — the Chrome MCP connection is never attempted.

2. Named pipe is alive and healthy

The native messaging host creates the pipe and it accepts connections:

> node test-pipe.js
Expected pipe name: \.\pipe\claude-mcp-browser-bridge-kenne
SUCCESS: Connected to pipe!

3. All config is correct

  • Registry: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension → points to correct JSON
  • Native host config: Points to chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/ (correct extension ID)
  • Bat file: C:\Users\kenne\.claude\chrome\chrome-native-host.bat exists, points to correct node/CLI path
  • VS Code binary: claude.exe at resources/native-binary/ exists and runs (--version returns 2.1.34)
  • /chrome status: Shows Enabled + Installed (green)
  • Chrome restarted: Multiple times after setup

4. Startup log shows zero Chrome initialization

Full startup sequence loads:

  • Trello MCP ✅
  • GitLab plugin (auth expected) ⚠️
  • claude-vscode ❌ Method not found
  • Chrome/browser: completely absent

Steps to reproduce

  1. Windows 11 with Claude Code VS Code extension 2.1.34
  2. Install Claude in Chrome extension from Chrome Web Store
  3. Run claude --chrome in terminal, run /chrome — shows Status: Enabled, Extension: Installed
  4. Restart Chrome
  5. Open VS Code, start new Claude Code conversation
  6. Try @browser go to google.com or any browser tool
  7. Browser tools are not available — falls back to WebFetch/WebSearch
  8. Check Output > Claude VSCode — see claude-vscode MCP error

Expected behavior

Chrome browser tools (mcp__claude-in-chrome__*) should be available in VS Code sessions after Chrome extension is installed and /chrome shows enabled.

Likely cause

The claude-vscode MCP channel is the bridge through which the VS Code extension injects Chrome tools into the Claude process. The -32601: Method not found JSON-RPC error suggests a protocol mismatch — the extension calls a method the Claude binary doesn't recognize (or vice versa).

Related issues

  • #21371 — Chrome extension not connecting (40 upvotes, Windows-specific)
  • #22000 — Windows 11 unable to connect to Chrome (named pipe crash)
  • #23218 — Windows 11 not connecting (socket path discovery fix)
  • #23539 — Windows configuration correct but not connecting

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗