turbo-browser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURBO_BROWSER_MODE | No | Browser launch mode: auto (tries CDP, then persistent dir, then launch), cdp, persistent, or launch. | auto |
| TURBO_BROWSER_CDP_URL | No | CDP endpoint when attaching to an open Chrome/Edge session. | http://127.0.0.1:9222 |
| TURBO_BROWSER_HEADLESS | No | Run headless or open a visible browser window. | true |
| TURBO_BROWSER_EXECUTABLE | No | Override Chromium/Chrome/Edge/Brave binary path. | |
| TURBO_BROWSER_TIMEOUT_MS | No | Default navigation and action timeout in ms. | 15000 |
| TURBO_BROWSER_ALLOW_SUBMIT | No | Permit Submit/Publish clicks globally without passing allowSubmit: true per call. | false |
| TURBO_BROWSER_USER_DATA_DIR | No | Browser profile directory for persistent mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Fill several fields, comboboxes ({ref, option}) and uploads with one smart_fill_form. Chain steps with batch_actions (returnSnapshot=true for the end state). After the first inspect_compact use onlyChanged=true; * marks new refs. Use refs from the latest snapshot.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tabs_batchC | Tab operations in one call: list, open/open_many, navigate, activate, resize, emulate, reload, back/forward, close. |
| inspect_compactC | List interactive elements (with refs), forms or readable sections across frames and open Shadow DOM, capped at maxChars. |
| smart_fill_formB | Fill several fields at once: inputs, editors, comboboxes, selects, checkboxes, Shadow DOM/iframe fields, file uploads. Stops before Submit by default. |
| act_fastC | One action on a ref, selector, text or x/y. Supports returnSnapshot; blocks submit/publish/send unless allowSubmit=true. |
| batch_actionsB | Run actions or smart_fill_form steps in order, including navigate/extract for multi-page reading. Stops on Submit guard blocks; optional post-batch snapshot. |
| extract_clean_textC | Extract readable text or markdown from the main content and iframes, capped at maxChars. |
| evaluate_jsB | Evaluate JavaScript in a frame or element (ref/selector/text passes el and arg); returns JSON. |
| page_diagnosticsC | Read buffered console logs, network requests, downloads and dialogs for a tab. |
| capture_pageC | Screenshot (png/jpeg) or PDF of the page or an element, saved under cwd or TURBO_BROWSER_SAVE_ROOT; optional inline image. |
| network_sessionC | Manage browser cookies, localStorage/sessionStorage, Playwright storageState files, quick blocking presets (turbo, no-images, no-media, clean), and custom resource/URL blocking. |
| wait_for_humanB | Let a human do a step (login, bot check, 2FA) in the visible browser; wait until a condition holds, then continue in the same session. Only waits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: inspection, extraction, diagnostics, capture, storage, and human-wait are well separated. Some overlap exists between act_fast (single action), batch_actions (ordered actions including navigation/extraction), and smart_fill_form (multi-field filling), while navigation also appears inside tabs_batch, but the descriptions generally clarify when to use each.
All names use snake_case, but the conventions are mixed: some are verb_noun (extract_clean_text, capture_page), some noun_noun (page_diagnostics, network_session), and some adjective_verb or noun_verb (smart_fill_form, act_fast, tabs_batch). The names are readable but not a predictable pattern throughout.
Eleven tools is well-scoped for a browser automation server. The set covers tab management, inspection, actions, extraction, diagnostics, capture, storage/network control, and human handoff without excessive fragmentation.
The surface covers the major browser automation lifecycle: tabs, element discovery, form filling, actions, batching, text extraction, JS evaluation, diagnostics, screenshots/PDFs, cookies/storage, and human-in-the-loop waiting. Minor gaps remain for explicit scroll/drag/keyboard primitives, but these may be handled through act_fast or evaluate_js.