BUG: claude-in-chrome MCP fails - npm package @anthropic-ai/claude-in-chrome-mcp not published (404)

Description

The claude-in-chrome MCP server fails to connect because it tries to run npx @anthropic-ai/claude-in-chrome-mcp@latest, but this package does not exist on the npm registry (returns HTTP 404).

Steps to Reproduce

1. Install Claude Code CLI 2.1.79
2. Install the Claude Chrome extension (v1.0.62)
3. Run /chrome → Status: Enabled, Extension: Installed
4. Run claude mcp list → chrome-browser: npx @anthropic-ai/claude-in-chrome-mcp@latest - ✗ Failed to connect
5. Try using any mcp__claude-in-chrome__* tool → "No Chrome extension connected"

Error

npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@anthropic-ai%2fclaude-in-chrome-mcp - Not found
npm error 404 The requested resource '@anthropic-ai/claude-in-chrome-mcp@latest' could not be found

Environment

• Claude Code: 2.1.79
• Chrome extension: v1.0.62 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
• macOS Darwin 25.3.0 (Apple Silicon)
• Chrome: 146.0.7680.80
• Native messaging host: correctly configured
• No Claude Desktop installed (removed to avoid conflicts)
• /chrome shows Status: Enabled, Extension: Installed

Expected Behavior

The @anthropic-ai/claude-in-chrome-mcp package should be published to npm, or the MCP server should use the built-in mechanism instead of an external npm package.

Workaround

Using @playwright/mcp with Chromium works as an alternative for browser automation.