Accessibility Hub MCP Server

# AccesibilityHub MCP Server for orchestrating web accessibility tools (axe-core, Pa11y, Lighthouse). Analyze web pages, check color contrast, get

Local serverstdio

What is the Accessibility Hub MCP server?

AccesibilityHub MCP Server for orchestrating web accessibility tools (axe-core, Pa11y, Lighthouse). Analyze web pages, check color contrast, get Lighthouse accessibility scores, and get detailed WCAG compliance reports with enriched. Exposed over MCP by the accessibility hub mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • analyze-with-axe — Analyze accessibility using axe-core
  • analyze-with-pa11y — Analyze accessibility using Pa11y
  • analyze-with-lighthouse — Analyze accessibility using Lighthouse (score 0-100)
  • analyze-contrast — Check color contrast (WCAG 2.1 / APCA)

Configuration

  • Node.js ≥ 20 - Chrome/Chromium (automatically downloaded by Puppeteer)

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at AccesibilityHub on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Accessibility Hub's toolset — analyze-with-axe, analyze-with-pa11y, analyze-with-lighthouse and 1 more — is a fair guide to whether it matches your workflow. It is maintained by drzkn; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Accessibility Hub's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the accessibility hub mcp server does with a few real requests.

Available tools

ToolWhat it does
analyze-with-axeAnalyze accessibility using axe-core
analyze-with-pa11yAnalyze accessibility using Pa11y
analyze-with-lighthouseAnalyze accessibility using Lighthouse (score 0-100)
analyze-contrastCheck color contrast (WCAG 2.1 / APCA)

How to install the Accessibility Hub MCP server

Add to your MCP client configuration:

```json
{
  "mcpServers": {
    "AccesibilityHub": {
      "command": "npx",
      "args": ["-y", "AccesibilityHub"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js ≥ 20 - Chrome/Chromium (automatically downloaded by Puppeteer)

Example prompts to try

  • Use Accessibility Hub to analyze-with-axe.
  • Use Accessibility Hub to analyze-with-pa11y.
  • Use Accessibility Hub to analyze-with-lighthouse.

Frequently asked questions

Node.js ≥ 20 and Chrome/Chromium (the latter is automatically downloaded by Puppeteer).