A11ymcp MCP Server

If you want an AI assistant working directly with A11ymcp, the a11ymcp mcp server is the bridge. An MCP server for accessibility testing using Axe-core.

What A11ymcp does

https://github.com/user-attachments/assets/316c6d44-e677-433e-b4d5-63630b4bab2b

Key capabilities

• Test web pages — Test any public URL for accessibility issues with customizable viewport dimensions
• Test HTML snippets — Test raw HTML strings for accessibility issues
• WCAG compliance testing — Check content against various WCAG standards (2.0, 2.1, 2.2)
• Customizable tests — Specify which accessibility tags/standards to test against
• Rule exploration — Get information about available accessibility rules
• Color contrast analysis — Check color combinations for WCAG compliance
• ARIA validation — Test proper usage of ARIA attributes
• Orientation lock detection — Identify content that forces specific screen orientations

Tools it exposes

Once connected, the assistant can call these 9 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• Cursor — The Cursor tool exposed by this server
• Windsurf — Add to your Windsurf MCP configuration (~/.codeium/windsurf/mcp_config.json):
• test_accessibility — The test_accessibility tool exposed by this server
• test_html_string — The test_html_string tool exposed by this server
• get_rules — Get information about available accessibility rules with optional filtering. Returns an array of rule objects, each containing ruleId, description, help
• check_color_contrast — Check if a foreground and background color combination meets WCAG contrast requirements
• check_aria_attributes — The check_aria_attributes tool exposed by this server
• check_orientation_lock — The check_orientation_lock tool exposed by this server

Installing the a11ymcp mcp server

The server is distributed via npm as a11y-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Requirements

• Node.js 18 or later - An MCP-compatible client (Claude Desktop, Claude Code, VS Code, Cursor, etc.)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. A11ymcp sits in that group, and the shape of its toolset — Prerequisites, Cursor, Windsurf among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 9 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use A11ymcp.
• Maintained by ronantakizawa.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the a11ymcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.