Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.
Accessibility MCP server exists for a simple reason — assistants are far more useful when they can act on Accessibility directly instead of describing what you should do. Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.
An MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on. The agent calls one tool with a URL; it gets every violation grouped by severity, each with the exact element selector, the offending HTML, the specific failure, the WCAG success criterion, and a fix-guide link — plus the items that still need human review.
Once Accessibility is connected, these are the calls the assistant has available:
Input — The Input tool exposed by this serverscan_accessibility — Returns a report grouped by severity. For each rule: the WCAG criterion, a fix-guide link, and per element the selector, HTML, and exact failureSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need one environment variable: CHROME_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
CHROME_PATH environment variable to a Chromium binary)This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Accessibility's toolset — Input, scan_accessibility — is a fair guide to whether it matches your workflow. It is maintained by Bishop81; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Accessibility's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Input | The Input tool exposed by this server. |
| scan_accessibility | Returns a report grouped by severity. For each rule: the WCAG criterion, a fix-guide link, and per element the selector, HTML, and exact failure. Example flow with an agent: |
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": ["-y", "accessibility-scanner-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
CHROME_PATH environment variable to a Chromium binary)| Variable | Description | Required |
|---|---|---|
| CHROME_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.