CloakBrowser MCP v1.1.0
Summary
CloakBrowser MCP v1.1.0 adds Streamable HTTP transport alongside the existing default stdio transport, making the bridge usable both as a local spawned MCP server and as an HTTP endpoint for multi-client deployments.
Added
- Optional Streamable HTTP transport at a configurable endpoint, with
POST,GET, andDELETEsupport through the MCP SDK transport. - Per-session bridge/runtime isolation for HTTP clients: each session gets its own outer MCP server, upstream Playwright MCP child process, transport, and isolated browser profile.
- In-memory HTTP session metadata management with idle TTL and maximum session limits.
- Optional Bearer token authentication for Streamable HTTP requests.
- Commander-based CLI parsing with generated help and environment-variable support.
- Generated CLI reference in the MkDocs site.
- Codecov coverage upload and README coverage badge.
Fixed
- Concurrent Streamable HTTP sessions now use isolated upstream Playwright MCP browser profiles, avoiding shared Chromium profile conflicts.
- Generated CLI docs no longer trigger infinite rebuilds during
mkdocs serve. - Streamable HTTP request handling now has hardened Bearer parsing, IPv6 endpoint matching, and internal error responses without stack detail exposure.
Security
- Streamable HTTP still defaults to loopback binding.
- Optional Bearer auth is available for HTTP deployments.
- No deprecated SSE transport or legacy
/sseendpoint is added. - HTTP sessions are isolated across bridge runtime, upstream child process, MCP transport, and browser profile.
- The session store persists metadata only, not browser state or tool responses.
- The development test stack was updated to patched transitive
viteandesbuildversions.
Compatibility
- Node.js:
>=20 @playwright/mcp:^0.0.75- Docker base:
mcr.microsoft.com/playwright/mcp:v0.0.75 - CloakBrowser:
^0.3.30 - Published transports: stdio and Streamable HTTP