Sign inSign up

swimmwatch/cloakbrowser-mcp

By swimmwatch

•Updated 11 days ago

CloakBrowser-backed Playwright MCP browser automation for AI agents

Image
Languages & frameworks
Machine learning & AI
Developer tools
0

2.0K

swimmwatch/cloakbrowser-mcp repository overview

⁠cloakbrowser-mcp

CloakBrowser-backed Playwright MCP browser automation for AI agents.

cloakbrowser-mcp runs upstream Playwright MCP browser tools with the CloakBrowser Chromium binary. The bridge keeps upstream Playwright MCP tools unchanged and adds only local CloakBrowser introspection tools.

⁠Pull

docker pull swimmwatch/cloakbrowser-mcp:latest

⁠Run

docker run --rm --init swimmwatch/cloakbrowser-mcp:latest --help

For stdio MCP usage with persisted artifacts:

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

For a persistent browser profile, keep using /data as the container persistence root:

docker run --rm --init -i \
  -e PLAYWRIGHT_MCP_USER_DATA_DIR=/data/profiles/default \
  -v "$PWD/artifacts:/data" \
  swimmwatch/cloakbrowser-mcp:latest

For Chrome extensions, mount the extension directory separately and pass the container path:

docker run --rm --init -i \
  -e PLAYWRIGHT_MCP_USER_DATA_DIR=/data/profiles/default \
  -e CLOAK_PLAYWRIGHT_MCP_EXTENSION_PATHS=/extensions/my-extension \
  -v "$PWD/artifacts:/data" \
  -v "$PWD/extensions/my-extension:/extensions/my-extension:ro" \
  swimmwatch/cloakbrowser-mcp:latest

⁠MCP client config

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

⁠Alternative registry

The same release tags are also published to GHCR:

docker pull ghcr.io/swimmwatch/cloakbrowser-mcp:latest

⁠Links

Tag summary

Content type

Image

Digest

sha256:c18155daa…

Size

630.9 MB

Last updated

11 days ago

docker pull swimmwatch/cloakbrowser-mcp