Repository navigation
Troubleshooting
Start with npx -y turbo-browser-mcp --doctor. It prints Node, Playwright, Chromium and CDP diagnostics as JSON. Include that output in any bug report.
Install Playwright's Chromium:
npx playwright-core install chromiumOr point the server at an existing browser with --executable <path>.
When you enable chrome://inspect/#remote-debugging on the default User Data directory, Chrome asks for approval each time a new WebSocket client connects. That blocks unattended runs. The server has two ways around it:
- Bridge.
--bridge(ornpm run bridge) starts a background daemon onhttp://127.0.0.1:9224that keeps one connection to Chrome open. You click Allow once, and later clients connect without another prompt. The port can be changed withTURBO_BROWSER_BRIDGE_PORT. - Dedicated profile.
--launch-chrome(ornpm run launch-chrome) starts Chrome with--remote-debugging-port=9222and its own profile at~/.turbo-browser-mcp/chrome-profile. The README says this shows no confirmation dialog, even on the first connection.
Refs such as [e12] come from the latest snapshot. After a navigation or a large page change they no longer match. Take a new snapshot with inspect_compact, or use returnSnapshot: true on the action. A missing ref in an error message lists the 3 nearest current refs.
That is the submit guard. The result has a blockedBy field. If you want the click to go through, pass allowSubmit: true on that call. See Submit Guard and Safety.
The server does not bypass bot checks. Use wait_for_human or --open-profile, described in Submit Guard and Safety.
Open an issue with the bug report form, or ask in Discussions.