MCP server for web accessibility analysis using axe-core
MCP Web A11y MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for web accessibility analysis using axe-core.
An MCP (Model Context Protocol) server that provides web accessibility analysis capabilities using axe-core and Puppeteer.
Once MCP Web A11y is connected, these are the calls the assistant has available:
Parameters — The Parameters tool exposed by this serverBuilding — This will: 1. Compile TypeScript to JavaScript 2. Make the output file executable 3. Place the compiled files in the build directoryDebugging — The server includes detailed debug logging that can be observed in the console output. This includes: - Network requests and responses - Page loadingThe server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
You will need one environment variable: MCP_OUTPUT_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Web A11y's toolset — Parameters, Building, Debugging — is a fair guide to whether it matches your workflow. It is maintained by bilhasry-deriv; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Parameters | The Parameters tool exposed by this server. |
| Building | This will: 1. Compile TypeScript to JavaScript 2. Make the output file executable 3. Place the compiled files in the build directory |
| Debugging | The server includes detailed debug logging that can be observed in the console output. This includes: - Network requests and responses - Page loading status - Selector waiting status - Any console messages from the analy |
{
"mcpServers": {
"web-a11y": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"MCP_OUTPUT_DIR": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MCP_OUTPUT_DIR | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.