Browser Pool MCP
A dynamic browser pool MCP server that gives each agent its own isolated browser, enabling concurrent browser automation without conflicts.
README
π₯οΈ Browser Pool MCP
Dynamic browser pool MCP server β every agent gets its own isolated browser.
English | δΈζζζ‘£
A Model Context Protocol server that wraps
Microsoft's @playwright/mcp and
turns it into a dynamic browser pool: each unique caller gets its own
isolated Chrome instance, so multiple Claude Code sessions, subagents, or any
MCP clients can run browser automation concurrently without conflicts.
β¨ Features
- π§© Per-agent isolation β each unique
_agent_idgets its own browser. No more"Browser is already in use"errors when multiple agents hit the browser at once. - π On-demand spawning β browsers are lazily started on first use (local CLI, ~1s), never pre-allocated.
- π§Ή Auto-cleanup β idle instances are killed after 30 min; orphaned instances from crashed wrappers are cleaned on startup.
- π‘οΈ Never kills busy agents β when the pool is full, the wrapper evicts only idle instances; if all are busy it waits, so a running agent's browser is never yanked away.
- π Backward compatible β calling tools without
_agent_idshares one "default" browser, preserving original single-session behavior. - π Full Playwright toolset β all
@playwright/mcptools (navigate, click, type, screenshot, evaluate, tabs, networkβ¦), no feature loss.
π§ Architecture
Claude Code main session ββstdioββ> playwright-pool-mcp (this server)
β
βββ agent "A" ββSSEββ> @playwright/mcp :9000 ββ> Chrome A
βββ agent "B" ββSSEββ> @playwright/mcp :9001 ββ> Chrome B
βββ agent "C" ββSSEββ> @playwright/mcp :9002 ββ> Chrome C
βββ "default" ββSSEββ> @playwright/mcp :9003 ββ> Chrome D
The wrapper does not control Chrome directly. It spawns @playwright/mcp
instances on demand and proxies MCP tool calls to them, adding per-agent routing.
π Quick Start
Prerequisites
- Node.js β₯ 18
- npm
Install
git clone <your-repo-url> playwright-pool-mcp
cd playwright-pool-mcp
npm install
# First-time Chromium download (if needed):
npx playwright install chromium
Configure Claude Code
User-level global config (~/.claude.json):
{
"mcpServers": {
"playwright-pool": {
"type": "stdio",
"command": "node",
"args": ["/path/to/playwright-pool-mcp/playwright-pool-script.js"],
"env": {
"BROWSER_POOL_BASE_PORT": "9000",
"BROWSER_POOL_MAX_INSTANCES": "10",
"BROWSER_POOL_GLOBAL_MAX": "12",
"BROWSER_POOL_INSTANCE_TIMEOUT_MS": "1800000",
"BROWSER_POOL_DEBUG": "0"
}
}
}
}
Restart Claude Code. Tools appear as mcp__playwright-pool__*.
π‘ Usage
Mode 1: Shared (backward compatible)
Omit _agent_id β all calls share one "default" browser:
mcp__playwright-pool__browser_navigate(url="https://example.com")
mcp__playwright-pool__browser_snapshot()
Mode 2: Isolated per agent (recommended)
Pass _agent_id β each unique value gets its own browser:
subagent A: mcp__playwright-pool__browser_navigate(url="https://news.ycombinator.com", _agent_id="agent-a")
subagent B: mcp__playwright-pool__browser_navigate(url="https://github.com/trending", _agent_id="agent-b")
subagent C: mcp__playwright-pool__browser_navigate(url="https://www.baidu.com", _agent_id="agent-c")
β οΈ Important: pass the same
_agent_idacross all calls from one agent to keep its browser state (cookies, login, navigation). Different agents use different values.
Subagent template
Create .claude/agents/web-worker.md:
---
name: web-worker
description: Run browser tasks (scraping / research / testing / automation)
tools: mcp__playwright-pool__*, Read, Bash
---
Use mcp__playwright-pool__* tools to operate the browser.
**Key rule: pass the `_agent_id` parameter on every browser tool call.**
The main conversation may dispatch multiple web-workers concurrently; different
workers must use different `_agent_id` values so each gets its own isolated browser.
Examples:
- mcp__playwright-pool__browser_navigate(url="...", _agent_id="worker-1")
- mcp__playwright-pool__browser_evaluate(function="...", _agent_id="worker-1")
Use the same `_agent_id` for all calls within one worker.
π οΈ Tools
All tools accept an optional _agent_id parameter. Aligned 1:1 with @playwright/mcp v0.0.78.
βΉοΈ Element targeting: interaction tools use
target(snapshot ref or CSS selector). Therefparameter is accepted as an alias fortarget(Claude Code's client maps it).
| Tool | Description |
|---|---|
browser_navigate |
Navigate to a URL |
browser_navigate_back |
Go back |
browser_snapshot |
Accessibility tree (LLM-friendly) |
browser_take_screenshot |
Screenshot (PNG/JPEG) |
browser_click |
Click element |
browser_type |
Type text into element |
browser_press_key |
Press keyboard key |
browser_hover |
Hover element |
browser_select_option |
Select dropdown option |
browser_drag / browser_drop |
Drag & drop |
browser_evaluate |
Run JavaScript |
browser_wait_for |
Wait for condition |
browser_find |
Find text in page snapshot |
browser_fill_form |
Fill multiple form fields (JSON array of {name, target, type, value}) |
browser_tabs |
Manage tabs |
browser_resize |
Resize window |
browser_handle_dialog |
Handle alert/confirm |
browser_file_upload |
Upload files |
browser_console_messages |
Get console logs |
browser_network_requests / browser_network_request |
Network activity |
browser_mouse_move_xy / browser_mouse_click_xy / browser_mouse_drag_xy / browser_mouse_down / browser_mouse_up / browser_mouse_wheel |
Mouse control (screen coordinates) |
browser_run_code_unsafe |
Run arbitrary code (dangerous) |
browser_close |
Close browser for this agent |
pool_status |
Pool status (per agent) |
βοΈ Configuration
All config via environment variables in ~/.claude.json β no code changes needed:
| Variable | Default | Description |
|---|---|---|
BROWSER_POOL_BASE_PORT |
9000 |
Starting port for browser instances |
BROWSER_POOL_MAX_INSTANCES |
10 |
Max concurrent browsers per wrapper (β300MB RAM each) |
BROWSER_POOL_GLOBAL_MAX |
0 (disabled) |
Global max browsers across ALL wrapper sessions (multiple Claude Code windows). File-lock based counter in ~/.browser-pool/. Set e.g. 12 to cap total instances across every session. |
BROWSER_POOL_INSTANCE_TIMEOUT_MS |
1800000 |
Idle timeout (30 min) |
BROWSER_POOL_DEBUG |
0 |
Set 1 for debug logging to debug.log |
Changes take effect after restarting Claude Code.
π‘ Global limit (
BROWSER_POOL_GLOBAL_MAX): each Claude Code window runs its own wrapper, andBROWSER_POOL_MAX_INSTANCESlimits only that wrapper. To cap browser instances across ALL sessions (e.g. two windows must share a total of 12), setBROWSER_POOL_GLOBAL_MAXto the same value in every session's config. Slots are counted via a lock-protected counter file (~/.browser-pool/global-count) and are released when instances close or the wrapper exits gracefully.
π How It Works
- Any browser tool call arrives β wrapper extracts
_agent_id(defaults to"default") - Looks up the per-agent assignment map β reuse existing browser if alive
- If none: check the global limit (
BROWSER_POOL_GLOBAL_MAX) β find a free port β spawn local@playwright/mcpCLI (node cli.js --port X --isolated) - Mark the instance
busyduring the call, so eviction never kills an in-flight call - Pool full? Evict only idle instances (oldest first); if all busy, wait up to 60s
- Idle > 30 min β auto-killed; wrapper startup scans for orphaned instances and cleans them (PPID-guarded, never kills another live session's browsers)
- Global slot accounting: acquired before spawn, released when the instance closes or the wrapper exits gracefully
π¦ Dependencies
@modelcontextprotocol/sdkβ MCP protocol@playwright/mcpβ browser automation enginezodβ schema validation
π License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.