parallel-browser-mcp
Related Servers
Alternatives to parallel-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA multi-agent orchestrator that enables multiple AI agents to share a single Chrome browser instance with tab isolation and shared state. It preserves local browser data like cookies and logins while allowing concurrent agent sessions through the official Playwright MCP.10MIT
- AlicenseNot gradedqualityDmaintenanceEnables browser automation for AI assistants via Playwright, supporting multiple browsers, sessions, and tools for web interaction and testing.1,581 npmMIT
- AlicenseBqualityBmaintenanceEnables multiple AI agents to each run Google's full Chrome DevTools toolset in an isolated Chrome instance with saved logins, origin allowlists, reconnect recovery, and process cleanup. It also provides visibility into running browsers so stale sessions can be inspected or reaped.3817 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.246 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to control multiple independent browser instances in parallel with process-level isolation, supporting any backend MCP server for browser automation.271,627 npm19MIT
- AlicenseNot gradedqualityCmaintenanceLets several AI clients drive one shared, signed-in Chrome at the same time, giving each session its own background tabs and tab group with per-tab leases so mutations queue while reads overlap. Exposes a full Chrome DevTools-style toolset plus Claude's 31-member browser toolset, along with an HTTP endpoint that turns Messages API tool_use blocks into tool_result blocks.MIT
TDQS
Scored across 29 tools
Most tools map to distinct browser actions (click, type, hover, drag, navigate, snapshot, etc.), so an agent can usually choose correctly. However, session_close and browser_close both appear to close the current session, and browser_evaluate vs browser_run_code_unsafe overlap in executing JavaScript.
Names are consistently snake_case and grouped with predictable browser_ and session_ prefixes. Minor deviations include run_parallel without a prefix and a mix of verb-based (browser_click) and noun-based (browser_snapshot, browser_tabs) names.
29 tools is heavy for a single MCP server, even for full browser automation. Most actions are justified, but the redundant close-session tools and niche operations like browser_drop and browser_emulate_media make the surface feel larger than necessary.
The surface covers a broad browser-automation lifecycle: sessions, navigation, interaction, forms, dialogs, screenshots, snapshots, network inspection, and parallel execution. Minor gaps include no forward-navigation or explicit reload tool, though these can be worked around via browser_navigate or browser_evaluate.