Turbo Browser MCP logo

Turbo Browser MCP

Playwright MCP server for batched browser actions, compact snapshots, form filling, and guarded submissions.

Install Turbo Browser MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "turbo-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "turbo-browser-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 11 tools correctly ().

Overview

turbo-browser-mcp provides Playwright-based browser automation through 11 MCP tools designed to complete multiple browser operations per call. It can fill complex forms, batch actions and navigation, return only changed page elements, capture files, inspect diagnostics, and manage browser state. Final-submit controls are blocked by default, with optional human handoff for CAPTCHA or other bot checks. Reach for it when reducing agent turns and repeated page text matters more than stealth automation.

Use cases

  • Fill multi-field forms and upload files in one call
  • Batch navigation and text extraction across several pages
  • Inspect only page elements changed since the last snapshot
  • Capture screenshots or PDFs from automated browser sessions
  • Pause for human completion of bot checks

Key features

  • Playwright browser automation over MCP
  • Batched actions and multi-page extraction
  • Compact and delta page snapshots
  • Form filling with rich inputs and file uploads
  • Default protection against final-submit actions
  • Browser storage, diagnostics, screenshots, and PDF tools

Tools11

What Turbo Browser MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

What it can do

From the 11 tools this server returned when we ran it; 11 declare their own safety hints.

Can delete or modify data · 3Handles credentials · 1Makes network requests · 10Read-only tools · 8
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age1 days
Maintainers1

Observed 2026-11-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 20h ago via OSV.dev · turbo-browser-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars127Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed11Callable tools this server registers over MCP.

How Turbo Browser MCP works

What turbo-browser-mcp does

turbo-browser-mcp exposes browser automation through the Model Context Protocol and Playwright. Its 11 tools cover browser and tab lifecycle, compact page inspection, form completion, direct page actions, batched workflows, text extraction, JavaScript evaluation, diagnostics, screenshots and PDFs, network or storage state, and human-assisted steps.

The server is aimed at workflows where one MCP call can replace several individual browser actions. smart_fill_form handles complete forms, including React inputs, selects, comboboxes, rich-text editors, checkboxes, and file uploads. batch_actions can combine clicks, key presses, form operations, page navigation, and extraction. inspect_compact can limit output to elements that changed after an earlier snapshot.

How it works

The default auto mode first checks for a Chrome-compatible browser listening on http://127.0.0.1:9222. If none is available, it launches Chromium. Other modes attach to an existing browser through CDP, reuse a persistent profile, or launch a clean session. Supported browser sources include Playwright's cache and installed Chrome, Edge, Brave, or Chromium binaries.

Tabs can use separate cookie and storage contexts through isolatedContext. Multiple URLs can be opened concurrently, with a maximum concurrency of 10. Navigation in batch workflows uses GET in the same tab and waits for domcontentloaded.

Submit-like controls such as Submit, Send, Publish, Pay, and Confirm are blocked by default, including equivalents in several Asian languages. A call can opt in with allowSubmit: true, or the server can start with --allow-submit. wait_for_human pauses for a person to complete a step and then resumes in the same session.

Setup and configuration

Node.js 20 or newer and a Chromium-based browser are required. Install the package with npx -y turbo-browser-mcp, or clone the repository, run npm install, and start node src/index.mjs.

Claude Code can register the server with claude mcp add turbo-browser -- npx -y turbo-browser-mcp. Clients using an mcpServers JSON configuration can launch the same command with npx and the package name. Run npx -y turbo-browser-mcp --doctor to check the setup; npx playwright-core install chromium installs Playwright's Chromium when needed.

TURBO_BROWSER_SAVE_ROOT restricts where screenshots, PDFs, and storage files may be written or read. If omitted, the working directory is used. Set TURBO_BROWSER_TOOLS=core, or pass --tools core, to expose only the six core tools: tabs_batch, inspect_compact, smart_fill_form, act_fast, batch_actions, and extract_clean_text.

Tools and capabilities

  • tabs_batch manages tabs, browser lifecycle, navigation, resizing, emulation, and isolated contexts.
  • inspect_compact returns capped snapshots of interactive elements, forms, article text, or all supported content.
  • smart_fill_form fills fields, editors, selects, checkboxes, and file inputs in one call.
  • act_fast performs a single page action, while batch_actions runs ordered steps and can verify expected URLs, text, selectors, or new text.
  • extract_clean_text returns page text or compact Markdown; evaluate_js runs an expression or element function.
  • page_diagnostics, capture_page, network_session, and wait_for_human cover diagnostics, screenshots or PDFs, resource and storage controls, and human intervention.

The server returns short initialization instructions recommending batched form fields, batched action steps, changed-only snapshots after the first inspection, and references from the latest snapshot.

Limitations and notes

The automation intentionally does not use stealth patches, fingerprint changes, or CAPTCHA solving. Sites with bot checks may require a person to take over through wait_for_human. Submit protection can be overridden per call or globally, so workflows that enable it should include their own confirmation or duplicate-submission checks. File and storage access is constrained by TURBO_BROWSER_SAVE_ROOT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Turbo Browser MCP

turbo-browser-mcp is an MCP server that connects AI agents to Chromium-based browsers through Playwright. Its main tools handle tab management, compact inspection, full-form filling, single and batched actions, text extraction, diagnostics, screenshots, storage, and human handoff for browser automation workflows.

Install it with Node.js 20 or newer by running `npx -y turbo-browser-mcp`, then configure that command in your MCP client. Run `npx -y turbo-browser-mcp --doctor` to check the setup, and use `npx playwright-core install chromium` if Playwright cannot find a browser.

Yes, turbo-browser-mcp works with Cursor through an `mcpServers` JSON configuration. Set the command to `npx`, pass `-y` and `turbo-browser-mcp` as arguments, and optionally define `TURBO_BROWSER_SAVE_ROOT` for controlled file and storage access.

Leave submit protection enabled, which is the default. Submit-like controls are blocked unless a call sets `allowSubmit: true` or the server starts with `--allow-submit`; use `stopBeforeSubmit` with `smart_fill_form` when you want the workflow to end after prefilling.

Yes, in its default `auto` mode it first probes a Chrome-compatible browser at `http://127.0.0.1:9222`. It can attach through CDP, reuse a persistent profile, or launch its own Chromium session depending on the selected mode and browser availability.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTurbo Browser MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/turbo-browser-mcp?style=directory)](https://allmcps.com/mcp/turbo-browser-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/turbo-browser-mcp"><img src="https://allmcps.com/api/badge/turbo-browser-mcp?style=directory" alt="Turbo Browser MCP on AllMCPs" /></a>