EAA Accessibility MCP Server

MCP (Model Context Protocol) server for EAA Accessibility Scanner — run WCAG 2.1 AA accessibility audits directly from Claude Code, Claude Desktop, or any MCP-compatible AI agent.

Quick Start

Add to your Claude Code settings.json:

{
  "mcpServers": {
    "eaa-scanner": {
      "command": "npx",
      "args": ["-y", "eaa-accessibility-mcp"],
      "env": {
        "MCP_TOKEN": "your-mcp-token-here"
      }
    }
  }
}

Get your MCP token from the EAA Scanner platform: Settings > API Keys > Create New.

What You Can Do

Ask Claude to audit any website for accessibility compliance:

"Scan https://example.com for WCAG 2.1 AA accessibility issues"

"Show me the critical accessibility issues on my site"

"Compare the last two audits to see if accessibility improved"

"Generate an AGID accessibility declaration for the latest audit"

Available Tools

Read Operations

| Tool | Description | |------|-------------| | eaa_list_clients | List all clients in your organization | | eaa_list_projects | List projects, optionally filtered by client | | eaa_list_audits | List audits with filters (project, status) | | eaa_get_audit | Get full audit details with compliance metrics | | eaa_get_audit_issues | Get issues filtered by severity or WCAG criterion |

Write Operations

| Tool | Description | |------|-------------| | eaa_create_client | Create a new client (idempotent) | | eaa_create_project | Create a new project under a client (idempotent) | | eaa_run_scan | Start a WCAG 2.1 AA accessibility scan | | eaa_update_client | Update client information | | eaa_update_project | Update project details | | eaa_sign_audit | Digitally sign a completed audit |

Analytics

| Tool | Description | |------|-------------| | eaa_get_scan_status | Monitor scan progress in real-time | | eaa_get_compliance_summary | Compliance overview with trend analysis | | eaa_compare_audits | Compare two audits for progress/regression | | eaa_find_critical_issues | Find critical issues with suggested fixes | | eaa_get_platform_stats | Aggregated platform KPIs |

Reports & Compliance

| Tool | Description | |------|-------------| | eaa_generate_report | Generate professional HTML/PDF reports | | eaa_generate_agid_declaration | Generate AGID accessibility declaration (Italian law) |

Resources

| URI | Description | |-----|-------------| | eaa://compliance-levels | Compliance level definitions (conforme/parzialmente/non conforme) | | eaa://scanner-capabilities | Available scanners and WCAG coverage |

Scanners

EAA Scanner uses 5 automated testing engines:

• Pa11y — HTML5/ARIA validation, heading structure, contrast
• Axe-core — Gold standard automated testing, high precision
• Google Lighthouse — Accessibility + performance audit
• WAVE WebAIM — Visual accessibility evaluation
• QualWeb — ACT Rules + WCAG Techniques engine

Automated scanners cover approximately 30-40% of WCAG 2.1 AA success criteria.

Compliance Standards

• WCAG 2.1 Level AA — Web Content Accessibility Guidelines
• EN 301 549 v3.2.1 — European harmonized standard for ICT accessibility
• Directive (EU) 2019/882 — European Accessibility Act (EAA)
• AGID Guidelines — Italian accessibility declaration requirements

Compliance Levels

| Level | Score | Condition | |-------|-------|-----------| | Conforme | >= 85% | AND zero critical errors | | Parzialmente conforme | 60-84% | No critical errors | | Non conforme | < 60% | OR critical errors present |

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | MCP_TOKEN | Yes | Your MCP API key from the EAA Scanner platform | | EAA_API_URL | No | Custom backend URL (default: https://eaa.principi.it) |

Multi-Site Setup

You can connect multiple sites with different tokens:

{
  "mcpServers": {
    "site-a": {
      "command": "npx",
      "args": ["-y", "eaa-accessibility-mcp"],
      "env": { "MCP_TOKEN": "mcp_token-for-site-a" }
    },
    "site-b": {
      "command": "npx",
      "args": ["-y", "eaa-accessibility-mcp"],
      "env": { "MCP_TOKEN": "mcp_token-for-site-b" }
    }
  }
}

Security

• MCP tokens are scoped per organization with granular permissions
• Tokens can be revoked instantly from the platform
• All communication uses HTTPS
• No credentials stored in the npm package
• Token travels only in your local environment variables

Example Conversation

You: Scan principiadv.com for accessibility issues

Claude: I'll start an accessibility scan using EAA Scanner.
        [calls eaa_run_scan with URLs]
        Scan started! Monitoring progress...
        [calls eaa_get_scan_status]
        Scan complete: 73% compliance score.

        3 critical issues found:
        1. Missing alt text on 12 images (WCAG 1.1.1)
        2. Insufficient color contrast on navigation (WCAG 1.4.3)
        3. Missing form labels on contact form (WCAG 1.3.1)

        Would you like me to generate a full report or AGID declaration?

License

MIT

Links

• EAA Scanner Platform
• WCAG 2.1 Guidelines
• Model Context Protocol