Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude in Chrome (Beta): mcp__claude-in-chrome__* tools unavailable in VS Code extension — needs official workaround documentation [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52879•Fetched 2026-04-25 06:18:26
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
kasiaalenakasiaalena
Participants
github-actions[bot]github-actions[bot]kasiaalenakasiaalena
Timeline (top)
labeled ×4closed ×1commented ×1

Fix Action

Fix / Workaround

Note: I see this was partially discussed in #23939 (closed "not planned"), but there's no official documentation of a workaround for VS Code users.

Workaround I found

  1. If VS Code support is not planned — please document the Bash workaround officially in https://code.claude.com/docs/en/chrome
  2. If VS Code support is planned — please provide an ETA or reopen #23939
RAW_BUFFERClick to expand / collapse

Environment

  • Claude Code: 2.1.96 (VS Code extension)
  • Claude for Chrome extension: 1.0.66
  • OS: macOS Darwin 25.4.0
  • Chrome: latest stable

Problem

When using the VS Code extension (not CLI), claude-in-chrome MCP server never appears in the MCP servers list, and Chrome tools (mcp__claude-in-chrome__navigate, mcp__claude-in-chrome__read_page, etc.) are not available via ToolSearch.

What I've verified:

  • Native messaging host is installed and running: /Users/kasiaalena/.claude/chrome/chrome-native-host
  • Unix socket is active: /tmp/claude-mcp-browser-bridge-kasiaalena/<PID>.sock
  • Chrome extension is enabled and authenticated
  • claude --chrome in CLI shows: Status: Enabled, Extension: Installed
  • VS Code window was reloaded multiple times
  • mcp.json does not support claude-in-chrome as a regular MCP server entry (no schema support for chrome key in settings.json)

Note: I see this was partially discussed in #23939 (closed "not planned"), but there's no official documentation of a workaround for VS Code users.

Expected behavior

Chrome tools should be accessible in the VS Code extension, consistent with CLI behavior.

Actual behavior

Chrome tools work in claude --chrome CLI session only. In VS Code extension, they are completely unavailable.

Workaround I found

Running claude --chrome -p "prompt" via the Bash tool inside a VS Code session works as a proxy — but this is undocumented and creates a new subprocess for each request (no session continuity, ~15–30s latency per call).

Request

  1. If VS Code support is not planned — please document the Bash workaround officially in https://code.claude.com/docs/en/chrome
  2. If VS Code support is planned — please provide an ETA or reopen #23939

extent analysis

TL;DR

The issue can be temporarily worked around by running claude --chrome -p "prompt" via the Bash tool inside a VS Code session, although this creates a new subprocess for each request with significant latency.

Guidance

  • Verify that the native messaging host and Unix socket are correctly set up and active, as the issue reporter has already done.
  • Check the mcp.json file to ensure it does not contain any incorrect or unsupported configurations that might interfere with the claude-in-chrome MCP server.
  • Consider documenting the Bash workaround in the official Claude documentation as a temporary solution for VS Code users.
  • If VS Code support is planned, reopening issue #23939 might be necessary to track progress and provide an ETA for the fix.

Example

No code snippet is provided as the issue does not require a specific code change, but rather a workaround or documentation update.

Notes

The provided workaround has significant latency and lacks session continuity, making it less than ideal. Official support or documentation for VS Code users is necessary for a more seamless experience.

Recommendation

Apply the workaround by running claude --chrome -p "prompt" via the Bash tool inside a VS Code session, as it provides some functionality despite its limitations, until official support or a better solution is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Chrome tools should be accessible in the VS Code extension, consistent with CLI behavior.

#environment setup#docker error#permission error#memory optimization#batch processing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Claude in Chrome (Beta): mcp__claude-in-chrome__* tools unavailable in VS Code extension — needs official workaround documentation [1 comments, 2 participants]