chrome-devtools-mcp-broker
Provides per-agent Google Chrome browser sessions and tools to automate Chrome through chrome-devtools-mcp, including opening pages, taking snapshots, interacting with pages, and running browser tools in isolated sessions.
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.
chrome-devtools-mcp-broker
Let several AI agents use Chrome at the same time, each in its own browser.
Why
Google's chrome-devtools-mcp can serve several agents from one server, but they all share one browser:
Agents see each other's pages.
isolatedContextseparates cookies and storage, but every agent'slist_pagesshows the other agents' pages with titles and URLs, andevaluate_scriptcan run on any of them.Agents wait for each other. Browser-wide tools such as
evaluate_script,new_pageor a performance trace run one at a time; while one runs, no other agent's call can start.Large results flood the context. A big snapshot or listing comes back in full.
This broker gives each agent session its own chrome-devtools-mcp worker and temporary Chrome profile, so a session sees only its own pages and never waits for another session's call. It caps each reply at a character budget and caches the full result, so agents can page or filter it without running the action again. It drives the published chrome-devtools-mcp through MCP, unmodified. Evidence: docs/VALIDATION.md.
Related MCP server: SpidexLab's Multi-Tenant Browser MCP
When to use it
You have | Use |
Several agents on one MCP server or client, e.g. parallel subagents | This broker |
Large snapshots or listings you want to page or filter | This broker |
Agents in separate processes, each starting its own server | Upstream with |
Agents that may share pages and mostly navigate, click and fill, or tight memory | Upstream with |
Your own logged-in Chrome ( | Upstream |
Quick start
Requires Node.js 22.12+ and Google Chrome (or Chromium via --chrome-path).
(umask 077; openssl rand -hex 32 > ~/.chrome-broker-token) # once
CHROME_BROKER_TOKEN=$(cat ~/.chrome-broker-token) npx -y chrome-devtools-mcp-broker
# listening at http://127.0.0.1:7331/mcp
claude mcp add --transport http chrome-broker http://127.0.0.1:7331/mcp \
--header "Authorization: Bearer $(cat ~/.chrome-broker-token)"Other clients: see examples/mcp-config.json. Or let the client start its own broker over stdio (no token; one session limit per client):
{ "mcpServers": { "chrome-broker": { "command": "npx", "args": ["-y", "chrome-devtools-mcp-broker", "--transport", "stdio"] } } }Tools
Tool | Purpose |
|
|
| List, search, or get the input schema of upstream tools; does not launch Chrome |
| Run an upstream tool ( |
| Page ( |
Output options for chrome_call and chrome_read: maxChars (reply budget, default 6,000 characters), filter (case-insensitive line match), select (JSON Pointer into the raw result), includeImages.
chrome_session {"action":"open"} -> {"sessionId":"S",...}
chrome_call {"sessionId":"S","tool":"new_page","args":{"url":"https://example.com"}}
chrome_call {"sessionId":"S","tool":"take_snapshot","args":{}} -> first part, "resultId":"R", "nextOffset":N
chrome_read {"sessionId":"S","resultId":"R","filter":"heading"} -> only heading lines
chrome_read {"sessionId":"S","resultId":"R","offset":N} -> next page, no re-run
chrome_session {"action":"close","sessionId":"S"}Page tools act on the session's selected page, so they take no pageId. Calls in one session run in order; different sessions run in parallel.
Configuration
npx -y chrome-devtools-mcp-broker --help lists every option and default. Flags after -- go to every upstream worker:
npx -y chrome-devtools-mcp-broker --max-sessions 8 -- --viewport=1280x720Flags that would break per-session isolation (attaching to an existing browser, a shared profile, and so on) are rejected at startup; see deniedFlags in src/upstream.js.
Security
For one user's trusted agents on their own machine. HTTP binds to 127.0.0.1 and requires the token. It is not a sandbox: pages run JavaScript and Chrome runs as your OS user. Threat model and reporting: SECURITY.md.
Limitations
Each session runs its own worker and Chrome, so memory grows with sessions and tabs. Size
--max-sessionsto fit.A call that times out closes its session; the broker never retries.
Sessions and cached results live in memory; cached results expire after 10 minutes.
Agents run in parallel only if the MCP client sends their calls concurrently.
Verified on macOS only so far.
More
docs/ARCHITECTURE.md: design and trade-offs
docs/VALIDATION.md: measurements and how to reproduce them
Development:
npm ci && npm test(no Chrome needed);CHROME_PATH=/path/to/chrome npm run test:chromefor real-Chrome tests
License
MIT. Independent project, not affiliated with Google.
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.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Let AI agents use your real, signed-in Chrome: tabs, clicks, forms, screenshots and video.
Let AI agents work in your own signed-in Chrome, with approvals and verified results.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables local AI agents to control Chrome in parallel with isolated tab groups, supporting operations like navigation, clicks, and form filling without interference.-
- AlicenseNot gradedqualityDmaintenanceEnables multiple autonomous agents to concurrently control separate tabs in a single Chrome instance, with features like semantic search and network monitoring.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple agents to share a single Chrome browser with isolated tabs and shared sessions, allowing coordinated browsing and automation.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceLets several AI clients drive one shared, signed-in Chrome at the same time, giving each session its own background tabs and tab group with per-tab leases so mutations queue while reads overlap. Exposes a full Chrome DevTools-style toolset plus Claude's 31-member browser toolset, along with an HTTP endpoint that turns Messages API tool_use blocks into tool_result blocks.MIT