Add CloakBrowser MCP submission

[swimmwatch]

Tool Submission

Tool Information

• Tool ID: cloakbrowser-mcp
• Tool Name: CloakBrowser MCP
• Version: 1.3.0
• Author: swimmwatch
• Homepage: https://github.com/swimmwatch/cloakbrowser-mcp

Description

CloakBrowser MCP is a Playwright MCP-compatible browser automation bridge that runs upstream @playwright/mcp with the CloakBrowser Chromium executable. It forwards upstream Playwright MCP browser tools unchanged and adds two local introspection tools for bridge and browser diagnostics.

MCP Functions Exposed

Forwarded upstream Playwright MCP browser tools:

• browser_click - click a page element
• browser_close - close the browser session
• browser_console_messages - read browser console messages
• browser_drag - drag between page elements
• browser_drop - drop a dragged item
• browser_evaluate - evaluate JavaScript in the page context
• browser_file_upload - upload a local file to a page input
• browser_fill_form - fill page form fields
• browser_handle_dialog - handle browser dialogs
• browser_hover - hover over a page element
• browser_navigate - navigate the browser to a URL
• browser_navigate_back - navigate back in browser history
• browser_network_request - inspect a browser network request
• browser_network_requests - list browser network requests
• browser_press_key - press a keyboard key
• browser_resize - resize the browser viewport
• browser_run_code_unsafe - run Playwright code through the forwarded browser tool
• browser_select_option - select a page option
• browser_snapshot - capture the page accessibility snapshot
• browser_tabs - list and manage browser tabs
• browser_take_screenshot - capture a page screenshot
• browser_type - type text into a page element
• browser_wait_for - wait for page state

Local CloakBrowser MCP introspection tools:

• cloakbrowser_binary_info - return CloakBrowser package, cache, platform, and resolved browser binary information
• cloakbrowser_bridge_info - return runtime metadata for the bridge over upstream Playwright MCP

Permissions Justification

Permission	Value	Reason
filesystem	["read:~/", "write:~/.cache/cloakbrowser", "write:.playwright-mcp", "write:/tmp/cloakbrowser-artifacts"]	Browser automation may read user-selected files for uploads. CloakBrowser may be downloaded/cached locally, and Playwright MCP writes screenshots, PDFs, traces, and other artifacts to the configured output directory.
network	true	Browser navigation and page resource loading require outbound network access to user-requested websites.
env_vars	common PLAYWRIGHT_MCP_* and CLOAK_PLAYWRIGHT_MCP_* configuration variables	These configure transport, output location, headless mode, browser engine, auth token for optional Streamable HTTP, console fallback, and extra Chromium launch arguments.
allow_exec	true	The bridge starts upstream @playwright/mcp and launches the CloakBrowser Chromium child process.
processes	implied by allow_exec = true	Required for MCP bridge, upstream Playwright MCP child process, and browser runtime lifecycle.

Checklist

• toolbox.toml is in submissions/cloakbrowser-mcp/
• Binary entry name matches an actual binary: cloakbrowser-mcp from the npm package
• All permissions are justified above
• Tool description is accurate and does not contain hidden instructions
• I have tested this tool locally with an MCP client path through npx -y cloakbrowser-mcp@latest doctor and project integration tests

Local Validation

python3 - <<'PY'
import tomllib
from pathlib import Path
with Path('submissions/cloakbrowser-mcp/toolbox.toml').open('rb') as f:
    data = tomllib.load(f)
assert data['tool']['name'] == 'cloakbrowser-mcp'
assert data['tool']['version'] == '1.3.0'
assert data['binary']['entry'] == 'cloakbrowser-mcp'
assert len(data['mcp']['tools']) == 25
print('toolbox.toml valid TOML with 25 tools')
PY

bash scripts/review-tool.sh submissions/cloakbrowser-mcp/

Result: manifest structure passed. The local review pipeline fell back to pattern scanning because the toolbox CLI was not installed locally; it reported two expected non-blocking findings for unrestricted network access and child process execution, both justified above for browser automation and bridge process startup.