WCAG Accessibility Audit MCP Server

An MCP server for the Mamba Labs Website Accessibility Checker, WCAG 2.2 AA actor on Apify. Send a domain or a list. Each domain is rendered in a real browser and audited with axe-core, and you get back one row per domain: the WCAG issues automated checks find by severity, the worst failing rules, a score, European Accessibility Act exposure signals, and optional compliance page checks.

What's Inside

• What it does

• Quick start

• Prerequisites

• Example prompts

• Tool

• Inputs

• Pricing

• Your keys

• Full actor documentation

• License

Related MCP server: mcp-accessibility-scanner

What it does

Audit websites for accessibility with axe-core in a real browser. Give one domain or a list; each domain returns one row with the WCAG issues automated checks find (distinct failing rules by impact, affected element count, top failing rules with help links, sample selectors), a 0 to 100 score, European Accessibility Act exposure signals, and optional presence checks for an accessibility statement, an accessibility overlay widget, a privacy policy, a German Impressum, and the US privacy choice link and GPC file. Blocked, timed out, or unreachable sites return a free row that says why. Automated checks find a subset of WCAG failures and the result is never a conformance claim. A run that does not succeed is returned as an error with its run ID. Read-only on the audited sites; requires an APIFY_TOKEN and consumes Apify credits per audited domain.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-wcag-accessibility-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-wcag-accessibility-audit"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The audit_wcag_accessibility tool appears.

Prerequisites

• Node.js 18 or newer.

• An Apify API token from console.apify.com/account/integrations, set as APIFY_TOKEN. The server lists its tool without a token; a call needs one.

Example prompts

• "Audit mambabuilt.com and example.de against WCAG 2.2 AA and list the critical issues."

• "Check these 20 EU shop domains for EAA exposure and whether each links an accessibility statement."

• "Does this German site have an Impressum, and which required fields does it show?"

Tool

audit_wcag_accessibility. One tool. Example arguments:

{
  "domains": ["mambabuilt.com", "example.de"],
  "standard": "wcag22aa",
  "compliance_checks": ["accessibility_statement", "impressum", "overlay"]
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Blocked, timed out, and unreachable domains are never charged.

Your keys

The actor needs no provider key. It reads only the sites you give it and holds no key of its own.

Full actor documentation

apify.com/mambalabs/wcag-accessibility-audit

License

MIT. See LICENSE.