Docs > 🔌 MCP Server
Bring accessibility testing and AI-powered fixes straight into your editor. The WebAbility MCP server plugs into AI coding agents — Cursor, Claude Code, GitHub Copilot, Windsurf and VS Code — so you find and fix WCAG / ADA / Section 508 issues while you build, without leaving your workflow.
verify_fix re-checks that your fix actually resolved the issue.generate_report_pdf turns findings into a branded report you can attach to any ticket or email.start_audit produces a timestamped report and Excel workbook.Two ways in. Use the CLI if you want the account tools (visual_audit, start_audit) — it signs you in and registers the server for you. Use the local server if you only want the free tools and no account.
npm install -g @webability/cli
abilyo loginabilyo login opens your browser, signs you in, and registers the hosted server in Claude Code and Cursor automatically — no JSON to edit. For any other MCP client (VS Code, Windsurf), run abilyo mcp print to get the config block below with your token already filled in:
{
"mcpServers": {
"webability": {
"url": "https://mcp.webability.io/mcp",
"headers": { "x-webability-token": "YOUR_TOKEN" }
}
}
}npm install -g @webability/mcpThen add it to your IDE’s MCP config:
{
"mcpServers": {
"webability": { "command": "webability-mcp" }
}
}This runs on your machine and gives you every free tool below. The account tools return an error until you add a token. Published as @webability/cli and @webability/mcp on npm.
| Tool | What it does | Access |
|---|---|---|
scan_page | Scan any URL for WCAG issues — axe-core + WebAbility detectors + HTML_CodeSniffer. | Free · local |
scan_html | Scan a raw HTML snippet without serving it. | Free · local |
flow_scan | Scan a multi-page journey (login → checkout) in one report. | Free · local |
detect_framework | Detect the page's stack (Tailwind, MUI, Bootstrap, WordPress, Next.js). | Free · local |
generate_ai_fix | Framework-aware fix suggestions you apply in your own code. The finding is sent to api.webability.io for the AI model; no account needed. | Sends to API |
verify_fix | Re-scan a fixed element and confirm the violation is gone. | Free · local |
check_color_contrast | WCAG contrast check with brand-aware suggestions. | Free · local |
check_aria | Validate ARIA attributes in an HTML snippet. | Free · local |
get_rules | List axe-core rules with an optional WCAG tag filter. | Free · local |
find_source | Map a selector from a scan issue back to the source files that render it. | Free · local |
scan_history | Browse your past scans — full results stay on your machine. | Free · local |
generate_report_pdf | Turn scan findings into a branded accessibility-report PDF saved next to your project. The findings are sent to api.webability.io to render the PDF; free, no account. | Sends to API |
visual_audit | Vision pass for focus visibility, icon contrast, and looks-like-a-button issues DOM scanners miss. | Account |
start_audit / get_audit | Generate a full audit deliverable — report + Excel workbook with download links. | Account |
The tools chain into one workflow inside your editor, which is what sets WebAbility apart from find-only accessibility tools:
scan_page → generate_ai_fix → (apply the fix) → verify_fix → generate_report_pdf / start_auditscan_page finds the issues,generate_ai_fix gives you code for your framework,verify_fix confirms the fix landed,generate_report_pdf turns the findings into a branded PDF, andstart_audit produces the report you can hand to a compliance officer.
The DOM-based scan and fix tools are free and run locally with no account; generate_ai_fix and generate_report_pdf are free too but send the findings to api.webability.io for processing. The vision audit (visual_audit) and the full audit deliverable (start_audit / get_audit) run server-side and need a WebAbility account — authenticate with abilyo login or set a WEBABILITY_API_KEY in your MCP server config.