Skip to main content
Glama
Accessibility MCP

Accessibility MCP

by ksmuvva

Related Servers

Alternatives to Accessibility MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables automated WCAG 2.2 AA accessibility audits of Figma designs and webpages. Generates detailed markdown reports with severity-grouped violations, specific criterion references, and concrete fix recommendations.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to perform comprehensive accessibility audits on websites using Playwright and axe-core against WCAG standards. Provides detailed compliance reports with violation summaries and remediation guidance across multiple browsers.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agentic accessibility auditing of a URL through a tool that runs axe-core, zoom and WCAG text-spacing checks, a keyboard-focus agent, and visual analysis, returning fixes as Markdown plus structured results. Keeps Chromium warm between calls so an agent can audit, apply fixes, and re-audit the same page to see what changed.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Audits web pages and local HTML files against WCAG 2.2 with the pour accessibility engine. Returns proven failures, the items that need a person to review, the keyboard focus order, and screenshots, using Chrome on your own machine.
      3
      439 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 41 tools

    Disambiguation4/5

    Tools are largely distinct with clear descriptions, but some overlap exists (e.g., audit_automated_checks vs audit_axe, or audit_url vs audit_current_page). The group and principle audits are well separated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (audit_*, browser_*, list_*, etc.). No mix of styles, highly predictable.

    Tool Count3/5

    41 tools is on the high side but justified by the breadth of accessibility auditing (multiple engines, groups, principles, site crawl, browser session). Could be streamlined but not excessive.

    Completeness5/5

    The tool surface covers automated checks, manual checks, multiple engines, site crawling, browser interactions, rule listing, and statement generation. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues