MCP Accessibility Bridge
Related Servers
Alternatives to MCP Accessibility Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real browser for navigation, clicking, typing, screenshots, accessibility snapshots, and network/console monitoring. It also supports multi-step JSON test scenarios with assertions, session recording, and visual regression checks.106 npmMIT
- AlicenseAqualityDmaintenanceAttaches to your existing Chrome browser to allow Claude to see the active tab, interact via accessibility tree, and detect handoff triggers like 2FA and captchas.10MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to drive a real browser, so you can navigate, click, type, screenshot, and run multi-step test scenarios with assertions, visual regression, and console/network monitoring straight from the terminal.106 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables Claude Code to control a real browser for navigating, clicking, typing, capturing screenshots, running multi-step E2E tests, assertions, visual regression, and session recording from the terminal.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives Claude Code a real browser so it can navigate, click, type, screenshot, and assert against web pages directly from the terminal. Enables multi-step test scenarios, visual regression checks, session recording, and console/network error monitoring with security controls.106 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser through MCP tools for navigation, clicking, typing, screenshots, accessibility snapshots, and automated test scenarios. It also supports visual regression, session recording, and network/console monitoring to verify web apps directly from the terminal.106 npmMIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: browser connection management, navigation, accessibility tree capture, element property retrieval, focus detection, interactive element listing, and tree querying. The descriptions clearly differentiate their functions, preventing misselection.
All tools follow a consistent verb_noun or verb_adjective_noun pattern using snake_case (e.g., browser_connect, get_accessibility_tree, query_accessibility_tree). The naming is predictable and readable throughout the set.
With 8 tools, the server is well-scoped for its accessibility testing domain. Each tool earns its place by covering essential operations like connection, navigation, tree analysis, and element inspection without being overly sparse or bloated.
The toolset provides complete coverage for accessibility testing workflows: browser setup, navigation, tree capture, element inspection, focus management, interactive element listing, and search capabilities. There are no obvious gaps, enabling agents to perform comprehensive accessibility analysis.