WCAG Accessibility MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | HTTP bind address | 127.0.0.1 |
| PORT | No | HTTP transport port | 3000 |
| A11Y_MCP_HOST | No | HTTP bind address | 127.0.0.1 |
| A11Y_MCP_BODY_LIMIT | No | HTTP JSON body limit | 4mb |
| A11Y_MCP_NO_SANDBOX | No | Disables Chromium sandboxing only when the runtime requires it | false |
| A11Y_MCP_ALLOWED_ROOT | No | Restricts local file audits to a specific folder | |
| A11Y_MCP_BROWSER_PATH | No | Absolute path to Chrome, Chromium, or Edge | |
| A11Y_MCP_ALLOWED_HOSTS | No | Allowed Host headers for HTTP mode | |
| A11Y_MCP_ALLOW_PRIVATE | No | Allows localhost/private-network URL audits in trusted environments | |
| A11Y_MCP_AUDIT_TIMEOUT_MS | No | Timeout for the audit phase | 25000 |
| A11Y_MCP_ENABLE_FILE_AUDIT | No | Enables local file audits over HTTP in trusted deployments | |
| A11Y_MCP_BROWSER_CONCURRENCY | No | Maximum concurrent Chromium audits | 2 |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_urlA | Load a public or local web page in headless Chromium, run axe-core, and return prioritized WCAG findings, DOM evidence, computed styles, and contrast corrections. Read-only. |
| audit_htmlA | Render supplied HTML in an isolated headless browser and return WCAG findings plus evidence and suggested corrections. Use for generated UI before it is hosted. Read-only. |
| audit_fileA | Render a local .html or .htm file beneath the configured allowed root and return accessibility findings and corrections. Read-only. |
| check_contrastA | Calculate the WCAG contrast ratio for foreground and background colors and determine whether the pair passes for the supplied text size and weight. |
| suggest_contrast_fixA | Find the nearest black-or-white-directed foreground or background adjustment that reaches the selected WCAG contrast threshold. Returns a mathematical candidate, not an automatic edit. |
| explain_issueA | Return implementation-focused remediation steps and the axe rule reference for a rule ID found in an audit. |
| get_wcag_checklistA | Return every success criterion required by a WCAG 2.0, 2.1, or 2.2 A/AA/AAA profile, with W3C references, axe rule mappings, and explicit automated-partial versus manual coverage. Use this to plan the checks that a browser audit cannot complete. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| accessibility-fix-loop | A reusable agent workflow for evidence-led accessibility correction. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a clear and distinct task: three different methods for auditing (by URL, HTML string, or file), a contrast checker, a contrast fix suggester, an issue explainer, and a checklist retriever. There is no overlap or ambiguity among them.
Tool names mostly follow a verb_noun pattern (audit_url, audit_html, audit_file, check_contrast, explain_issue, get_wcag_checklist). The only minor deviation is 'suggest_contrast_fix', which is a verb_verb_noun but still clear and consistent in style.
7 tools is an ideal number for this domain. Each tool covers a necessary function without unnecessary redundancy: three audit entry points, two contrast helpers, one explainer, and one checklist reference. The scope is well-scoped and focused on WCAG accessibility.
The tool set provides a complete lifecycle for accessibility auditing: multiple ways to ingest content for auditing, contrast analysis and remediation, issue explanation, and a checklist for manual coverage. There are no obvious gaps for the intended use case of assessing and fixing WCAG compliance.