A11y Expert MCP
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_patternA | Get the accessible implementation pattern for a UI component. |
| review_codeA | Review code for accessibility issues and suggest fixes. |
| list_patternsA | List all available accessible component patterns. |
| check_contrastA | Check if two colors meet WCAG contrast ratio requirements. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit-component | Step-by-step accessibility audit for a UI component. Provide the code and optionally the component type. |
| make-accessible | Transform inaccessible code into a fully accessible implementation. Provide the code and what the component is. |
| check-form-accessibility | Audit a form for accessibility — labels, errors, validation, and keyboard flow. |
| wcag-checklist | Generate a WCAG 2.2 compliance checklist for a page or component. Specify the conformance level. |
| aria-guide | Get a complete ARIA implementation guide for a specific component type. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pattern-index | Index of all WAI-ARIA component patterns in the knowledge base. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: color contrast checking, retrieving patterns, listing patterns, and reviewing code. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (check_contrast, get_pattern, list_patterns, review_code), making the API predictable.
With 4 tools, the server is well-scoped for its niche. It covers the core needs of an accessibility expert without being too sparse or bloated.
The server covers contrast checking, pattern reference, and code review. It lacks a dedicated tool for keyboard navigation testing or automated audit, but review_code can handle many issues.