# Turbo-browser-mcp: a Playwright MCP server with batched tools and submit guards

published: 2026-11-15T08:05:26.785Z
topic: mcp
source: https://github.com/Tthanh2k6/turbo-browser-mcp
url: https://aiagentnews.io/stories/turbo-browser-mcp-a-playwright-mcp-server-with-batched-tools-and-submit-guards

Turbo-browser-mcp is an open-source Playwright-based MCP server that consolidates browser automation into 10 batched tools. Its author reports large reductions in token use and round-trips on form filling, DOM snapshots and uploads.

The server exposes tools such as inspect_compact, which returns compact element snapshots and delta snapshots limited to changed elements, and smart_fill_form, which prefills an entire form in one call. The form engine covers React-controlled inputs, Shadow DOM, iframes, ARIA widgets and contenteditable editors, and passes file paths straight to Playwright so binary data never enters the model context.

The README's benchmarks, run locally on headless Chromium with o200k_base tokenization, report a 10-field form filled in one turn in 82 ms versus 574 ms over 11 turns. A 48 KiB PDF upload via disk path used 85 tokens compared with 44,728 for an inline Base64 argument. The project also lists a network blocking preset set, diagnostics that default to errors only, and path confinement for saved files.

By default, a human-in-the-loop Submit guard blocks final actions resembling Submit, Send, Post, Apply, Confirm or payment triggers unless allowSubmit is passed or the --allow-submit flag is set. The repository is at version 0.4.0 and includes 407 tests according to its README.

## Why it matters if you build agents

Agent builders who fill forms or upload files through MCP can use smart_fill_form and disk-path uploads to cut turns and context size, though the figures are the author's own local benchmarks.

The default Submit guard means agents must explicitly pass allowSubmit to submit forms, so workflows that expect automatic submission will stop before the final action.

Closed Shadow roots on tabs attached before the init script runs, and strict cross-origin sandboxed frames, fall back to coordinate actions and keyboard input, which the README lists as a trade-off.
