CloakBrowser MCP — Claude Code MCP server: browser automation
Wires CloakBrowser Chromium browser automation into your coding agent. Useful when the agent should visit pages itself and report what it found.
claude mcp add --env PLAYWRIGHT_MCP_BROWSER_ENGINE=<PLAYWRIGHT_MCP_BROWSER_ENGINE> --env PLAYWRIGHT_MCP_HEADLESS=<PLAYWRIGHT_MCP_HEADLESS> --env PLAYWRIGHT_MCP_OUTPUT_DIR=<PLAYWRIGHT_MCP_OUTPUT_DIR> --env PLAYWRIGHT_MCP_CODEGEN=<PLAYWRIGHT_MCP_CODEGEN> --env PLAYWRIGHT_MCP_SNAPSHOT_BOXES=<PLAYWRIGHT_MCP_SNAPSHOT_BOXES> --transport stdio cloakbrowser-mcp -- npx -y cloakbrowser-mcpWhat CloakBrowser MCP does
The server boots the @playwright/mcp runtime and aims it at CloakBrowser Chromium. Tool names stay identical to upstream Playwright MCP, with two extra local introspection tools on top. Ship it via npm or Docker, over stdio or Streamable HTTP.
Session-scoped CDP access is opt-in: clients that speak CDP attach through chromium.connectOverCDP(). Persistent browser profiles, Chrome extension loading and GeoIP-matched proxies for regional QA are all supported. Mouse, keyboard and scroll input is humanized, which shows up on flows that react to how you interact.
npm installs need Node.js 22.13+ on the 22.x line, or Node.js 24+. Run npx -y cloakbrowser-mcp@latest doctor before wiring a client. Docker images are built and smoke-tested for linux/amd64 and linux/arm64.
What it helps with
- let the agent open a page and pull data off it
- walk a signup flow in a real browser and find the break
- run regional QA through a proxy that matches the location
- keep a login alive across runs with a persistent profile
- load a Chrome extension into the automation session
Example prompts for the agent
- Open the pricing page and list every plan name in a table
- Run through signup on the staging site and show me where the form fails
- Start the browser with a persistent profile and confirm the login survived
How to install CloakBrowser MCP
Platform CLI
claude mcp add --env PLAYWRIGHT_MCP_BROWSER_ENGINE=<PLAYWRIGHT_MCP_BROWSER_ENGINE> --env PLAYWRIGHT_MCP_HEADLESS=<PLAYWRIGHT_MCP_HEADLESS> --env PLAYWRIGHT_MCP_OUTPUT_DIR=<PLAYWRIGHT_MCP_OUTPUT_DIR> --env PLAYWRIGHT_MCP_CODEGEN=<PLAYWRIGHT_MCP_CODEGEN> --env PLAYWRIGHT_MCP_SNAPSHOT_BOXES=<PLAYWRIGHT_MCP_SNAPSHOT_BOXES> --transport stdio cloakbrowser-mcp -- npx -y cloakbrowser-mcpReplace <…> with your own values. 14 more environment variables are in the server README
Platform CLI
codex mcp add cloakbrowser-mcp --env PLAYWRIGHT_MCP_BROWSER_ENGINE=<PLAYWRIGHT_MCP_BROWSER_ENGINE> --env PLAYWRIGHT_MCP_HEADLESS=<PLAYWRIGHT_MCP_HEADLESS> --env PLAYWRIGHT_MCP_OUTPUT_DIR=<PLAYWRIGHT_MCP_OUTPUT_DIR> --env PLAYWRIGHT_MCP_CODEGEN=<PLAYWRIGHT_MCP_CODEGEN> --env PLAYWRIGHT_MCP_SNAPSHOT_BOXES=<PLAYWRIGHT_MCP_SNAPSHOT_BOXES> -- npx -y cloakbrowser-mcpReplace <…> with your own values. 14 more environment variables are in the server README
Config file
{
"mcpServers": {
"cloakbrowser-mcp": {
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp"
],
"env": {
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "<PLAYWRIGHT_MCP_BROWSER_ENGINE>",
"PLAYWRIGHT_MCP_HEADLESS": "<PLAYWRIGHT_MCP_HEADLESS>",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "<PLAYWRIGHT_MCP_OUTPUT_DIR>",
"PLAYWRIGHT_MCP_CODEGEN": "<PLAYWRIGHT_MCP_CODEGEN>",
"PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "<PLAYWRIGHT_MCP_SNAPSHOT_BOXES>"
}
}
}
}Replace <…> with your own values. 14 more environment variables are in the server README
Config file
{
"servers": {
"cloakbrowser-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp"
],
"env": {
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "<PLAYWRIGHT_MCP_BROWSER_ENGINE>",
"PLAYWRIGHT_MCP_HEADLESS": "<PLAYWRIGHT_MCP_HEADLESS>",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "<PLAYWRIGHT_MCP_OUTPUT_DIR>",
"PLAYWRIGHT_MCP_CODEGEN": "<PLAYWRIGHT_MCP_CODEGEN>",
"PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "<PLAYWRIGHT_MCP_SNAPSHOT_BOXES>"
}
}
}
}Replace <…> with your own values. 14 more environment variables are in the server README
Platform CLI
gemini mcp add -e PLAYWRIGHT_MCP_BROWSER_ENGINE=<PLAYWRIGHT_MCP_BROWSER_ENGINE> -e PLAYWRIGHT_MCP_HEADLESS=<PLAYWRIGHT_MCP_HEADLESS> -e PLAYWRIGHT_MCP_OUTPUT_DIR=<PLAYWRIGHT_MCP_OUTPUT_DIR> -e PLAYWRIGHT_MCP_CODEGEN=<PLAYWRIGHT_MCP_CODEGEN> -e PLAYWRIGHT_MCP_SNAPSHOT_BOXES=<PLAYWRIGHT_MCP_SNAPSHOT_BOXES> cloakbrowser-mcp npx -y cloakbrowser-mcpReplace <…> with your own values. 14 more environment variables are in the server README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about CloakBrowser MCP
How do I install CloakBrowser MCP in Claude Code?
Run claude mcp add cloakbrowser-mcp -- npx -y cloakbrowser-mcp. For environment variables, use the variant with --env flags and --transport stdio.
What does CloakBrowser MCP do?
It is a browser automation MCP server: it runs @playwright/mcp against CloakBrowser Chromium. The tool surface matches upstream Playwright MCP.
What do I need to run it?
Node.js 22.13+ on the 22.x line, or Node.js 24+. Diagnostics: npx -y cloakbrowser-mcp@latest doctor.
