Chrome control MCP reports success but doesn't launch browser #155
Description
Bug Description
The Chrome control MCP tool returns "Opened [URL] in Chrome" without actually launching a Chrome process.
Environment
- Confirmed in: Claude.ai and Claude Code
- Chrome binary exists at:
/opt/google/chrome/chrome - Chrome not in PATH
Expected vs Actual
- Expected: Chrome launches with URL
- Actual: Success message but no process
- Subsequent calls fail: "Chrome not running"
Root Cause
Tool appears to be AppleScript-based (Mac) but used in Linux environments
Impact
Breaks user workflows with misleading success messages