Accessibility MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WAVE_API_KEY | No | Your WAVE API key for accessibility audits (optional) | |
| WAVE_API_URL | No | The WAVE API URL (optional) | https://wave.webaim.org/api/request |
| LIGHTHOUSE_TIMEOUT | No | Timeout in milliseconds for Lighthouse audits (optional) | 60000 |
| PLAYWRIGHT_BROWSER | No | Browser to use for Playwright (chromium, firefox, or webkit) (optional) | chromium |
| PLAYWRIGHT_TIMEOUT | No | Timeout in milliseconds for Playwright operations (optional) | 30000 |
| LIGHTHOUSE_CHROME_FLAGS | No | Chrome flags for Lighthouse (optional) | --headless --no-sandbox |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| axe_auditB | Run an accessibility audit using axe-core via Playwright. Supports URLs, local file paths, and localhost URLs. |
| lighthouse_auditB | Run an accessibility audit using Lighthouse CLI. Supports URLs, local file paths, and localhost URLs. |
| wave_auditA | Run an accessibility audit using WAVE API (requires WAVE_API_KEY). Supports URLs and localhost URLs. Local files are automatically served via temporary local server. |
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 3 tools
All three tools perform accessibility audits with overlapping purposes, making them highly ambiguous. An agent would struggle to choose between axe_audit, lighthouse_audit, and wave_audit since they all audit accessibility, differ only in the underlying engine (axe-core, Lighthouse, WAVE), and have nearly identical input support (URLs, local files). This overlap creates significant confusion without clear guidance on when to use each.
Tool names follow a perfectly consistent pattern: all use snake_case with the format 'engine_audit' (axe_audit, lighthouse_audit, wave_audit). This predictable naming makes it easy to understand each tool's purpose at a glance, with no deviations or mixed conventions.
With only 3 tools, the count feels thin for an accessibility server, as it lacks broader functionality like reporting, remediation suggestions, or compliance checks. However, it's borderline reasonable for a focused audit toolset, though it could benefit from additional tools to enhance utility beyond just running audits.
The server is severely incomplete for accessibility testing, offering only audit execution without any tools for analysis, reporting, or follow-up actions. There are no tools to generate reports, track issues, suggest fixes, or validate compliance, leaving significant gaps that will hinder agents in performing comprehensive accessibility workflows.