ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Atag MCP server exists for a simple reason — assistants are far more useful when they can act on Atag directly instead of describing what you should do. ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers.
An MCP (Model Context Protocol) server that provides guidance on ATAG 2.0 — the W3C Authoring Tool Accessibility Guidelines — to help authoring tool developers build more accessible software.
ATAG 2.0 defines how authoring tools (rich-text editors, CMSes, IDEs, website builders, etc.) should:
The server ships on npm as npm, 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.
Once Atag is connected, these are the calls the assistant has available:
get-server-info — Dataset statistics and attributionexplain-atag — Overview of ATAG, how it differs from WCAG, and its two-part structurelist-parts — Part A and Part B summarieslist-principles — All 8 principles, filterable by partlist-guidelines — All 24 guidelines, filterable by part or principlelist-success-criteria — All 63 success criteria, filterable by part, principle, guideline, or levelget-criterion — Full details for a specific SC (e.g. B.2.3.1)get-guideline — Full guideline details with all child success criteriaget-criteria-by-level — All criteria at Level A, AA, or AAAsearch-atag — Keyword search across all ATAG contentlist-glossary-terms — All ATAG glossary termsget-glossary-term — Definition of a specific ATAG termThis sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Atag's toolset — get-server-info, explain-atag, list-parts and 10 more — is a fair guide to whether it matches your workflow. It is maintained by MMasey; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Atag's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get-server-info | Dataset statistics and attribution |
| explain-atag | Overview of ATAG, how it differs from WCAG, and its two-part structure |
| list-parts | Part A and Part B summaries |
| list-principles | All 8 principles, filterable by part |
| list-guidelines | All 24 guidelines, filterable by part or principle |
| list-success-criteria | All 63 success criteria, filterable by part, principle, guideline, or level |
| get-criterion | Full details for a specific SC (e.g. B.2.3.1) |
| get-guideline | Full guideline details with all child success criteria |
| get-criteria-by-level | All criteria at Level A, AA, or AAA |
| search-atag | Keyword search across all ATAG content |
| list-glossary-terms | All ATAG glossary terms |
| get-glossary-term | Definition of a specific ATAG term |
| get-guidance | **Key tool** — describe a feature you're building and get the most relevant ATAG criteria |
{
"mcpServers": {
"atag-mcp": {
"command": "npx",
"args": ["-y", "atag-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.