@mhdd_24/accessibility-mcp
OfficialServer 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 |
|---|---|
| a11y_statusB | Show wcag/accessibility inspection configuration / health. |
| a11y_analyzeC | Analyze a page/site for wcag/accessibility inspection. |
| a11y_reportC | Generate a wcag/accessibility inspection report. |
| a11y_checkC | Quick wcag/accessibility inspection check. |
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 4 tools
a11y_analyze and a11y_check overlap in purpose, both performing inspection with only a depth/quick distinction. a11y_report and a11y_status are clearly distinct, but the boundary between analyze and check could confuse an agent.
All tools share the a11y_ prefix and follow the same verb-after-prefix pattern in lowercase snake_case, making the naming highly predictable and consistent.
Four tools is a well-scoped set for a focused accessibility inspection server, covering analysis, reporting, quick checks, and status without redundancy.
The core workflows of inspection, reporting, and configuration health are covered. A tool to list or retrieve specific violations would be a minor enhancement, but no critical gaps exist.