FAQ¶

What is CloakBrowser MCP?¶

CloakBrowser MCP is a Model Context Protocol server for browser automation over stdio or Streamable HTTP. It runs upstream @playwright/mcp and points the Playwright MCP browser launch configuration at the CloakBrowser Chromium binary.

How is it different from upstream Playwright MCP?¶

The upstream Playwright MCP server owns the browser tool schemas, descriptions, and responses. CloakBrowser MCP keeps those tools unchanged and adds only two local introspection tools: cloakbrowser_binary_info and cloakbrowser_bridge_info.

Should I install it from npm or Docker?¶

Use npm when your MCP client already runs on your machine and Node.js 20 or newer is available. Use Docker when you want a repeatable Playwright MCP-based image with the CloakBrowser cache prepared inside the container.

Which MCP clients can use it?¶

Any MCP client that supports stdio or Streamable HTTP servers can use CloakBrowser MCP. The Getting Started guide includes stdio JSON examples for Codex, Claude Desktop, Claude Code, Cursor, VS Code/Cline-style clients, Continue, Windsurf, Goose, and Warp-style configurations.

Does it support the same browser tools as Playwright MCP?¶

Yes. Upstream Playwright MCP browser tools are forwarded unchanged. The project also runs a parity comparison in CI so changes to the bridge can be checked against the official Playwright MCP behavior.

Does Docker improve security?¶

Docker gives you a more repeatable and isolated runtime, but it does not make browser automation risk-free. Treat automated browsing as untrusted execution: avoid sharing secrets with unknown pages, keep artifacts and screenshots in controlled directories, and review the Security guide before exposing the server to other systems.

Does this project use analytics or tracking?¶

No. The documentation site does not enable analytics by default. Search-engine discovery is handled through standard metadata, robots.txt, sitemap generation, optional webmaster verification tags, and optional IndexNow notifications.