A
licenseB
qualityD
maintenanceA concurrent browser MCP server that supports multiple parallel browser instances
20
53 npm
11
Apache 2.0
parallel-browser-mcp
by etairl
Related Servers
Alternatives to parallel-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMulti-instance parallel browser MCP server that manages multiple isolated browser instances in a single Chrome process with automatic login state cloning, allowing parallel independent operations across instances.36MIT
- AlicenseAqualityAmaintenanceAn MCP server that runs concurrent, session-isolated Playwright browser contexts, so many agents can each drive their own browser at the same time without colliding.2311 npm3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for browser automation, exposing tools for tab management, navigation, CDP, action plans, and cleanup.163 npm280MIT
- AlicenseBqualityCmaintenanceA production-ready MCP server that exposes Selenium 4 browser automation as MCP tools.27MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for browser automation with shared authentication and built-in UI auditing.MIT
TDQS
C2.6/5.0
Scored across 26 tools
Disambiguation3/5
Most browser actions are individually clear, but several near-overlapping pairs exist: browser_snapshot, browser_get_page_structure, and browser_dom_query all describe page/DOM inspection, while browser_fill, browser_keyboard_type, browser_click, and browser_mouse_click_xy cover similar input territory. Descriptions reduce some ambiguity, but an agent could still easily select the wrong tool.
Naming Consistency4/5
Session tools follow a clean verb_noun pattern like start_session and close_session, while browser actions consistently use a browser_ prefix followed by descriptive verbs. The mixed prefixes are minor and the naming remains predictable and readable.
Tool Count2/5
With 26 tools, this server sits above the 25+ threshold and feels too heavy for a single MCP surface. Several mouse, keyboard, and DOM primitives could be consolidated or split into a separate server without losing functionality.
Completeness4/5
The toolset covers the core browser automation lifecycle well: navigation, DOM interaction, form filling, mouse/keyboard input, screenshots, uploads, waits, and session management. Notable gaps like tab/window management, cookies, and frame handling are missing, but agents can often work around them via browser_evaluate or separate sessions.
Maintenance
ActivityMaintained
ResponsivenessResponsive