Mcp Accessibility Scanner
Run automated WCAG-oriented accessibility scans on URLs from the agent using Playwright and Axe-core over MCP.
Overview
MCP Accessibility Scanner is a ship-phase MCP server that automates web accessibility checks with Playwright and Axe-core from your agent.
What is this MCP server?
- Playwright plus Axe-core automated accessibility scans
- npm package mcp-accessibility-scanner 1.1.1 with stdio transport
- MCP tools to scan pages agents specify without manual Lighthouse tab hopping
- npm package mcp-accessibility-scanner version 1.1.1
- Transport: stdio; registryType npm
- Stack: Playwright and Axe-core per server description
What problem does it solve?
You are about to ship a web UI but lack a fast, repeatable way to surface WCAG issues from inside the agent workflow.
Who is it for?
Indie SaaS and content sites that want agent-driven a11y regression on staging or production URLs.
Skip if: Native mobile-only apps with no web surface, or teams that forbid Playwright browsers in their environment.
What do I get? / Deliverables
After install, agents trigger scans and get structured Axe violations you can turn into fix tickets before release.
- Stdio MCP server wired in agent config
- Axe-core violation reports for scanned URLs
- Repeatable pre-launch accessibility checks on demand
Recommended MCP Servers
Journey fit
How it compares
Browser a11y scan MCP, not a copywriting skill or production error monitoring integration.
Common Questions / FAQ
Who is MCP Accessibility Scanner for?
Solo builders and small frontend teams using MCP agents who need Playwright-and-Axe scans without leaving the coding session.
When should I use MCP Accessibility Scanner?
During ship-phase testing when you want automated accessibility findings on specific URLs before launch or after UI changes.
How do I add MCP Accessibility Scanner to my agent?
Add io.github.JustasMonkev/mcp-accessibility-scanner, install the npm package mcp-accessibility-scanner, and configure stdio MCP in Claude Code or Cursor.