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.Every tool is free. The hosted server needs no API key: point your client at the URL below and the scan and check tools work straight away, under fair-use limits. Sign in with a free WebAbility account to lift the limits and unlock visual_audit, start_audit and get_audit. An AI agent with its own AgentMail inbox can sign up on its own: it chooses Sign in with AgentID on the WebAbility sign-in page (https://app.webability.io/auth/signin) and gets its own free account, with no human account or API key.
Add this to your MCP client config (Cursor, Claude Code, VS Code, Windsurf):
{
"mcpServers": {
"webability": {
"url": "https://mcp.webability.io/mcp"
}
}
}This URL is anonymous by default. Calling visual_audit, start_audit or get_audit without signing in returns sign-in steps as a normal tool result. It does not disconnect your client.
Use https://mcp.webability.io/mcp/auth when you want to sign in. It has the same tools, and it always asks for sign-in (401 and OAuth) until you are signed in.
https://mcp.webability.io/mcp/auth as a custom connector to use visual_audit and full audits. Use https://mcp.webability.io/mcp for the free scan tools only.https://mcp.webability.io/mcp/auth as the url in your MCP config.claude mcp login <server-name> (Claude Code 2.1 or later), or run /mcp inside Claude Code, choose the server and follow the browser sign-in steps.codex mcp login <server-name>.opencode mcp auth <server-name>.<server-name> is the name you gave the server, for example webability.
Run the server on your machine over stdio. Add this to your IDE’s MCP config:
{
"mcpServers": {
"webability": { "command": "webability-mcp" }
}
}To use the account tools locally, install the CLI and sign in once. It opens your browser; no key to copy:
npm install -g @webability/cli
webability loginPublished 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 an HTML snippet or component fragment in-process — milliseconds, no browser, no URL. | Free · local |
flow_scan | Scan a multi-page journey (login → checkout) in one report. | Free · local |
diff_scan | Diff a baseline scan against the current page — fixed, new and remaining issues, so a change is checked for regressions. | 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 and WebAbility rules with WCAG tags and a fixability tier (mechanical, contextual, visual). | Free · local |
find_source | Map a selector back to the source files that render it. On React/Vue dev builds, scan results already carry file, line and component per finding. | 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 / diff_scan → 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.
Every tool is free. The DOM-based scan and fix tools need no account; generate_ai_fix and generate_report_pdf 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 free WebAbility account. Sign in through the sign-in URL above, or run webability login for the local server.