Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Scan any URL for WCAG accessibility issues (axe-core) and get per-element fixes for an AI agent.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CHROME_PATHYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": [
"-y",
"accessibility-scanner-mcp"
],
"env": {
"CHROME_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add accessibility-scanner --env CHROME_PATH=your-value -- npx -y accessibility-scanner-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": [
"-y",
"accessibility-scanner-mcp"
],
"env": {
"CHROME_PATH": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"accessibility-scanner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"accessibility-scanner-mcp"
],
"env": {
"CHROME_PATH": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CHROME_PATH envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Bishop81, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on. The agent calls one tool with a URL; it gets every violation grouped by severity, each with the exact element selector, the offending HTML, the specific failure, the WCAG success criterion, and a fix-guide link — plus the items that still need human review.
It runs the real axe-core engine in your local Chrome (via playwright-core), so nothing about the pages you scan leaves your machine. It scrolls the page first so lazy-loaded content is actually checked rather than silently skipped, and it resolves color contrast over CSS gradients, which most tools leave as "needs review."
Upgrading from 0.1.x? 0.2.0 sees more of each page and returns more findings for the same URL.
See CHANGELOG.md.
Part of accessibilityscanner.app.
CHROME_PATH to point at a specific binary if you'd rather choose. A browser already installed by Playwright is used as a last resort; nothing is ever downloaded for you.Set SCANNER_API_URL and the scan runs on accessibilityscanner.app instead of locally:
{ "env": { "SCANNER_API_URL": "https://accessibilityscanner.app" } }
No account or key needed — it uses the same public endpoints the website's own form uses. Useful in CI, in a container, or anywhere you can't install a browser. Hosted scans also carry suggested fix colours for contrast failures, which the local scanner doesn't compute yet.
⚠️ In this mode the URL you scan is sent to our server. The local path sends nothing anywhere, and stays the default — hosted mode is opt-in via that environment variable only.
Add it to your MCP client's config. No global install needed — npx fetches it on first run.
Claude Desktop (claude_desktop_config.json), Cursor, Claude Code, or any MCP client:
{
"mcpServers": { "accessibility-scanner": { "command": "npx", "args": ["-y", "accessibility-scanner-mcp"] } } }
If Chrome is not auto-detected, add an env block:
{
"mcpServers": { "accessibility-scanner": { "command": "npx", "args": ["-y", "accessibility-scanner-mcp"], "env": { "CHROME_PATH": "/usr/bin/google-chrome" } } } }
scan_accessibility| Input | |
|---|---|
url (string, required) | The http(s) URL to scan. |
Returns a report grouped by severity. For each rule: the WCAG criterion, a fix-guide link, and per element the selector, HTML, and exact failure. Example flow with an agent:
You: Audit https://example.com for accessibility and fix what you can.
Agent: *(calls
scan_accessibility)* → reads the findings → edits the code → re-scans.
Automated testing covers the machine-checkable subset of WCAG (most of the issues on a typical page, but not all of it). Items that need human judgement are returned under "Needs manual review." It never claims a page is "compliant."
MIT