A
licenseA
qualityC
maintenanceMulti-agent Playwright MCP server with tab isolation via targetId, enabling multiple agents to share a single Chrome browser while maintaining isolated tab groups and shared sessions.
14
19 npm
3
MIT
playwright-mcp-tabbed
by songofhawk
Related Servers
Alternatives to playwright-mcp-tabbed
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn 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.238 npm4MIT
- FlicenseNot 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.10-
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.5,484 npm57-
- AlicenseNot gradedqualityBmaintenanceLets many AI agent sessions share one real logged-in browser, each with its own tab group, using standard Playwright MCP tools.356 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.8,987,267 npmApache 2.0
TDQS
B3.2/5.0
Scored across 23 tools
Disambiguation3/5
Most tools target distinct actions, but browser_run_code and browser_evaluate overlap heavily as JavaScript execution tools. browser_tabs bundles list/create/close tab operations while browser_context_info also describes tabs, adding some boundary ambiguity.
Naming Consistency4/5
The browser_ prefix is used consistently and most tools follow a verb_object style. The main deviations are noun-style names like browser_tabs, browser_context_info, browser_network_requests, and browser_console_messages, plus loose forms like browser_wait_for.
Tool Count3/5
23 tools is on the heavy side for an MCP server, though the browser automation scope justifies much of the surface. The count could be tightened by merging or removing the overlapping JS execution tools.
Completeness4/5
The toolset covers navigation, interaction, forms, uploads, drag-and-drop, dialogs, waiting, screenshots, accessibility snapshots, console logs, network requests, tabs, and browser lifecycle. Minor gaps like cookie/storage management and an explicit reload/new-page tool exist, but core automation workflows have no dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues