playwright-mcp-orchestrator
Enables multiple AI agents to interact with a single Google Chrome instance simultaneously, providing tab isolation and maintaining shared state like cookies, logins, and extensions via the Chrome DevTools Protocol (CDP).
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
playwright-mcp-orchestrator
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 Problem
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:
--isolatedmode gives each agent a fresh profile (no saved logins/cookies)Separate
--user-data-dirper agent means separate profiles (no shared state)Community alternatives (
ultimate-playwright-mcp,concurrent-browser-mcp) are unmaintained or don't share profiles
Related MCP server: agentic-playwright-mcp
The Approach
Use 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│ │
│ └────────────────────────────────┘ │
└─────────────────────────────────────────────┘Key design decisions
Delegates to official
@playwright/mcp— not a reimplementation. New tools and features from Microsoft are available automatically.Shared user profile — all agents see the same cookies, logins, localStorage.
Tab isolation — each agent operates on its own tabs, no interference.
CDP connection — connects to a running Chrome instance via
--remote-debugging-port.
Status
Early development. The CDP foundation has been validated:
Chrome 145 with
--remote-debugging-port=9222+--user-data-dirworksMultiple
playwright-coreconnections viaconnectOverCDPto the same browser workEach connection can create and manage its own tabs independently
All connections share the same BrowserContext (cookies, logins, storage)
Chrome Setup
Chrome 136+ silently ignores --remote-debugging-port on the default profile directory. You must use --user-data-dir pointing to a non-default path.
Copy your profile (preserves all logins)
# 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=9222Verify CDP is working
curl -s http://127.0.0.1:9222/json/versionResearch
Why not existing solutions?
Project | Stars | Issue |
| — | |
| 1 | Full reimplementation, abandoned after 1 day. Can't track official updates. |
| — | Isolated ephemeral instances, no shared profile. |
| — | Separate processes, separate profiles. |
| 47 | CDP but no tab isolation. Abandoned. |
Why not other browser frameworks?
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. |
The multi-agent shared-profile problem is unsolved
No well-maintained project provides: real user profile + multiple concurrent agents + tab isolation + MCP interface. This project aims to be the first.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
Real Chrome for coding agents over MCP: browse, replay playbooks, human takeover, HIPAA & BAA.
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Related MCP Servers
- AlicenseAqualityDmaintenanceMulti-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.1412 npm3MIT
- AlicenseNot gradedqualityBmaintenanceLets many AI agent sessions share one real logged-in browser, each with its own tab group, using standard Playwright MCP tools.18 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables multiple agents to share a single Chrome browser with isolated tabs and shared sessions, allowing coordinated browsing and automation.18 npmMIT

Dooza Browserofficial
AlicenseNot gradedqualityCmaintenanceGives AI agents a single shared, logged-in Chrome they can drive over MCP or plain HTTP: open and read tabs, click, type, upload files, run short Playwright scripts, hand off whole web tasks to a cheaper model, and keep per-site memory. Agents work in background windows they own without stealing the user's mouse or closing their tabs.MIT