Browser Controller vs MCP Accessibility Scanner
A side-by-side look at the Browser Controller 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.
B
Browser ControllerBrowser Automation · Local subprocess (stdio)MCP server + Chrome extension that gives AI agents control of your real browser with existing sessions and logins59GoodAuth: no auth requiredVerdict: choose Browser Controller 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?
BChoose Browser Controller 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_tabs, browser_snapshot.
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 | B Browser Controller | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 61/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 | 7 | 57 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 42 |
| Full listing | View Browser Controller | View MCP Accessibility Scanner |
Tools & capabilities
Browser Controller tools 17
browser_navigate- `url` (required): an address (scheme optional: `https://` is added; `http://` for `localhost`, `127.0.0.1` and `[::1]`), or `back`, `forward`, `reload`.browser_tabs- `action`: `list` (default), `close` or `focus`. `close` and `focus` need `tabId`.browser_snapshot- `tabId` (required).browser_text- `tabId` (required); `target` (the element); `maxChars` (20000; 100–100000).browser_screenshot- `tabId` (required); `target` (crop to the element's box); `region` (`{x, y, width, height}` in CSS px, crop to a rectangle).browser_inspect_element- `tabId`, `target` (required).browser_click- `tabId`, `target` (required; a point `x,y` is allowed).browser_type- `tabId` (required); `target`; `text`; `key`; `clear` (false); `submit` (false). Give at least one of `text`, `key`, `clear` or `submit`.browser_fill- `tabId` (required); `fields` (1–50 entries of `{target, value}`; `value` is a string, a number, a boolean or an array of strings).browser_scroll- `tabId` (required); `target`; `dy` and `dx` (pixels).browser_wait- `tabId` (required); exactly one of `target`, `url` or `ms`; `gone` (false; with `target`); `timeout` (10000; 1–50000).browser_evaluate- `tabId`, `expression` (required); `timeout` (5000; 1000–30000).- +5 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.
Browser Controller
{
"mcpServers": {
"browser-controller": {
"command": "npx",
"args": [
"-y",
"browser-controller"
]
}
}
}
MCP Accessibility Scanner
{
"mcpServers": {
"mcp-accessibility-scanner": {
"command": "npx",
"args": [
"-y",
"--allow-scripts=re2",
"mcp-accessibility-scanner"
]
}
}
}
Frequently asked questions
Browser Controller 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 Browser Controller 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.
Browser Controller is listed as free. Auth: no auth required. 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 browser-controller and mcp-accessibility-scanner as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser Controller has a quality signal of 59/100 (Good) with 0 views, 0 installs and 7 GitHub stars. MCP Accessibility Scanner has 61/100 (Good) with 1 views, 0 installs and 57 GitHub stars.
