axe MCP
Runs Deque's axe engine against a page and returns structured violations with the failing selector and rule.
What it does
Runs Deque's axe engine against a page and returns structured violations with the failing selector and rule. It will not find everything — automated checks catch roughly a third of real accessibility problems — but it catches the cheap ones before a user does. Good default in a CI pipeline, bad as a compliance claim.
Install
npx -y axe-mcp-server
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
{
"mcpServers": {
"axe": {
"command": "npx",
"args": [
"-y",
"axe-mcp-server"
]
}
}
}
Use it for
Catching WCAG violations on a page before a human audit
Skip it if
Certifying accessibility; automated tools catch a minority of real issues
When to use it
Reach for this when the task needs accessibility inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other TypeScript servers
- Filesystem — Gives an agent scoped read, write, and search access to directories you explicitly allow
- Memory — A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
- Sequential Thinking — Gives the model a scratchpad for structured, revisable reasoning: numbered thoughts that can branch, revise, and conclude