cloakbrowser-mcp-server
Enables human-in-the-loop monitoring of browser automation by providing a VNC view of the Chromium browser driven by MCP, while exposing the MCP server over Streamable HTTP for client integration.
README
cloakbrowser-mcp-server
Headed wrapper around swimmwatch/cloakbrowser-mcp that exposes the Chromium browser over VNC so a human can watch the same session an MCP client is driving over Streamable HTTP.
The whole project is one Python launcher + one Dockerfile. It starts Xvfb + openbox so Chromium runs headed (required by anti-bot probes that inspect window/widget state), mirrors the display with x11vnc, then execs the upstream cloakbrowser-mcp CLI in Streamable HTTP mode.
Quick start
docker build -t cloakbrowser-mcp-server .
docker run --rm \
-p 3000:3000 \
-p 5900:5900 \
-e VNC_PASSWORD=changeme \
-e DISPLAY_WIDTH=1024 \
-e DISPLAY_HEIGHT=768 \
cloakbrowser-mcp-server
Then:
- MCP client — point it at
http://localhost:3000/mcp(any Streamable HTTP MCP client: Claude Desktop viaclaude mcp add --transport http cloakbrowser http://localhost:3000/mcp, Codex CLI, Cursor, etc.) - VNC viewer — connect to
localhost:5900, passwordchangeme. macOS built-in:open vnc://localhost:5900. Any VNC client works.
Architecture
┌────────────────────────────────────────────┐
│ container │
host ── 3000 ──► │ cloakbrowser-mcp (Streamable HTTP) │
│ └─ Playwright MCP ──► Chromium headed │
host ── 5900 ──► │ Xvfb :99 + openbox ◄── x11vnc mirror │
│ │
│ /data (bind-mounted, persistent profile) │
└────────────────────────────────────────────┘
scripts/launcher.py orchestrates the whole thing in one process:
Xvfb :99at$DISPLAY_WIDTH x $DISPLAY_HEIGHTopenbox(window manager so Chromium honours--start-maximized)x11vncon:5900, password from$VNC_PASSWORDor openexecnode /opt/cloakbrowser-mcp/dist/cli.js --transport streamable-http --http-host 0.0.0.0 --http-port 3000- force
PLAYWRIGHT_MCP_HEADLESS=falsein the child env (the wrapper's whole reason to exist) - wait for SIGTERM/SIGINT, tear down X + VNC
Configuration
Environment variables (wrapper-specific)
| Var | Default | Effect |
|---|---|---|
VNC_PASSWORD |
unset | If set, VNC requires this plaintext password. If unset, VNC is unauthenticated (x11vnc -nopw). |
DISPLAY_WIDTH |
1024 |
Xvfb screen width. Also passed to Playwright as the page viewport (unless the operator sets CLOAK_PLAYWRIGHT_MCP_CONTEXT_OPTIONS). |
DISPLAY_HEIGHT |
768 |
Xvfb screen height. Also passed to Playwright as the page viewport. |
Pass-through
Any PLAYWRIGHT_MCP_* and CLOAK_PLAYWRIGHT_MCP_* variable is forwarded to the upstream cloakbrowser-mcp CLI untouched. See Configuration in the upstream docs for the full list. The wrapper only overrides:
PLAYWRIGHT_MCP_HEADLESS=false(always)--transport streamable-http --http-host 0.0.0.0 --http-port 3000(always)
MCP auth, persistent profiles, Chrome extensions, regional proxies, humanized input — all configured via upstream env vars.
Hardcoded (cannot be changed via env)
| Thing | Value | Reason |
|---|---|---|
| MCP transport | streamable-http |
The wrapper exists to expose the MCP server over HTTP, not stdio. |
| MCP HTTP host | 0.0.0.0 |
Containerised; operator maps ports on docker run. |
| MCP HTTP port | 3000 |
Same. |
| MCP endpoint | /mcp |
Upstream default. |
| Display | :99 |
Xvfb + WM + Chromium all agree. |
| VNC port | 5900 |
Operator maps with -p. |
Volume
Bind-mount /data to persist Chromium's profile across container runs:
docker run --rm \
-p 3000:3000 -p 5900:5900 \
-v ~/cloak-mcp-data:/data \
-e VNC_PASSWORD=changeme \
cloakbrowser-mcp-server
Without the mount, /data lives inside the container and is lost on docker rm.
Port mapping
The internal MCP port is always 3000 and the internal VNC port is always 5900, regardless of what you map them to on the host:
# default: same ports on host and container
-p 3000:3000 -p 5900:5900
# remap both
-p 8080:3000 -p 5999:5900
Project layout
cloakbrowser-mcp-server/
├── Dockerfile # FROM swimmwatch/cloakbrowser-mcp:latest + X stack
├── README.md
├── pyproject.toml # ruff config (lint + format)
├── scripts/
│ └── launcher.py # single-file orchestrator
└── tests/
└── test_launcher.py # stdlib unittest, no test framework dependency
No build system, no CI — keep it boring.
Lint & test
ruff check . # lint
ruff format --check . # format check
ruff format . # format fix
python3 -m unittest discover -s tests -v # 12 unit tests, stdlib only
docker build -t cloakbrowser-mcp-server . # full image build (~30s with cached base)
License
Inherits MIT from cloakbrowser-mcp.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.