S
sgudimitla/accesslumens-mcp
Free WCAG accessibility checks for AI coding agents, including localhost
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Install command from the repository
claude mcp add accesslumens -- npx -y @accesslumens/mcp
Parsed from the README we fetched on 2026-10-26; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · sgudimitla/accesslumens-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-22 · last seen 2026-11-14 · seen 27× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
claude mcp add accesslumens -- npx -y @accesslumens/mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
claude mcp add accesslumens -- npx -y @accesslumens/mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sgudimitla/accesslumens-mcp;first catalogued 2026-10-22;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# AccessLumens MCP server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Free accessibility checks for your AI coding agent. Ask it to scan the page you are building, and it gets back every WCAG problem with the exact element, the reason it fails and how to fix it. Then it fixes the code and scans again to confirm.
It runs the same scanner as accesslumens.com: axe-core plus AccessLumens' own checks for things axe does not test, such as controls you cannot reach by keyboard, keyboard traps, invisible focus, reflow at 320px, and names a screen reader cannot tell apart (three identical "Add to cart" buttons, alt text that repeats the heading beside it, an aria-label that drops the visible words).
Everything runs on your machine in a headless browser. It works on localhost, staging URLs, public sites and plain .html files. Nothing is sent to AccessLumens and no account or API key is needed.
Watch the 1-minute demo: Claude Code takes a page from 75 to 100, then axe DevTools confirms zero issues. Setup guide and FAQ: accesslumens.com/mcp.
## Setup
Requires Node.js 18.17 or later. AccessLumens scans in a headless Chromium, which it downloads once (about 150 MB). Download it now so your first scan does not wait on it:
sh
npx -y @accesslumens/mcp install
Then add the server to your editor.
Claude Code
sh
claude mcp add accesslumens -- npx -y @accesslumens/mcp
Cursor (.cursor/mcp.json), Windsurf, Claude Desktop and most other clients:
json
"mcpServers": {
"accesslumens": { "command": "npx", "args": ["-y", "@accesslumens/mcp"] }
VS Code (.vscode/mcp.json):
json
"servers": {
"accesslumens": { "type": "stdio", "command": "npx", "args": ["-y", "@accesslumens/mcp"] }
## Use it
Start your dev server, then run one of the ready-made workflows below, or just ask:
> Check http://localhost:3000/checkout for accessibility issues and fix them.
## Workflows (prompts)
Ready-made instructions that tell your agent not just what is wrong but how to fix it well: in the source, native HTML before ARIA, shared causes fixed once, design and behaviour unchanged, and every fix verified by a rescan. In clients that support MCP prompts they appear as slash commands: in Claude Code, type / and pick accesslumens:fix-all. Each takes an optional url; leave it empty and the agent finds your dev server. Some clients, including some VS Code Copilot versions, do not list MCP prompts; there, just ask your agent to fix the accessibility issues on your page. The scanner's results carry the same guidance.
| Prompt | What it does |
| fix-page | Scans one page, fixes every issue in the source, rescans until no Critical or Serious issues remain, and lists what it changed. |
| fix-all | Two passes over every route in your app: fixes everything the scanner finds, then reviews the code for what scanners cannot detect (duplicate button names, focus in dialogs, route-change announcements, form errors, reduced motion). Rescans every route and reports scores before and after. |
| audit | The same review without changing any files: issues grouped by root cause, with the file each one comes from and an ordered fix plan. |
It runs the same scanner as accesslumens.com: axe-core plus AccessLumens' own checks for things axe does not test, such as controls you cannot reach by keyboard, keyboard traps, invisible focus, reflow at 320px, and names a screen reader cannot tell apart (three identical "Add to cart" buttons, alt text that repeats the heading beside it, an aria-label that drops the visible words).
Everything runs on your machine in a headless browser. It works on localhost, staging URLs, public sites and plain .html files. Nothing is sent to AccessLumens and no account or API key is needed.
Watch the 1-minute demo: Claude Code takes a page from 75 to 100, then axe DevTools confirms zero issues. Setup guide and FAQ: accesslumens.com/mcp.
## Setup
Requires Node.js 18.17 or later. AccessLumens scans in a headless Chromium, which it downloads once (about 150 MB). Download it now so your first scan does not wait on it:
sh
npx -y @accesslumens/mcp install
Then add the server to your editor.
Claude Code
sh
claude mcp add accesslumens -- npx -y @accesslumens/mcp
Cursor (.cursor/mcp.json), Windsurf, Claude Desktop and most other clients:
json
"mcpServers": {
"accesslumens": { "command": "npx", "args": ["-y", "@accesslumens/mcp"] }
VS Code (.vscode/mcp.json):
json
"servers": {
"accesslumens": { "type": "stdio", "command": "npx", "args": ["-y", "@accesslumens/mcp"] }
## Use it
Start your dev server, then run one of the ready-made workflows below, or just ask:
> Check http://localhost:3000/checkout for accessibility issues and fix them.
## Workflows (prompts)
Ready-made instructions that tell your agent not just what is wrong but how to fix it well: in the source, native HTML before ARIA, shared causes fixed once, design and behaviour unchanged, and every fix verified by a rescan. In clients that support MCP prompts they appear as slash commands: in Claude Code, type / and pick accesslumens:fix-all. Each takes an optional url; leave it empty and the agent finds your dev server. Some clients, including some VS Code Copilot versions, do not list MCP prompts; there, just ask your agent to fix the accessibility issues on your page. The scanner's results carry the same guidance.
| Prompt | What it does |
| fix-page | Scans one page, fixes every issue in the source, rescans until no Critical or Serious issues remain, and lists what it changed. |
| fix-all | Two passes over every route in your app: fixes everything the scanner finds, then reviews the code for what scanners cannot detect (duplicate button names, focus in dialogs, route-change announcements, form errors, reduced motion). Rescans every route and reports scores before and after. |
| audit | The same review without changing any files: issues grouped by root cause, with the file each one comes from and an ordered fix plan. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sgudimitla-accesslumens-mcp/)
- Source
- github · https://github.com/sgudimitla/accesslumens-mcp
- Browse by field
- Open source
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.