Browser MCP Cdp vs BRYG
A side-by-side look at the Browser MCP Cdp and BRYG MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browser MCP Cdp for browser automation work as a local process; choose BRYG 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 Browser MCP Cdp when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
browser_navigate, browser_evaluate, browser_screenshot.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 56/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | 43 |
| Full listing | View Browser MCP Cdp | View BRYG |
Tools & capabilities
Browser MCP Cdp tools 13
browser_navigateNavigate the browser to a URL. Returns the final URL and page title.browser_evaluateExecute JavaScript in the current page context and return the result. Use await_promise=true (default) for async expressions.browser_screenshotCapture a screenshot of the current page. Returns a PNG image.browser_clickClick an element matched by a CSS selector. Returns true if found and clicked.browser_fillSet the value of an input, textarea, or select element matched by a CSS selector.browser_wait_forWait until an element matching the CSS selector appears in the DOM. Returns true if found within the timeout, false otherwise.browser_get_urlGet the current page URL.browser_get_textGet the visible text content of the page or a specific element.browser_get_htmlGet the outer HTML of the page or a specific element.browser_scrollScroll the page by a relative offset in pixels.browser_click_atClick at an absolute (x, y) pixel coordinate on the page using real CDP mouse events. Pierces through iframes and ad overlays that block CSS-selector clicks.browser_tabsList all open browser tabs with their id, url, and title.- +1 more on the listing page
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
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.
Browser MCP Cdp
{
"mcpServers": {
"browser-mcp-cdp": {
"command": "npx",
"args": [
"-y",
"browser-mcp-cdp"
]
}
}
}
BRYG
{
"mcpServers": {
"bryg": {
"command": "npx",
"args": [
"-y",
"bryg-mcp"
]
}
}
}
Frequently asked questions
Browser MCP Cdp is categorized under Browser Automation and uses a local stdio subprocess. BRYG belongs to Browser Automation and uses a local stdio subprocess. Pick Browser MCP Cdp for browser automation work and BRYG 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.
Browser MCP Cdp has no declared pricing — check the project's own site. BRYG has no declared pricing — check the project's own site. 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 browser-mcp-cdp and bryg as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser MCP Cdp has a quality signal of 56/100 (Good) with 5 views, 0 installs and 0 GitHub stars. BRYG has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
