Open Source · DevTool
Docker containers running Playwright MCP and Chrome DevTools MCP servers with built-in anti-detection, cookie import, and browser signature spoofing. One container per project, no conflicts.
[+] Creating krakalaken-browsers-mealmatch-1 Started [+] Creating krakalaken-browsers-erp-1 Started [+] Creating krakalaken-browsers-wordpress-1 Started [+] Creating krakalaken-browsers-resumes-1 Started [+] Creating krakalaken-browsers-kreeder-1 Started # 5 isolated browser instances. Zero conflicts.
Each project gets its own isolated browser
Three steps to isolated browser automation
Clone the repo and drop your exported cookies into the shared directory.
Add container entries to docker-compose.yml. One service per project.
Point your AI agent’s MCP config at the container’s SSE endpoint. Done.
Zero Conflicts
Each project gets its own isolated browser instance. No session conflicts, no cookie cross-contamination, no port collisions between parallel agent sessions.
Stay Under the Radar
Built-in fingerprint spoofing and browser signature randomization. Navigate authenticated pages without triggering bot detection.
Two Protocols, One Stack
Playwright MCP for web app testing, Chrome DevTools MCP for extension development. Both protocols in the same infrastructure.
No Manual Login
Export cookies and IndexedDB from your logged-in browser. Containers replay your session automatically — no manual login required.
# Quick start $ git clone https://github.com/kenpodragon/browser-mcp-containers.git $ cd browser-mcp-containers/docker $ cp ../storageState.json shared/ $ docker compose up -d # Connect: http://localhost:9100/sse
Also by Stephen Salaka