A Model Context Protocol (MCP) server that enables AI assistants like Claude to control Chrome browsers through a Chrome extension and WebSocket communication. Perfect for cross-platform automation, especially WSL/Windows setups.

• Browser Automation: Navigate, click, scroll, fill forms, take screenshots
• Cross-Platform: Works across WSL/Windows network boundaries
• Dual Communication: Native messaging (local) + WebSocket (network)
• Claude Integration: Direct integration with Claude Code and Claude Desktop
• Real-time Control: Live browser interaction through MCP tools
• Chrome Extension: Easy-to-install browser extension with popup controls

┌─────────────┐    WebSocket     ┌─────────────┐    MCP/stdio    ┌─────────────┐
│   Windows   │ ←─────────────→  │     WSL     │ ←─────────────→ │ Claude Code │
│   Chrome    │   ws://IP:9222   │   Server    │                 │             │
│ + Extension │                  │             │                 │             │
└─────────────┘                  └─────────────┘                 └─────────────┘

• Node.js >= 18.0.0
• Chrome/Chromium browser
• TypeScript (for development)

1. Clone the repository

   git clone https://github.com/deoxy/chrome-pilot.git
   cd chrome-pilot

2. Install dependencies

   cd server
   npm install
   npm run build

3. Start the WebSocket server

   node dist/index.js --websocket

4. Load Chrome extension

   • Open chrome://extensions/
   • Enable "Developer mode"
   • Click "Load unpacked"
   • Select the extension folder

5. Configure extension

   • Click extension icon
   • Enter WebSocket URL: ws://YOUR_IP:9222/ws
   • Click "Save Configuration" and "Reconnect"

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "chrome-pilot": {
      "command": "node",
      "args": ["/path/to/chrome-pilot/server/dist/index.js", "--websocket"],
      "env": {}
    }
  }
}

Add to Claude Desktop settings:

{
  "mcpServers": {
    "chrome-pilot": {
      "command": "node",
      "args": ["/path/to/chrome-pilot/server/dist/index.js"]
    }
  }
}

ip route | grep default

# Run as Administrator
New-NetFirewallRule -DisplayName "Chrome MCP Server" -Direction Inbound -Port 9222 -Protocol TCP -Action Allow

1. Access extension via \\wsl$\Ubuntu\path\to\chrome-pilot\extension
2. Load in Windows Chrome
3. Configure WebSocket URL in popup
4. Test connection

curl http://localhost:9222/info
curl -X POST http://localhost:9222/command \
  -H "Content-Type: application/json" \
  -d '{"action": "get_tabs", "params": {}}'

Can you navigate to google.com and take a screenshot?

chrome-pilot/
├── server/                 # MCP Server (TypeScript)
│   ├── src/
│   │   ├── index.ts        # Main server entry
│   │   ├── websocket-server.ts    # WebSocket server
│   │   ├── native-host.ts  # Native messaging
│   │   └── tools/          # Browser automation tools
│   ├── package.json
│   └── tsconfig.json
├── extension/              # Chrome Extension
│   ├── manifest.json       # Extension config
│   ├── background-websocket.js   # Service worker
│   ├── content.js          # Content script
│   ├── popup.html          # Extension popup
│   └── popup.js
├── native-host/            # Native messaging setup
│   ├── install.sh          # Installation script
│   └── com.chrome_mcp.host.json.template
└── docs/                   # Documentation

• Verify WebSocket URL in extension popup
• Check WSL IP address hasn't changed
• Ensure server is running on correct port
• Check Windows firewall settings

• Restart Chrome extension
• Verify "Connected" status in popup
• Check server logs for errors
• Ensure extension has necessary permissions

• Use ethernet connection for best performance
• Monitor network latency between WSL and Windows
• Consider running on fixed IP

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request

MIT License - see LICENSE file for details.

• Built with MCP SDK by Anthropic
• Uses Chrome Extension APIs for browser automation
• WebSocket communication for cross-platform support

• Create an issue for bug reports
• Check documentation for detailed guides
• See network setup guide for WSL/Windows configuration