mcp-browser-parallel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 |
|---|---|
| browser_connectA | Connect to an existing Chrome browser via CDP and extract auth cookies. Chrome must be running with --remote-debugging-port. This also extracts cookies/storage so new instances can be created without re-login. |
| instance_createA | Create a new isolated browser instance. Auth (cookies/localStorage) is automatically cloned from the connected Chrome, so no re-login is needed. Each instance has fully isolated state. |
| instance_listA | List all active browser instances with their current URLs and titles. |
| instance_closeB | Close a specific browser instance and release its resources. |
| instance_close_allA | Close all browser instances. |
| page_navigateB | Navigate an instance to a URL. |
| page_snapshotA | Take an accessibility snapshot of the page. Returns a structured text representation with refs for interactive elements. Always use this before performing actions to understand the current page state. |
| page_clickB | Click an element identified by ref from the latest page_snapshot. |
| page_fillB | Clear and fill text into an input element identified by ref. |
| page_typeA | Type text into editable element. By default fills at once; set slowly=true to type character by character. |
| page_select_optionB | Select option(s) in a element. |
| page_hoverC | Hover over an element. |
| page_press_keyC | Press a key or key combination (e.g. "Enter", "Control+a", "Escape"). |
| page_screenshotC | Take a screenshot of the page or a specific element. |
| page_waitC | Wait for text to appear, disappear, or a specified time. |
| page_evaluateB | Evaluate a JavaScript expression in the page context. Returns JSON-serializable result. |
| page_maximizeB | Maximize the browser window for an instance via CDP protocol. |
| page_navigate_backB | Go back to the previous page in history. |
| page_resizeB | Resize the browser viewport for an instance. |
| page_dragB | Drag an element and drop it onto another element. |
| page_file_uploadB | Upload one or multiple files via a file input element. |
| page_fill_formC | Fill multiple form fields at once. |
| page_handle_dialogA | Handle a browser dialog (alert, confirm, prompt). Must be called when a dialog is open. |
| page_console_messagesC | Return all console messages captured from the page. |
| page_network_requestsA | Return all network requests since the page was loaded. |
| page_run_codeB | Run a Playwright code snippet against the instance page. For advanced use cases. |
| page_mouse_click_xyB | Click at specific coordinates on the page. |
| page_mouse_move_xyC | Move the mouse to specific coordinates. |
| page_mouse_drag_xyB | Drag from one point to another using coordinates. |
| page_pdf_saveC | Save the page as a PDF file. |
| page_verify_text_visibleB | Verify that text is visible on the page. |
| page_verify_element_visibleB | Verify that an element with a specific role and name is visible. |
| page_verify_valueC | Verify the value of a form element. |
| page_generate_locatorB | Generate a Playwright locator string for the given element, useful for test code generation. |
| page_start_tracingC | Start a Playwright trace recording for debugging. |
| page_stop_tracingB | Stop the trace recording and save to file. |
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 36 tools
Each tool has a clear, distinct purpose. Even similar actions like click vs mouse_click_xy are differentiated by targeting element vs coordinates. Fill, fill_form, and type are distinct in scope and behavior.
All tools follow a consistent category_verb pattern in snake_case. Prefixes like browser_, instance_, page_ clearly indicate the scope. Multi-word verbs are used consistently.
With 36 tools, the set is larger than typical recommendations (25+). However, the browser automation domain inherently requires many distinct actions. The count is borderline but justified by the comprehensive coverage.
The tool set covers the full lifecycle of browser interactions: connection, instance management, navigation, all major user actions, state inspection (snapshot, console, network), debugging (tracing), and output (screenshot, PDF). No obvious gaps.