Skip to content

Installation and Clients

Tran Trung Thanh edited this page Nov 16, 2026 · 1 revision

Installation and Clients

You need Node 20 or newer and a Chromium-based browser (Chrome, Edge, Brave, or Playwright's Chromium).

Claude Code

claude mcp add turbo-browser -- npx -y turbo-browser-mcp

Clients with an mcpServers JSON config

Cursor, Claude Desktop, Antigravity and others:

{
  "mcpServers": {
    "turbo-browser": {
      "command": "npx",
      "args": ["-y", "turbo-browser-mcp"],
      "env": { "TURBO_BROWSER_SAVE_ROOT": "/absolute/path/to/workspace" }
    }
  }
}

TURBO_BROWSER_SAVE_ROOT is the only folder the server may write screenshots, PDFs and storage files to, or read storage files from. If you leave it out, the current working directory is used.

From source

git clone https://github.com/Tthanh2k6/turbo-browser-mcp.git
cd turbo-browser-mcp
npm install
node src/index.mjs --doctor

Check the setup

npx -y turbo-browser-mcp --doctor

--doctor prints Node, Playwright, Chromium and CDP diagnostics as JSON. If no browser is found:

npx playwright-core install chromium

Connection modes

Set with --mode or TURBO_BROWSER_MODE.

Mode What it does
auto (default) Tries a Chrome already listening on http://127.0.0.1:9222 first, so the agent can use a browser you are signed in to. Otherwise it launches headless Chromium.
cdp Attaches to a running Chromium, Chrome or Edge remote debugging port. Change the endpoint with --cdp <url>.
persistent Launches with a reusable profile. Set the folder with --user-data-dir <path>.
launch Starts a clean browser session, headless by default. Use --headed for a visible window.

Other flags, such as --executable <path>, --timeout <ms>, --tools core and --allow-submit, are listed in the README.

Next: Choosing the Right Tool.

Clone this wiki locally