Kitsune a11y MCP
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kitsune a11y MCPaudit https://example.com for WCAG 2.2 AA violations"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kitsune a11y MCP
An accessibility audit desk your AI assistant can drive. Point it at a URL, get back every WCAG 2.2 violation grouped by impact, with fix hints.
It runs axe-core in a real headless browser, so it sees the page your users actually get: JavaScript executed, styles applied, dynamic content rendered. Then it adds a second pass of checks that axe cannot do on its own.
The point is to make "is this accessible?" a question an agent can answer with a tool call instead of a guess.
Tools
Tool | What it does |
| WCAG 2.2 audit of a live URL in a real browser. Returns violations sorted by impact (critical first) with the elements at fault and how to fix them. |
| Same audit against a raw HTML string, for output you have not deployed yet. |
| Returns the standard the fixes have to meet: the WCAG 2.2 AA legal floor, plus 14 requirements above it. |
Related MCP server: a11y-mcp-server
Why the extra checks
Automated tools catch about a third of real accessibility problems. axe-core is the best of them and it still cannot tell you that your carousel has no pause button, or that your only way to reach the main content is tabbing through forty nav links.
So on top of axe, this checks for things a screen-reader user would immediately notice and a linter never will:
a skip link near the top of the page
a real
<main>landmarka pause control on anything that moves on its own
labels on inputs that actually associate with them
Everything critical or serious gets fixed before shipping. That is the rule this was built to enforce.
Install
git clone https://github.com/KitsuneTech1/kitsune-a11y-mcp.git
cd kitsune-a11y-mcp && npm install
npx playwright install chromiumRegister it with any MCP client. For Claude Code:
claude mcp add a11y -- node /path/to/kitsune-a11y-mcp/server.mjsThen just ask: "audit https://example.com for accessibility".
Example
> a11y_audit_url https://example.com
2 axe violation rule(s) and 2 Kitsune check failure(s).
Fix every critical/serious before shipping.
MODERATE meta-viewport Zooming and scaling must not be disabled
user-scalable=no on <meta> disables zoom on mobile
MODERATE region All page content should be contained by landmarks
KITSUNE no <main> landmark
KITSUNE no skip link near top of pageNotes
Node 18+. Chromium comes from
playwright-core, so the audit runs against a real rendering engine, not a DOM shim.best_practicesdefaults to true. Set it false for the legal floor only.The audit is read-only. It loads the page, runs the checks, and reports.
License
MIT.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KitsuneTech1/kitsune-a11y-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server