BRYG vs MCP Accessibility Scanner
A side-by-side look at the BRYG and MCP Accessibility Scanner 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 MCP Accessibility Scanner 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 MCP Accessibility Scanner when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
scan_page, audit_site, scan_page_matrix.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 60/100 · Good | 61/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 | 57 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 43 | 42 |
| Full listing | View BRYG | View MCP Accessibility Scanner |
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
MCP Accessibility Scanner tools 42
scan_pagePerforms a comprehensive accessibility scan on the current page using Axe-core.audit_siteCrawls and scans multiple internal pages, then aggregates violations across the site.scan_page_matrixRuns Axe scans on the same page across viewport/media/zoom variants and compares deltas against baseline.audit_keyboardAudits real keyboard focus behavior by pressing Tab (and optional Shift+Tab) with practical heuristics.audit_screen_readerInspects the browser's accessibility tree (`page.ariaSnapshot`), accessible names and element geometry for potential accessibility issues. No actual screen reader is installed or driven, and its announcements and interactions are not tested.browser_navigateNavigate to a URL.browser_navigate_backGo back to the previous page.browser_navigation_timeoutSet default navigation timeout for existing tabs.browser_default_timeoutSet default operation timeout for existing tabs.browser_snapshotCapture accessibility snapshot of the current page (better than screenshot for analysis).browser_findSearch the current page accessibility snapshot without returning the full snapshot.browser_clickPerform click on a web page element.- +30 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"
]
}
}
}
MCP Accessibility Scanner
{
"mcpServers": {
"mcp-accessibility-scanner": {
"command": "npx",
"args": [
"-y",
"--allow-scripts=re2",
"mcp-accessibility-scanner"
]
}
}
}
Frequently asked questions
BRYG is categorized under Browser Automation and uses a local stdio subprocess. MCP Accessibility Scanner belongs to Browser Automation and uses a local stdio subprocess. Pick BRYG for browser automation work and MCP Accessibility Scanner 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. MCP Accessibility Scanner 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 bryg and mcp-accessibility-scanner 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. MCP Accessibility Scanner has 61/100 (Good) with 1 views, 0 installs and 57 GitHub stars.
