Accessibility Testing MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WCAG_LEVEL | No | WCAG version & level (e.g., 2.0_A, 2.0_AA, 2.1_A, 2.1_AA, 2.1_AAA, 2.2_A, 2.2_AA, 2.2_AAA) | 2.1_AA |
| A11Y_ENGINE | No | Testing engine (axe or ace) | axe |
| SCREEN_SIZES | No | Comma-separated viewport sizes to test (WIDTHxHEIGHT format, e.g., 1280x1024,320x640) | 1280x1024 |
| BEST_PRACTICES | No | Include best practices/recommendations | true |
| HEADLESS_BROWSER | No | Run browser in headless mode; set to false to open visible browser | true |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_urlB | Run accessibility tests on a URL and return detailed violation reports. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_url_jsonA | Run accessibility tests on a URL and return violations in raw JSON format. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_htmlB | Run accessibility tests on raw HTML content. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_html_jsonA | Run accessibility tests on raw HTML content and return violations in raw JSON format. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| get_rulesA | Get information about available accessibility rules for the specified engine. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| accessibility_review | Get guidance on performing an accessibility review |
| fix_suggestion | Get suggestions for fixing a specific accessibility issue |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| WCAG Guidelines Reference | Information about WCAG accessibility guidelines and levels |
| Common Accessibility Issues | Most common accessibility issues found in web applications |
| Engine Comparison | Comparison of Axe-core and IBM Equal Access engines |
TDQS
Scored across 5 tools
The tools are clearly separated by input type (URL vs HTML) and output format (detailed report vs raw JSON). The _json suffix disambiguates the output format, but analyze_url and analyze_url_json are conceptually similar, which could cause minor selection confusion.
All tool names follow a consistent verb_noun pattern with snake_case. The analyze_* prefix is used for testing actions, and get_rules follows the same convention, making the naming predictable and uniform.
With 5 tools, the set is well-scoped for the server's purpose of accessibility testing. Each tool serves a distinct input/output combination without unnecessary bloat, and the count is within the ideal range.
The server covers the core workflows of accessibility testing: analyzing URLs and HTML, with both human-readable and JSON output, plus rule discovery. Minor gaps exist, such as lack of customizable WCAG versions or screen sizes, but the essential surface is complete.