Server data from the Official MCP Registry
Playwright MCP bridge that runs upstream browser tools with the CloakBrowser Chromium binary.
Playwright MCP bridge that runs upstream browser tools with the CloakBrowser Chromium binary.
Valid MCP server (4 strong, 4 medium validity signals). 5 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.
9 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: PLAYWRIGHT_MCP_BROWSER_ENGINE
Environment variable: PLAYWRIGHT_MCP_HEADLESS
Environment variable: PLAYWRIGHT_MCP_OUTPUT_DIR
Environment variable: PLAYWRIGHT_MCP_OUTPUT_MODE
Environment variable: CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK
Environment variable: CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_HOST
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_PORT
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_ENDPOINT
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_AUTH_TOKEN
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_BACKEND
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_IDLE_TTL_MS
Environment variable: CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_MAX
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-swimmwatch-cloakbrowser-mcp": {
"env": {
"PLAYWRIGHT_MCP_HEADLESS": "your-playwright-mcp-headless-here",
"PLAYWRIGHT_MCP_OUTPUT_DIR": "your-playwright-mcp-output-dir-here",
"PLAYWRIGHT_MCP_OUTPUT_MODE": "your-playwright-mcp-output-mode-here",
"PLAYWRIGHT_MCP_BROWSER_ENGINE": "your-playwright-mcp-browser-engine-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_HOST": "your-cloak-playwright-mcp-http-host-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_PORT": "your-cloak-playwright-mcp-http-port-here",
"CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS": "your-cloak-playwright-mcp-extra-args-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_ENDPOINT": "your-cloak-playwright-mcp-http-endpoint-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_AUTH_TOKEN": "your-cloak-playwright-mcp-http-auth-token-here",
"CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK": "your-cloak-playwright-mcp-console-fallback-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_MAX": "your-cloak-playwright-mcp-http-session-max-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_BACKEND": "your-cloak-playwright-mcp-http-session-backend-here",
"CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_IDLE_TTL_MS": "your-cloak-playwright-mcp-http-session-idle-ttl-ms-here"
},
"args": [
"-y",
"cloakbrowser-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
cloakbrowser-mcp is a Model Context Protocol browser automation server that runs upstream @playwright/mcp with the CloakBrowser Chromium binary. It provides Playwright MCP-compatible tools through a thin CloakBrowser bridge for npm and Docker users over stdio or Streamable HTTP.
Documentation: swimmwatch.github.io/cloakbrowser-mcp
The server is intentionally thin:
launchOptions.executablePath to CloakBrowser;cloakbrowser_binary_info and cloakbrowser_bridge_info.| cloakbrowser-mcp | @playwright/mcp | Playwright MCP Docker base | CloakBrowser | Node.js | Transport | Platform | Parity |
|---|---|---|---|---|---|---|---|
1.2.3 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio, Streamable HTTP | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.2.2 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio, Streamable HTTP | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.2.1 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio, Streamable HTTP | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.2.0 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio, Streamable HTTP | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.1.0 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio, Streamable HTTP | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.0.2 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.0.1 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
1.0.0 | ^0.0.75 | mcr.microsoft.com/playwright/mcp:v0.0.75 | ^0.3.30 | >=20 | stdio | linux/amd64 Docker, Node.js local | Upstream default tools compared in CI. |
See Version Compatibility for the maintained compatibility table.
npx -y cloakbrowser-mcp@latest --help
npx -y cloakbrowser-mcp@latest
npx -y cloakbrowser-mcp@latest --transport streamable-http --http-port 3000
Requires Node.js 20 or newer. The first real browser action may download the CloakBrowser binary unless it is already cached.
The default transport is stdio. Streamable HTTP binds to 127.0.0.1 by default and serves MCP at /mcp.
For the complete generated CLI flag reference, see the published CLI Reference.
docker pull ghcr.io/swimmwatch/cloakbrowser-mcp:latest
docker run --rm --init -i \
-v "$PWD/artifacts:/data" \
ghcr.io/swimmwatch/cloakbrowser-mcp:latest
docker run --rm --init -p 127.0.0.1:3000:3000 \
-v "$PWD/artifacts:/data" \
ghcr.io/swimmwatch/cloakbrowser-mcp:latest \
--transport streamable-http --http-host 0.0.0.0 --http-port 3000
The Docker image is based on the pinned official Playwright MCP image, installs the bridge under /opt/cloakbrowser-mcp, and writes artifacts to /data by default.
{
"mcpServers": {
"cloakbrowser": {
"command": "npx",
"args": ["-y", "cloakbrowser-mcp@latest"],
"env": {
"PLAYWRIGHT_MCP_OUTPUT_DIR": "/tmp/cloakbrowser-artifacts",
"PLAYWRIGHT_MCP_HEADLESS": "true"
}
}
}
}
{
"mcpServers": {
"cloakbrowser": {
"command": "docker",
"args": [
"run",
"--rm",
"--init",
"-i",
"-v",
"/tmp/cloakbrowser-artifacts:/data",
"ghcr.io/swimmwatch/cloakbrowser-mcp:latest"
]
}
}
}
Use upstream PLAYWRIGHT_MCP_* variables for browser, artifact, timeout, network, and tool capability settings. Cloak-specific bridge toggles use CLOAK_PLAYWRIGHT_MCP_*.
CLI flags are documented in the generated CLI Reference.
Common variables:
| Variable | Default | Description |
|---|---|---|
CLOAK_PLAYWRIGHT_MCP_TRANSPORT | stdio | MCP transport exposed by the bridge: stdio or streamable-http. |
CLOAK_PLAYWRIGHT_MCP_HTTP_HOST | 127.0.0.1 | Streamable HTTP bind host. |
CLOAK_PLAYWRIGHT_MCP_HTTP_PORT | 3000 | Streamable HTTP bind port. |
CLOAK_PLAYWRIGHT_MCP_HTTP_ENDPOINT | /mcp | Streamable HTTP endpoint path. |
CLOAK_PLAYWRIGHT_MCP_HTTP_AUTH_TOKEN | unset | Optional Bearer token for Streamable HTTP. |
CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_BACKEND | memory | Session metadata backend. Only memory is implemented in this release. |
CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_IDLE_TTL_MS | 3600000 | Idle TTL for Streamable HTTP sessions. |
CLOAK_PLAYWRIGHT_MCP_HTTP_SESSION_MAX | 32 | Maximum active Streamable HTTP sessions in one process. |
PLAYWRIGHT_MCP_BROWSER_ENGINE | cloak | cloak uses CloakBrowser. playwright uses the upstream Playwright MCP browser runtime. |
PLAYWRIGHT_MCP_HEADLESS | true | Runs Chromium headless. |
PLAYWRIGHT_MCP_OUTPUT_DIR | .playwright-mcp | Artifact directory for npm usage. Docker defaults to /data. |
PLAYWRIGHT_MCP_OUTPUT_MODE | stdout | Upstream output mode, either stdout or file. |
CLOAK_PLAYWRIGHT_MCP_CONSOLE_FALLBACK | true | Enables the compatibility patch for console messages. |
CLOAK_PLAYWRIGHT_MCP_STEALTH_ARGS | true | Adds CloakBrowser default stealth launch arguments. |
CLOAK_PLAYWRIGHT_MCP_EXTRA_ARGS | unset | Comma-separated or JSON array of extra Chromium launch arguments. |
The old CLOAKBROWSER_MCP_* variables are not supported.
The upstream Playwright MCP tool list is authoritative. This project does not reimplement or re-document upstream browser schemas in source code.
Local tools:
cloakbrowser_binary_info returns CloakBrowser package, platform, cache, and resolved binary data.cloakbrowser_bridge_info returns bridge metadata, upstream package/version, and local tool names.npm install
npm run build
npm test
npm run docker:build
npm run docker:smoke
npm run server:validate
npm run bridge:compare -- cloakbrowser-mcp:dev --report bridge-parity-report.json
Documentation starts at docs/getting-started.md. Contributor material is grouped under docs/contributor-guide.md.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.