axe MCP Server One-click accessibility fixes.

Connect Deque’s trusted accessibility expertise with AI coding agents to confidently build accessible code in your IDE.

An illustration of accessibility remediation advice automatically suggested within the IDE

What is the axe MCP Server?

Built on the Model Context Protocol (MCP), the axe MCP Server connects the accessibility expertise of the axe Platform with AI coding agents directly in a developer’s environment. Developers can apply, edit, or reject remediation suggestions with a single click—staying in flow while accelerating the creation of accessible experiences.

Why use axe MCP Server?

Fix more issues, faster

Accelerate remediation with accurate results and broader coverage. Surface root causes and get suggested code changes that can be applied in one click.

Keep devs focused and in flow

Bring recommended accessibility fixes directly into the IDE so developers can fix issues as they code without jumping between tools.

Scale accessibility knowledge

Empower all developers to build accessible code from the start by integrating testing and guidance into their workflow and grow their accessibility expertise over time.

Enterprise-grade security and data privacy

When it comes to security, the axe MCP Server is built with enterprise-grade protections and gives you full control of your data. Deque acts only as a data processor, never a controller, so your data is never used to train models. The result is trusted, expert-backed accessibility fixes with privacy and transparency at the core.

Get accessibility fixes instantly, right where you code.

Keep developers in flow, scale knowledge, and accelerate the creation of accessible experiences.

Streamline developer workflows

Get guidance and remediation fixes within your development environment to deliver accessible products, while eliminating context switching or long wait times for experts.

Illustration of a presentation screen showing a simple flow diagram, with connected circles representing a development process leading to an accessibility symbol
Illustration of a code editor with highlighted lines of code, surrounded by icons representing different developer tools and integrations.

Get context-specific guidance in your IDE

Work seamlessly in GitHub Copilot, Cursor, Claude Code, Windsurf, VS Code, and any AI coding assistant that supports MCP. The axe MCP Server understands your unique workflow, delivering expert-backed, contextual code fixes.

Act on expertise you can trust

Leveraging the same trusted engine as the axe DevTools Extension, the axe MCP Server (with axe Assistant layered on top) accesses the comprehensive Deque University knowledge base to accurately respond to nuanced, specialized digital accessibility questions—avoiding the misunderstandings common with general tools.

Illustration of a stack of books with a gold medal draped over them

For years, we’ve talked about the promise of ‘shifting left’—finding and fixing accessibility issues earlier in the process. With technologies like this, real change happens.”

Jennison Asuncion Co-Founder of Global Accessibility Awareness Day & the GAAD Foundation

Who can benefit from the axe MCP Server?

Developers

Stay in the flow and resolve accessibility issues faster and with greater confidence—regardless of your accessibility expertise.

Engineering managers

Enable teams with trusted guidance so they can deliver more accessible experiences while building internal expertise.

Central accessibility team leaders

Equip developers with accessibility knowledge to work more independently, freeing accessibility teams to focus on higher-level strategic initiatives.

 

Connecting accessibility everywhere

Built on the Model Context Protocol, the axe MCP Server, enables Deque’s tools and expertise to be integrated into new environments across the SDLC, as well as cater responses to the language of the tools you’re using.

Our first integration brings accessibility expertise into IDEs, and will later extend across the broader tool ecosystem. As more axe Platform functionality is delivered through the MCP Server, additional roles and use cases will be unlocked.

angle brackets and a forward slash on a screen

Frequently asked questions

The axe MCP Server works with major IDEs and AI-powered coding assistants—including GitHub Copilot, Cursor, Claude Code, Windsurf, and VS Code—as well as any agent compatible with MCP. This lets developers integrate accessibility testing directly into the tools they already use.

If you’re already using axe DevTools Linter, you catch accessibility issues early by testing code in your IDE. The axe MCP Server builds on this by introducing additional intelligence and context. It evaluates the rendered state of your application, providing actionable guidance in natural language based on specific prompts—all within the context of your IDE.

The axe MCP Server follows enterprise-grade protections and adheres to your configured axe DevTools settings and Deque’s privacy policy. For generative AI remediation recommendations, no data is ever stored.

Under the hood, the axe MCP Server uses the same trusted engine as the axe DevTools Extension, ensuring rigorous accessibility testing while respecting your organization’s settings and policies.

Layered on top is axe Assistant, Deque’s AI chatbot, which draws from Deque University, the most comprehensive digital accessibility knowledge base in the industry. Axe Assistant interprets user prompts and delivers consistent, expert-backed remediation guidance directly to the AI agent in your IDE.

This combination allows the axe MCP Server to handle nuanced, specialized accessibility issues that more general tools might misinterpret, giving teams more confidence in the guidance they receive.