Fill whole web forms in one call with Turbo Browser MCP
Turbo Browser MCP is a Playwright based browser server for Claude, Cursor and other agents. It fills a form in one call, returns only what changed on the page, and blocks the final Submit by default. Setup and what I saw testing 0.6.1.
Most browser MCP servers give an agent one action per tool call: click this, type that, take a snapshot, repeat. On a long form that turns into dozens of model turns, and every turn replays a big chunk of page text into the conversation. Turbo Browser MCP is a new open source server, built on Playwright, that tries to do more per call.
It showed up as a Show HN post this week and the repo is only a few days old, so treat it as early software. It is MIT licensed, and version 0.6.1 went out on npm earlier today. I ran that version locally on Linux before writing this.
What it does differently
smart_fill_form fills a whole form in one call: text inputs, selects, checkboxes, comboboxes, rich text editors and file uploads read from disk.
inspect_compact returns a size capped list of the elements on the page, and with onlyChanged it returns just what changed since the last look.
batch_actions runs a list of clicks, key presses and reads as a single call.
Buttons that look like a final commit, such as Submit, Send, Publish, Pay or Confirm, are blocked unless you pass allowSubmit. An agent can prefill a form and leave the last click to you.
It does not hide that the browser is automated. There are no stealth patches and no CAPTCHA solving. For a site with a bot check, wait_for_human hands the tab to a person and carries on afterwards.
There are 11 tools in total. If you also need Lighthouse audits or performance traces, the README itself suggests keeping Chrome DevTools MCP next to it.
Add it to Cursor
You need Node 20 or newer and a Chromium based browser. Add this to your Cursor MCP settings. TURBO_BROWSER_SAVE_ROOT is the only folder the server may write screenshots, PDFs and storage files to; leave it out and it uses the current working directory.
To check your setup first, run the doctor command. It reports the Node version, whether Playwright loaded and which browser it found. If it finds none, install Chromium with the second command.
By default it first looks for a Chrome already listening on port 9222, so an agent can use a browser you are signed in to. If none is there it launches its own headless Chromium.
What I saw when I tested it
The doctor command found the Chrome install on my machine. I then started the server over stdio and pointed it at a small local signup page with a name field, an email field, a plan dropdown, a terms checkbox and a Submit button.
inspect_compact in forms mode listed the five controls with short refs and labels, in a few lines of text instead of a full page snapshot.
One smart_fill_form call filled the name, the email and set the plan dropdown to Pro, and reported that it stopped before submit.
Clicking Submit without allowSubmit was refused with a clear message that the submit guard blocked it. With allowSubmit set, the click went through.
After the submit, inspect_compact with onlyChanged returned just the new confirmation line on the page.
The terms checkbox was the one miss. With the field shapes I tried, the result did not list it as filled or skipped. Check the filled list in the result, and use act_fast with the check action for a stubborn checkbox.
Things to keep in mind
The project is days old and ships several releases a day right now. Pin a version if you want a stable setup.
The README publishes its own benchmarks against other browser stacks and says plainly that they come from one trial per task so far. Read them as a direction, not a result.
Pointing it at a Chrome you are signed in to gives the agent your sessions. The submit guard helps, but only connect a browser profile you are happy for the agent to use.
Find it on PlugMCP
Turbo Browser MCP is listed on PlugMCP with links to the publisher. If you want your own agent to search the directory for browser servers like this one, the PlugMCP directory MCP needs no key.