Purpose: To provide browser automation capabilities for AI agents. It uses the open-source @playwright/mcp as a unified tool interface and points the runtime to CloakBrowser Chromium, and can be used as a replacement for Playwright MCP.
Main capabilities: Retains the upstream browser tools, adding only two additional local introspection tools (cloakbrowser_binary_info returns CloakBrowser package, platform, cache, and resolved binary information; cloakbrowser_bridge_info returns bridge metadata, upstream package version, and local tool names). Supports persistent browser profiles, validated context options, loading Chrome extensions, GeoIP proxy matching for regional QA, human-like mouse/keyboard/scroll behavior, and session-level controlled CDP access for CDP-capable clients (chromium.connectOverCDP()).
Usage: Can be started with npx -y cloakbrowser-mcp@latest, or use the Docker image; supports stdio and Streamable HTTP transports. The Docker image writes artifacts to /data, defaults CLOAK_PLAYWRIGHT_MCP_NO_SANDBOX=true, and the Chromium sandbox can be enabled by setting it to false. Configuration follows the upstream PLAYWRIGHT_MCP_* variables, while bridge switches use CLOAK_PLAYWRIGHT_MCP_*; use --release-channel preview or CLOAK_PLAYWRIGHT_MCP_RELEASE_CHANNEL=preview to select the Pro Preview build, defaulting to stable. The server entry can be added to the mcpServers configuration of MCP clients such as Claude Desktop, Cursor, Cline, Windsurf, and VS Code.
Limitations and requirements: Requires Node.js 22.13+ (22.x line) or Node.js 24+. Regarding security, when handling untrusted pages, container network access and mounted directories should be strictly restricted. The upstream Playwright MCP tool list is authoritative; this project does not reimplement its browser architecture.
The materials do not provide specific pricing, performance data, or complete installation command examples; the above content is based on publicly available information on the official page.
