loading…
Search for a command to run...
loading…
A multi-agent orchestrator that enables multiple AI agents to share a single Chrome browser instance with tab isolation and shared state. It preserves local bro
A 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.
Multi-agent orchestrator for Playwright MCP — multiple AI agents sharing one Chrome browser with tab isolation. Local-first, preserving your real browser state (cookies, logins, extensions, localStorage).
The official @playwright/mcp only supports a single agent per browser. When multiple Claude Code agents (or any MCP clients) try to use it simultaneously, they fight over the same tabs and interfere with each other.
Existing workarounds all sacrifice something:
--isolated mode gives each agent a fresh profile (no saved logins/cookies)--user-data-dir per agent means separate profiles (no shared state)ultimate-playwright-mcp, concurrent-browser-mcp) are unmaintained or don't share profilesUse a single Chrome instance with CDP (Chrome DevTools Protocol) as the shared backend, and orchestrate multiple @playwright/mcp sessions on top — each scoped to its own tabs.
┌─────────────────────────────────────────────┐
│ Chrome (one instance) │
│ --remote-debugging-port=9222 │
│ --user-data-dir=<profile> │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ Agent 1 │ │ Agent 2 │ │ Agent 3 │ tabs │
│ │ tabs │ │ tabs │ │ tabs │ │
│ └────┬────┘ └────┬────┘ └────┬────┘ │
└───────┼──────────┼──────────┼───────────────┘
│ │ │ CDP (ws://127.0.0.1:9222)
┌───────┼──────────┼──────────┼───────────────┐
│ ▼ ▼ ▼ │
│ ┌────────────────────────────────┐ │
│ │ playwright-mcp-orchestrator │ │
│ │ │ │
│ │ - Tab group isolation │ │
│ │ - Session routing │ │
│ │ - Uses official @playwright/mcp│ │
│ └────────────────────────────────┘ │
└─────────────────────────────────────────────┘
@playwright/mcp — not a reimplementation. New tools and features from Microsoft are available automatically.--remote-debugging-port.Early development. The CDP foundation has been validated:
--remote-debugging-port=9222 + --user-data-dir worksplaywright-core connections via connectOverCDP to the same browser workChrome 136+ silently ignores --remote-debugging-port on the default profile directory. You must use --user-data-dir pointing to a non-default path.
# Quit Chrome first
osascript -e 'tell application "Google Chrome" to quit'
# Copy profile
cp -r ~/Library/Application\ Support/Google/Chrome /tmp/chrome-cdp-profile
# Launch with CDP
open -a "Google Chrome" --args \
--user-data-dir=/tmp/chrome-cdp-profile \
--remote-debugging-port=9222
curl -s http://127.0.0.1:9222/json/version
| Project | Stars | Issue |
|---|---|---|
@playwright/mcp (official) |
— | Single agent only. Issues #893, #1294 open. |
ultimate-playwright-mcp |
1 | Full reimplementation, abandoned after 1 day. Can't track official updates. |
concurrent-browser-mcp |
— | Isolated ephemeral instances, no shared profile. |
playwright-parallel-mcp |
— | Separate processes, separate profiles. |
mcp-playwright-cdp |
47 | CDP but no tab isolation. Abandoned. |
| Framework | Stars | Issue for our use case |
|---|---|---|
| Browser Use | 80k | Single-session locally. Cloud for concurrency. |
| Stagehand/Browserbase | 21k | Cloud-only shared state. Not local. |
| Agent Browser (Vercel) | 21k | CLI, not MCP. No tab isolation. CDP still maturing. |
| Dev Browser | 3.8k | Skill, not MCP. Same multi-agent gap (#33). |
| Skyvern | 21k | Vision-first, different paradigm. |
No well-maintained project provides: real user profile + multiple concurrent agents + tab isolation + MCP interface. This project aims to be the first.
MIT
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"playwright-mcp-orchestrator": {
"command": "npx",
"args": []
}
}
}