BRYG vs Cloakbrowser MCP
A side-by-side look at the BRYG and Cloakbrowser MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BRYG for browser automation work as a local process; choose Cloakbrowser MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BRYG when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
browser_tabs, browser_new_tab, browser_close_tab.
Choose Cloakbrowser MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_close, browser_resize, browser_console_messages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 60/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 168 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 43 | 26 |
| Full listing | View BRYG | View Cloakbrowser MCP |
Tools & capabilities
BRYG tools 43
browser_tabsList tabs across all browsers (chrome / edge) with ids, grouped by browser and window.browser_new_tabOpen a new tab (optionally at url); it becomes the current tab. browser: chrome / edge (default: the current browser; launched automatically if not running). window: "current" (default: the window of the current tab), "new" (a new window), or a window id from browser_tabs. isolated=true opens a new window with its own cookies / login state, so different accounts can be signed in at once (gone when the browser closes). Afterwards any tool given that page id is routed to its browser automatically.browser_close_tabClose the given tab.browser_activate_tabBring the given tab to the foreground.browser_navigateNavigate to a URL.browser_reloadReload the page.browser_go_backGo back in history.browser_go_forwardGo forward in history.browser_page_infoReturn url/title/viewport/scroll.browser_snapshotAccessibility-tree snapshot; interactive elements are tagged [ref=N]. On large pages use interactive_only=true (interactive elements only) or query (only lines containing the string) to save tokens; ref numbers stay stable under filtering.browser_click_textClick the element with the given visible text (text-based targeting is more reliable than coordinates; great for cookie banners, popups and buttons, e.g. 'OK').browser_login_fillFill login credentials without exposing them to the conversation. Pass credsFile (path to a credentials file: JSON / key=value / two lines / one line) or user+pass directly; visible username/password fields are auto-detected (override with *Selector). Fills only, never submits - press the login button with click_text afterwards.- +31 more on the listing page
Cloakbrowser MCP tools 26
browser_closeClose the pagebrowser_resizeResize the browser windowbrowser_console_messagesReturns all console messagesbrowser_handle_dialogHandle a dialogbrowser_evaluateEvaluate JavaScript expression on page or elementbrowser_file_uploadUpload one or multiple filesbrowser_dropDrop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.browser_findSearch the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.browser_fill_formFill multiple form fieldsbrowser_press_keyPress a key on the keyboardbrowser_typeType text into editable elementbrowser_navigateNavigate to a URL- +14 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
BRYG
{
"mcpServers": {
"bryg": {
"command": "npx",
"args": [
"-y",
"bryg-mcp"
]
}
}
}
Cloakbrowser MCP
{
"mcpServers": {
"swimmwatch-cloakbrowser-mcp": {
"command": "npx",
"args": [
"-y",
"cloakbrowser-mcp@latest"
]
}
}
}
Frequently asked questions
BRYG is categorized under Browser Automation and uses a local stdio subprocess. Cloakbrowser MCP belongs to Browser Automation and uses a local stdio subprocess. Pick BRYG for browser automation work and Cloakbrowser MCP for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
BRYG has no declared pricing — check the project's own site. Cloakbrowser MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bryg and swimmwatch-cloakbrowser-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BRYG has a quality signal of 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Cloakbrowser MCP has 69/100 (Great) with 2 views, 0 installs and 168 GitHub stars.
