What can you do with this server?

The CloakBrowser MCP server is a browser automation tool that runs Playwright with a CloakBrowser (stealth Chromium) backend, enabling AI agents to control a browser for web interactions. Navigate & Control the Browser * Navigate to URLs, go back, close the browser, resize the window, and manage tabs (list, create, close, select) Interact with Web Elements * Click (left/right/middle, double-click), type text, fill forms, press keyboard keys, hover, drag-and-drop, select dropdown options, upload files, and drop files/data onto elements Inspect & Capture Page State * Take screenshots (browser_take_screenshot), capture accessibility snapshots (browser_snapshot), retrieve console messages (browser_console_messages), and list/inspect network requests (browser_network_requests, browser_network_request) Scripting & Automation * Execute JavaScript on the page (browser_evaluate), run arbitrary Playwright code (browser_run_code_unsafe — use with caution), and wait for text to appear/disappear or a timeout (browser_wait_for) Handle Browser Events * Accept or dismiss dialogs (alerts, confirms, prompts) via browser_handle_dialog Diagnostics & Metadata * Retrieve CloakBrowser binary details (cloakbrowser_binary_info) and bridge runtime metadata including upstream Playwright MCP version and available tools (cloakbrowser_bridge_info)

CloakBrowser MCP

by swimmwatch

Overview Schema Related Servers Score Discussions

TypeScript

Remote

cloakbrowser-mcp

codecov Actionlint CodeQL Dependency Review OpenSSF Scorecard Zizmor Release MCP Registry cloakbrowser-mcp MCP server npm Docker Hub pulls Node.js >=20 Docker License: MIT

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:

upstream Playwright MCP owns browser tool schemas, descriptions, and responses;
this package generates a Playwright MCP config that points launchOptions.executablePath to CloakBrowser;
the bridge exposes upstream tools unchanged;
the only local tools are cloakbrowser_binary_info and cloakbrowser_bridge_info.

Version compatibility

cloakbrowser-mcp	@playwright/mcp	Playwright MCP Docker base	CloakBrowser	Node.js	Transport	Platform	Parity
`1.3.0`	`^0.0.75`	`mcr.microsoft.com/playwright/mcp:v0.0.75`	`^0.3.31`	`>=20`	stdio, Streamable HTTP	`linux/amd64` Docker, Node.js local	Upstream default tools compared in CI.
`1.2.7`	`^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.6`	`^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.5`	`^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.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.

Related MCP server: browser-devtools-mcp

Registry visibility

cloakbrowser-mcp publishes server.json to the official MCP Registry. GitHub's github.com/mcp registry is a separate curated discovery surface, so an official MCP Registry release may not appear there immediately.

Verify the current official registry entry and GitHub MCP visibility probe with:

npm run registry:check

Use npm run registry:check:strict only when GitHub MCP listing visibility should be treated as a required release gate.

Run from npm

npx -y cloakbrowser-mcp@latest --help
npx -y cloakbrowser-mcp@latest doctor
npx -y cloakbrowser-mcp@latest doctor --json
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. Use doctor for local diagnostics before connecting an MCP client. It checks the Node.js engine, project metadata, upstream Playwright MCP resolution, and CloakBrowser binary metadata without starting the bridge or downloading a browser. The default transport is stdio. Streamable HTTP binds to 127.0.0.1 by default, serves MCP at /mcp, and exposes fixed GET /healthz and GET /readyz probes. If --http-auth-token is set, the probes require the same Authorization: Bearer ... header as MCP requests. For the complete generated CLI flag reference, see the published CLI Reference.

Run from Docker

docker pull swimmwatch/cloakbrowser-mcp:latest
docker run --rm --init -i \
  -v "$PWD/artifacts:/data" \
  swimmwatch/cloakbrowser-mcp:latest

docker run --rm --init -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

curl http://127.0.0.1:3000/healthz
curl http://127.0.0.1:3000/readyz

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. The same tags are also published to ghcr.io/swimmwatch/cloakbrowser-mcp.

MCP client configuration

npm

{
  "mcpServers": {
    "cloakbrowser": {
      "command": "npx",
      "args": ["-y", "cloakbrowser-mcp@latest"],
      "env": {
        "PLAYWRIGHT_MCP_OUTPUT_DIR": "/tmp/cloakbrowser-artifacts",
        "PLAYWRIGHT_MCP_HEADLESS": "true"
      }
    }
  }
}

Docker

{
  "mcpServers": {
    "cloakbrowser": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "--init",
        "-i",
        "-v",
        "/tmp/cloakbrowser-artifacts:/data",
        "swimmwatch/cloakbrowser-mcp:latest"
      ]
    }
  }
}

Configuration

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.

Tools

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.

Development

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.

Install Server

license - permissive license

quality

maintenance

How are these scores calculated?

Maintenance

–Maintainers

<1hResponse time

1dRelease cycle

12Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Tools

View all tools

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/swimmwatch/cloakbrowser-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server