{
  "id": 20119801,
  "title": "Show HN: Turbo-Browser-MCP – Batch forms, DOM deltas and submit guards for MCP",
  "url": "https://urgent.news/2026/11/15/show-hn-turbo-browser-mcp-batch-forms-dom-deltas-and-submit-guards",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-15T04:09:11.000Z",
  "source": {
    "name": "Hacker News",
    "slug": "hacker-news",
    "url": "https://github.com/Tthanh2k6/turbo-browser-mcp"
  },
  "original_language": "en",
  "account": "Turbo-Browser-MCP is a Playwright-based Model Context Protocol (MCP) server designed to reduce LLM token waste and multi-turn latency in browser automation. It combines 25-33 fine-grained browser primitives into 10 batched tools, offering delta DOM snapshots, single-turn form prefill for React/Shadow DOM/iframe, direct disk file uploads, parallel tab sessions, network blocking presets, and a default human-in-the-loop Submit guard. All benchmarks were conducted on headless Chromium locally using exact OpenAI o200k_base tokenization, with specific figures sourced from the benchmark.mjs file (npm run benchmark) and npm run benchmark. Eliminating 10 round-trips on a 10-field form results in a 7x reduction in browser execution time (from 574 ms to 82 ms) and a 10-fold decrease in separate LLM inference round-trips (timeframes ranging from 2-5 seconds per turn during agent loops) plus approximately 71,800 replayed history tokens. Turbo-Browser-MCP charges an LLM round-trip for every snapshot, field fill, selection, upload, and verification check, in contrast to standard MCP servers. Each turn re-sends the expanding conversation history back into the model. The server features a prefilled form in a single MCP call, while simultaneously flushing microtasks and macrotasks between controlled inputs. To run the benchmark suite, users must have Chromium and Playwright installed. The environment and methodology involve headless Chromium via playwright-core, with the exact OpenAI o200k_base tokens measured using Python tiktoken (approx-bpe fallback if unavailable). Cumulative workflow tokens model standard chat-history replay across N sequential turns, calculated as the sum from 1 to N of (N - i + 1) multiplied by Ti, plus a one-shot baseline where the first turn captures context before acting. Turbo-Browser-MCP is compared against installed MCP JSON schemas on disk with compact parameter schemas lacking annotations. Turbo-Browser-MCP is intended for rapid multi-step UI automation, forms, and scraping with minimal token overhead. In situations where Chrome DevTools MCP is needed alongside Turbo-Browser-MCP, the Chrome DevTools MCP provides additional features such as Lighthouse audits, performance trace analysis, CSS computed style panels, V8 heap snapshots, and a built-in WebSocket in DevToolsActivePort for remote debugging in Chrome 136+/144+.",
  "summary": null,
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}