MCP Accessibility Bridge
Related Servers
Alternatives to MCP Accessibility Bridge
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityCmaintenanceEnables AI agents to inspect and control a live Chromium browser for frontend debugging, providing console logs, network requests, DOM snapshots, and accessibility analysis.195 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control and inspect a live Chrome browser for automated web debugging, performance analysis, and Lighthouse audits. It allows agents to capture screenshots, monitor network requests, and measure Core Web Vitals using plain-English prompts.1,026,016 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Claude to see and interact with any macOS application using natural language commands. Perfect for testing Mac applications, UI automation, and app development with AI assistance.33MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to autonomously interact with and test web applications in a real browser, providing DOM/Accessibility tree extraction, runtime telemetry, screenshot capture, and Markdown test reports.22 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to drive a selector-free browser through natural language, so they can debug styling and console errors, map and document web apps, and generate or run end-to-end and exploratory tests without screenshots.596 npm95MIT
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.