Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Playwright MCP-compatible browser automation bridge for CloakBrowser Chromium.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cloakbrowser": {
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp"
],
"env": {
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "your-value",
"PLAYWRIGHT_MCP_HEADLESS": "your-value",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "your-value",
"PLAYWRIGHT_MCP_CODEGEN": "your-value",
"PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "your-value",
"PLAYWRIGHT_MCP_TIMEOUT_SETTLE": "your-value",
"PLAYWRIGHT_MCP_USER_DATA_DIR": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK": "your-value",
"CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cloakbrowser --env PLAYWRIGHT_MCP_BROWSER_ENGINE=your-value --env PLAYWRIGHT_MCP_HEADLESS=your-value --env PLAYWRIGHT_MCP_OUTPUT_DIR=your-value --env PLAYWRIGHT_MCP_CODEGEN=your-value --env PLAYWRIGHT_MCP_SNAPSHOT_BOXES=your-value --env PLAYWRIGHT_MCP_TIMEOUT_SETTLE=your-value --env PLAYWRIGHT_MCP_USER_DATA_DIR=your-value --env CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS=your-value --env CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS=your-value --env CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK=your-value --env CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH=your-value --env CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS=your-value -- npx -y cloakbrowser-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cloakbrowser": {
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp"
],
"env": {
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "your-value",
"PLAYWRIGHT_MCP_HEADLESS": "your-value",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "your-value",
"PLAYWRIGHT_MCP_CODEGEN": "your-value",
"PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "your-value",
"PLAYWRIGHT_MCP_TIMEOUT_SETTLE": "your-value",
"PLAYWRIGHT_MCP_USER_DATA_DIR": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK": "your-value",
"CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"cloakbrowser": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp"
],
"env": {
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "your-value",
"PLAYWRIGHT_MCP_HEADLESS": "your-value",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "your-value",
"PLAYWRIGHT_MCP_CODEGEN": "your-value",
"PLAYWRIGHT_MCP_SNAPSHOT_BOXES": "your-value",
"PLAYWRIGHT_MCP_TIMEOUT_SETTLE": "your-value",
"PLAYWRIGHT_MCP_USER_DATA_DIR": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS": "your-value",
"CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK": "your-value",
"CLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH": "your-value",
"CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS": "your-value"
}
}
}
}PLAYWRIGHT_MCP_BROWSER_ENGINE envPLAYWRIGHT_MCP_HEADLESS envPLAYWRIGHT_MCP_OUTPUT_DIR envPLAYWRIGHT_MCP_CODEGEN envPLAYWRIGHT_MCP_SNAPSHOT_BOXES envPLAYWRIGHT_MCP_TIMEOUT_SETTLE envPLAYWRIGHT_MCP_USER_DATA_DIR envCLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS envCLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS envCLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK envCLOAK_PLAYWRIGHT_MCP_GEOIP_PROXY_MATCH envCLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026
The registry name was verified with the GitHub account swimmwatch, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Needs the server’s tool list first; this check starts in the next step
Compared only with servers in this prototype, not the whole registry.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (1.15.1) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
cloakbrowser-mcp is a drop-in Playwright MCP-compatible browser automation server with unchanged upstream tools, CloakBrowser Chromium, and production-ready npm, Docker, and Streamable HTTP packaging. It runs upstream @playwright/mcp as the canonical tool surface and points that runtime at CloakBrowser.
Run npx -y cloakbrowser-mcp@latest, connect Claude Desktop or Codex CLI, ask for web research, daily automation, or testing in plain English, and inspect the real browser result.
Documentation: swimmwatch.github.io/cloakbrowser-mcp · Comparison · Recipes
Use it when you need:
chromium.connectOverCDP();Cross-platform checks cover npm on Linux x64/arm64, macOS arm64/x64, and Windows x64 across the Node.js versions listed in Testing. Docker images are built and smoke-tested for linux/amd64 and linux/arm64.
See @playwright/mcp vs cloakbrowser-mcp when deciding whether plain upstream Playwright MCP or CloakBrowser MCP fits a deployment better. The Recipes pages show task-focused setup paths for persistent login profiles, Chrome extensions, reverse proxies, regional QA, client connections, and CI smoke tests.
npx -y cloakbrowser-mcp@latest
Requires Node.js 22.13+ in the 22.x line, or Node.js 24+. Run diagnostics before wiring a client:
npx -y cloakbrowser-mcp@latest doctor
For Streamable HTTP instead of stdio:
npx -y cloakbrowser-mcp@latest --transport streamable-http --http-port 3000
See the generated CLI Reference for all flags.
docker run --rm -i \
-v "$PWD/artifacts:/data" \ swimmwatch/cloakbrowser-mcp:latest
For Streamable HTTP:
docker run --rm -p 127.0.0.1:3000:3000 \
-v "$PWD/artifacts:/data" \ swimmwatch/cloakbrowser-mcp:latest \ --transport streamable-http --http-host 0.0.0.0 --http-port 3000
The Docker image writes artifacts to /data and is published for linux/amd64 and linux/arm64. It defaults to CLOAK_PLAYWRIGHT_MCP_NO_SANDBOX=true for compatibility with containerized runtimes where Chromium sandboxing is often unavailable. If your host and container runtime support Chromium sandboxing, set CLOAK_PLAYWRIGHT_MCP_NO_SANDBOX=false; for untrusted pages, keep container network access and mounted host directories tightly scoped. The same tags are also available from ghcr.io/swimmwatch/cloakbrowser-mcp. See Docker for persistent profiles, extension mounts, HTTPS, and smoke-test examples, or use the reverse proxy recipe for a focused Streamable HTTP deployment.
codex mcp add cloakbrowser -- npx -y cloakbrowser-mcp@latest
claude mcp add --transport stdio cloakbrowser -- npx -y cloakbrowser-mcp@latest
{
"servers": { "cloakbrowser": { "type": "stdio", "command": "npx", "args": ["-y", "cloakbrowser-mcp@latest"] } } }
mcpServers ClientsAdd this server entry to the client's MCP JSON config:
{
"mcpServers": { "cloakbrowser": { "command": "npx", "args": ["-y", "cloakbrowser-mcp@latest"] } } }
{
"mcpServers": { "cloakbrowser": { "command": "docker", "args": [ "run", "--rm", "-i", "-v", "/tmp/cloakbrowser-artifacts:/data", "swimmwatch/cloakbrowser-mcp:latest" ] } } }
npx -y cloakbrowser-mcp@latest --transport streamable-http --http-port 3000
codex mcp add cloakbrowser --url http://127.0.0.1:3000/mcp claude mcp add --transport http cloakbrowser http://127.0.0.1:3000/mcp
Paste this into Codex, Claude Code, Copilot, Cursor, Cline, Windsurf, or a similar coding assistant that can edit MCP config:
Install the CloakBrowser MCP server for this workspace. Name it "cloakbrowser".
Prefer stdio with command "npx" and args ["-y", "cloakbrowser-mcp@latest"]. If this client uses VS Code mcp.json, add it under "servers" with type "stdio". If this client uses Claude/Cursor/Cline/Windsurf/Warp-style config, add it under "mcpServers" with the same command and args. Do not add secrets.
More examples are in Getting Started, with dedicated recipes for Claude Desktop and Codex CLI.
Use upstream PLAYWRIGHT_MCP_* variables for browser, artifacts, timeouts, network, and tool capability settings. Cloak-specific bridge toggles use CLOAK_PLAYWRIGHT_MCP_*. Select a Pro Preview browser build before startup with --release-channel preview or CLOAK_PLAYWRIGHT_MCP_RELEASE_CHANNEL=preview; the default is stable.
The common variable table now lives in Configuration. That page also covers persistent profiles, validated context options, Chrome extensions, Streamable HTTP metadata, and HTTPS/auth options. See GeoIP Proxy Matching for regional proxy behavior, Humanized Input Behavior for interaction realism, and Recipes for task-focused configurations.
| cloakbrowser-mcp | @playwright/mcp | CloakBrowser | Node.js | Platform | ||
|---|---|---|---|---|---|---|
1.15.1 | ^0.0.83 | ^0.6.3 | `^22.13.0 | >=24.0.0` | npm on Linux x64/arm64, macOS arm64/x64, Windows x64; Docker linux/amd64, linux/arm64 | |
1.15.0 | ^0.0.83 | ^0.6.3 | `^22.13.0 | >=24.0.0` | npm on Linux x64/arm64, macOS arm64/x64, Windows x64; Docker linux/amd64, linux/arm64 | |
1.14.1 | ^0.0.82 | ^0.5.10 | `^22.13.0 | >=24.0.0` | npm on Linux x64/arm64, macOS arm64/x64, Windows x64; Docker linux/amd64, linux/arm64 | |
1.14.0 | ^0.0.82 | ^0.5.10 | `^22.13.0 | >=24.0.0` | npm on Linux x64/arm64, macOS arm64/x64, Windows x64; Docker linux/amd64, linux/arm64 |
| 1.13.0 | ^0.0.80 | ^0.5.10 | ^22.13.0 || >=24.0.0 | npm on Linux x64/arm64, macOS arm64/x64, Windows x64; D