Agent Browser MCP vs BRYG
A side-by-side look at the Agent Browser MCP and BRYG MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Agent Browser MCPBrowser Automation · Local subprocess (stdio)MCP server integrating with Vercel's agent-browser for AI-driven browser automation63GoodAuth: no auth requiredVerdict: choose Agent Browser MCP 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?
AChoose Agent Browser 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_navigate, browser_go_back, browser_go_forward.
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 | A Agent Browser MCP | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 63/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 34 | 43 |
| Full listing | View Agent Browser MCP | View BRYG |
Tools & capabilities
Agent Browser MCP tools 34
browser_navigateNavigate to a URL in the browserbrowser_go_backNavigate back in browser historybrowser_go_forwardNavigate forward in browser historybrowser_reloadReload the current pagebrowser_clickClick on an element identified by selector or accessibility propertiesbrowser_fillFill a text input field with the specified valuebrowser_typeType text character by character (useful for triggering key events)browser_hoverHover over an elementbrowser_scrollScroll the page or an elementbrowser_selectSelect an option from a dropdownbrowser_checkCheck a checkbox or radio buttonbrowser_uncheckUncheck a checkbox- +22 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.
Agent Browser MCP
{
"mcpServers": {
"agent-browser-mcp": {
"command": "npx",
"args": [
"agent-browser-mcp"
]
}
}
}
BRYG
{
"mcpServers": {
"bryg": {
"command": "npx",
"args": [
"-y",
"bryg-mcp"
]
}
}
}
Frequently asked questions
Agent Browser MCP is categorized under Browser Automation and uses a local stdio subprocess. BRYG belongs to Browser Automation and uses a local stdio subprocess. Pick Agent Browser MCP 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.
Agent Browser MCP is listed as free. Auth: no auth required. 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 agent-browser-mcp and bryg as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Browser MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 14 GitHub stars. BRYG has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
