Axe MCP Server
Run official Axe DevTools accessibility checks on web UIs from your agent during ship-phase QA.
Overview
axe MCP Server is a MCP server for the ship phase that connects agents to official Axe DevTools for Web accessibility testing via a stdio Docker package.
What is this MCP server?
- Official Deque axe MCP Server for Axe DevTools for Web
- Ships as OCI image docker.io/dequesystems/axe-mcp-server:v1.0.2 with stdio transport
- Brings axe-powered accessibility results into agent-driven fix loops
- Pairs with frontend ship workflows before launch compliance deadlines
- Registry version 1.0.2 aligned with published Docker identifier
- Official Deque Labs axe MCP Server
- OCI package: docker.io/dequesystems/axe-mcp-server:v1.0.2
Community signal: 6 GitHub stars.
What problem does it solve?
Agents can write UI fast but lack trusted, repeatable accessibility scans, so a11y debt ships unnoticed until late manual audits.
Who is it for?
Indie devs and small teams shipping web apps who want Deque-backed automated a11y checks inside Claude Code or Cursor.
Skip if: Mobile-native apps without a web surface, teams that need penetration testing, or orgs that cannot run Docker-based MCP transports.
What do I get? / Deliverables
Your agent runs axe-backed checks, returns structured violation data, and supports tighter fix-and-retest cycles before you launch.
- Axe accessibility scan results usable in agent fix plans
- Repeatable pre-release a11y regression signal
- Violation summaries suitable for ship checklists or PR notes
Recommended MCP Servers
Journey fit
Accessibility verification is part of pre-release quality gates, which Skillselion places under ship—not idea or launch SEO work. Automated a11y scanning is testing discipline; code review may consume results but the MCP’s job is executable audit runs.
How it compares
Official accessibility testing MCP integration, not a generic linter skill or SEO launch tool.
Common Questions / FAQ
Who is Axe MCP Server for?
Frontend-focused solo builders and small teams using MCP-enabled coding agents who already rely on or want Axe DevTools for Web in their QA stack.
When should I use Axe MCP Server?
Use it in ship during testing and review sprints—after features exist in a testable URL or build and before you treat the release as launch-ready.
How do I add Axe MCP Server to my agent?
Configure your MCP client to launch the OCI package dequesystems/axe-mcp-server:v1.0.2 with stdio transport (typically via Docker) per Deque’s registry entry and GitHub repo instructions.