playwright-mcp-parallel
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@playwright-mcp-parallelcreate two browser instances logged into example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
playwright-mcp-parallel
Drop-in parallel enhancement over @playwright/mcp
Run multiple isolated browser instances simultaneously, each with its own context, auth, and state.
Why playwright-mcp-parallel?
Standard @playwright/mcp supports only one browser instance per server. This package extends it to support N parallel instances, enabling:
š Parallel task execution ā Run multiple browser tasks at the same time
š Auth cloning ā Clone cookies/localStorage from your logged-in Chrome to all new instances
š§© Isolated contexts ā Each instance has fully independent state
š Drop-in compatible ā All original
@playwright/mcptools available viapage_*prefix
Related MCP server: playwright-mcp-orchestrator
Installation & Setup
Claude Desktop / Cursor / VS Code / Any MCP client
{
"mcpServers": {
"playwright-parallel": {
"command": "npx",
"args": [
"playwright-mcp-parallel@latest"
]
}
}
}With options (headless, etc.)
{
"mcpServers": {
"playwright-parallel": {
"command": "npx",
"args": [
"playwright-mcp-parallel@latest",
"--headless"
]
}
}
}Tools Reference
š Connection & Auth
Tool | Description |
| Connect to an existing Chrome via CDP and extract auth (cookies + localStorage). Chrome must be started with |
| Export auth state from a specific instance (or the connected Chrome). Updates global auth so new instances will inherit it. |
š„ļø Instance Management
Tool | Description |
| Create a new isolated browser instance. Optionally auto-clone auth from connected Chrome. |
| List all active instances with their current URLs and titles. |
| Close a specific instance and release its resources. |
| Close all instances at once. |
š Browser Tools (All Original @playwright/mcp tools)
All tools from @playwright/mcp are available with a page_ prefix and require an instanceId parameter:
Tool | Description |
| Navigate an instance to a URL |
| Click an element in an instance |
| Type text into an element |
| Take a screenshot of an instance |
| Get accessibility snapshot of an instance |
| Execute JavaScript in an instance |
| Wait for a condition in an instance |
... | All other |
Usage Examples
Typical Workflow: Auth Cloning + Parallel Tasks
1. Start Chrome with debugging:
chrome.exe --remote-debugging-port=9222
2. Log in manually in Chrome
3. In your AI agent:
ā browser_connect() # Extract auth from Chrome
ā instance_create({ instanceId: "task-1", url: "https://app.example.com" })
ā instance_create({ instanceId: "task-2", url: "https://app.example.com" })
ā (Both instances are logged in automatically!)
4. Run tasks in parallel:
ā page_browser_click({ instanceId: "task-1", ... })
ā page_browser_click({ instanceId: "task-2", ... })
5. Export auth from a running instance (e.g., after login flow):
ā instance_export_auth({ instanceId: "task-1" })
ā instance_create({ instanceId: "task-3" }) # Also logged inExport Auth from Instance
ā instance_create({ instanceId: "login-bot", url: "https://example.com/login" })
ā page_browser_click({ instanceId: "login-bot", ... }) # complete login
ā instance_export_auth({ instanceId: "login-bot" }) # export & set as global auth
ā instance_create({ instanceId: "worker-1" }) # inherits login state
ā instance_create({ instanceId: "worker-2" }) # inherits login stateCLI Options
All @playwright/mcp CLI options are supported:
npx playwright-mcp-parallel@latest [options]Option | Description |
| Run browser in headless mode |
| Browser to use: |
| Viewport size, e.g. |
| Path to user data directory |
| Path to storage state JSON file |
| Proxy server, e.g. |
| Disable sandbox |
| Port for SSE transport |
| Keep browser profile in memory only |
For the full list of options, see @playwright/mcp documentation.
How It Works
playwright-mcp-parallel
āāā Management Layer
ā āāā browser_connect ā Extract auth from existing Chrome
ā āāā instance_create ā Launch isolated browser + clone auth
ā āāā instance_list ā List active instances
ā āāā instance_close ā Dispose instance
ā āāā instance_close_all ā Dispose all
ā āāā instance_export_auth ā Export cookies/localStorage from instance
ā
āāā Per-Instance Tool Dispatch
āāā page_* tools ā routed to the correct BrowserBackend by instanceIdEach instance_create call launches a new Chromium process with an isolated context. Auth state (cookies + localStorage) extracted via browser_connect or instance_export_auth is automatically injected into new contexts.
Differences from @playwright/mcp
Feature | @playwright/mcp | playwright-mcp-parallel |
Browser instances | 1 | Unlimited |
Parallel execution | ā | ā |
Auth cloning | ā | ā |
Auth export | ā | ā |
Original tools | ā | ā
(via |
Drop-in config | ā | ā |
Requirements
Node.js >= 18
Any MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.)
License
Apache-2.0 ā based on @playwright/mcp by Microsoft.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceEnables browser automation and web scraping with multi-session management, supporting page navigation, element interaction, network request capture, and content extraction across multiple concurrent browser instances.11MIT
- Flicense-qualityDmaintenanceA 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
- AlicenseBqualityDmaintenanceEnables AI agents to control multiple independent browser instances in parallel with process-level isolation, supporting any backend MCP server for browser automation.272,58416MIT
- 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
Related MCP Connectors
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Browser MCP for logged-in tasks. Uses your Chrome ā credentials stay local. Zero-token replay.
Automate cloud browsers to navigate websites, interact with elements, and extract structured data.ā¦
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mokecy/playwright-mcp-parallel'
If you have feedback or need assistance with the MCP directory API, please join our Discord server