MCP Accessibility Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_connectA | Connect to a running Chrome browser via the Chrome DevTools Protocol (CDP). Chrome must be started with --remote-debugging-port=9222. Command: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug-profile |
| browser_navigateA | Navigate the connected browser to a URL. Returns the page title and HTTP status code when complete. |
| browser_disconnectA | Close the CDP connection to Chrome. Does NOT kill the Chrome process. Call this when you are done to release the connection. |
| get_accessibility_treeA | Capture a snapshot of the current page's accessibility tree. Returns a hierarchical tree of ARIA roles, names, and properties. Use interestingOnly=false for the complete raw tree. Use useFullTree=true for the CDP-level complete tree (slower but more accurate). Use maxDepth to control how deep the tree goes. |
| query_accessibility_treeA | Search the accessibility tree by ARIA role and/or accessible name. Returns matching nodes with their properties. Example: role="button", accessibleName="Submit" finds all Submit buttons. |
| get_element_propertiesA | Given a CSS selector, returns the element's full accessibility properties and multi-framework test selectors (Playwright, Selenium, Cypress, WebdriverIO). Selectors are prioritized: data-testid > stable id > ARIA role > semantic CSS. |
| get_interactive_elementsA | Find all interactive elements on the page (buttons, inputs, links, etc.) and return their accessibility info plus multi-framework test selectors. Covers 20 interactive ARIA roles. Use roles[] to filter to specific roles. |
| get_focused_elementB | Returns the currently keyboard-focused element's accessibility info and suggested selectors. Useful for checking focus management in accessible UIs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.