Developer documentation · Model Context Protocol
Give your AI agent the ability to run automated ADA/WCAG accessibility scans, explain violations, generate code-level fixes, and look up aggregate lawsuit statistics — all through the open Model Context Protocol.
Automated scanning catches common violations; full WCAG conformance requires human testing.
You ask your agent
“Why is the text on my page hard to read?”
The agent calls
explain_violation with rule_id: "color-contrast"
{
"rule": "color-contrast",
"title": "Text must have sufficient color contrast",
"wcag_criterion": "1.4.3 Contrast (Minimum)",
"level": "AA",
"severity": "serious",
"plain_english": "Text and its background are too close in color (below a 4.5:1 ratio for normal text), making it hard to read.",
"who_it_affects": "Low-vision users, color-blind users, and anyone in bright light."
}This is a remote MCP server over Streamable HTTP. Point any MCP-compatible client (Claude Desktop, ChatGPT, Cursor, etc.) at:
https://adawcag.org/api/mcp/mcp The URL really ends in /mcp/mcp. This is not a typo.
/api/mcp/[transport] is a dynamic route. The first mcp names the server, and the second is the transport segment, set to mcp. If you delete one, your client will fail to connect. Copy the URL exactly as shown.
Add the server with OAuth, then run /mcp inside Claude Code to sign in:
claude mcp add --transport http adawcag https://adawcag.org/api/mcp/mcpOr pass an API key as a header:
claude mcp add --transport http adawcag https://adawcag.org/api/mcp/mcp \
--header "Authorization: Bearer YOUR_ADAWCAG_API_KEY"https://adawcag.org/api/mcp/mcp. Keep both mcp segments.Add the server to Cursor’s MCP configuration file (.cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects) using the standard mcpServers shape. Copy it from the Generic JSON quick start. The headers block is for API-key authentication.
Authenticated tools read your key from an Authorization: Bearer <your-api-key> header. Any client that accepts the standard mcpServers shape can use this:
{
"mcpServers": {
"adawcag": {
"url": "https://adawcag.org/api/mcp/mcp",
"headers": {
"Authorization": "Bearer YOUR_ADAWCAG_API_KEY"
}
}
}
}Instead of pasting an API key, OAuth-capable clients (Claude, ChatGPT, MCP Inspector) can connect with no key at all. Add the server URL above and the client will discover our authorization server automatically, open a browser for you to sign in to your ADAWCAG account and approve access, then connect using a token bound to your account. It implements the standard MCP OAuth flow — Dynamic Client Registration, Authorization Code with PKCE (S256), and refreshable tokens. Discovery metadata is published at /.well-known/oauth-protected-resource. API keys and OAuth grant identical access, so use whichever your client supports.
Six tools. Each shows its access tier, what it does, and the parameters it accepts.
scan_urlAccess: API key (free or paid)
Scan a public page for ADA/WCAG violations. Returns rule id, WCAG criterion, severity, and element selectors. Free plan: up to 3 pages, top 10 violations, 5 scans/day.
get_scan_historyAccess: API key
List the most recent scans run with your API key (domain + timestamp).
explain_violationAccess: Free, no key
Plain-English explanation of any axe-core rule: what it means, the WCAG criterion, who it affects, and why it matters.
generate_fixAccess: API key (free or paid)
Code-level remediation guidance with a before/after snippet and step-by-step instructions.
check_compliance_statusAccess: Paid plan
Automated conformance score for a URL: scan-based readiness indicator, severity breakdown, and recommendation. Not a legal compliance determination.
get_lawsuit_dataAccess: Free, no key
Aggregate, anonymized ADA/WCAG lawsuit statistics by state, industry, and time period. Aggregate, anonymized counts only — never defendant names or contact details. Informational only, not legal advice.
| Tool | No key | Free account | Paid plan |
|---|---|---|---|
explain_violation | Yes | Yes | Yes |
get_lawsuit_data | Yes | Yes | Yes |
scan_url | No | Limited: ≤3 pages, top 10 violations, 5 scans/day | Yes: full multi-page scans |
generate_fix | No | Yes | Yes |
get_scan_history | No | Yes | Yes |
check_compliance_status | No | No | Yes |
Connect instantly with OAuth — just add the server URL and sign in to your ADAWCAG account when prompted, no key needed. Prefer an API key? Create a free account and generate one in your dashboard, then pick a plan on the pricing page.
Questions or issues connecting? contact@adawcag.org