MCP.Market

Atag MCP server

by MMasey·io.github.MMasey/atag-mcp·v1.0.2·1 stars
No reviews yet

ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

1 stars36 downloads/wk

Reviews

Write one

Nobody has reviewed Atag yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Atag tools (13)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • explain-atag

    Get an overview of ATAG 2.0 — what it is, who it applies to, how it differs from WCAG, and its two-part structure.

  • get-criteria-by-level

    Get all ATAG 2.0 success criteria at a specific conformance level (A, AA, or AAA). Optionally filter by part.

  • get-criterion

    Get full details for a specific ATAG 2.0 success criterion by ID (e.g. 'B.2.3.1' or 'A.3.1.2'), including description, conformance level, and implementation notes.

  • get-glossary-term

    Get the definition of a specific ATAG 2.0 term.

  • get-guidance

    Given a description of an authoring tool feature or scenario, return the most relevant ATAG 2.0 success criteria. Use this to find which criteria apply when building a specific feature.

  • get-guideline

    Get full details for a specific ATAG 2.0 guideline by ID (e.g. 'B.2.3'), including its description and all child success criteria.

  • get-server-info

    Get information about this ATAG MCP server including the total number of principles, guidelines, success criteria, and glossary terms available.

  • list-glossary-terms

    List all ATAG 2.0 glossary terms.

  • list-guidelines

    List ATAG 2.0 guidelines. Optionally filter by part (A or B) and/or principle ID (e.g. 'A.3').

  • list-parts

    List both parts of ATAG 2.0 with their descriptions and principle counts.

  • list-principles

    List ATAG 2.0 principles. Optionally filter by part (A or B).

  • list-success-criteria

    List ATAG 2.0 success criteria. Filter by part, principle ID, guideline ID, and/or conformance level.

  • search-atag

    Search across all ATAG 2.0 content (principles, guidelines, success criteria, glossary) using keywords.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan10 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 81 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Atag compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
13
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
36
more than 26% of 12,191 servers with a package

What its tools let an agent do: 13 read

Install Atag in Claude Code, Cursor or VS Code

Runs npx -y atag-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add atag-mcp -- npx -y atag-mcp
Add to Cursor

What the publisher says

From the Atag repository's README, as published. We do not edit it. Read it on GitHub

ATAG MCP

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.

What is ATAG?

ATAG 2.0 defines how authoring tools (rich-text editors, CMSes, IDEs, website builders, etc.) should:

  • Part A — Be accessible to authors with disabilities (the tool's own UI)
  • Part B — Help authors produce accessible web content (alt text prompts, accessibility checkers, accessible templates, etc.)

Why this exists

ATAG 2.0 has been a W3C Recommendation since 2015, but adoption among authoring tools remains limited — partly because the guidance is easy to overlook at the moment design and implementation decisions are actually made. With more authoring tool features now being built with the help of AI coding assistants, this server puts the full spec within the assistant's reach: describe the feature you're working on (an image upload dialog, a rich-text toolbar, a template picker) and get back the actual success criteria that apply, rather than a half-remembered summary. The aim is to lower the cost of considering ATAG at all — the first step towards tools that support it.

The data is a static, hand-checked copy of the ATAG 2.0 spec — not fetched or generated at runtime — so answers stay faithful to the W3C source. A weekly workflow checks for upstream spec changes.

Tools

Setup

No local install required — add the config below and your MCP client will fetch the package automatically via npx.

Claude Desktop

Edit ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows):

{
  "mcpServers": {
    "atag-mcp": {
      "command": "npx",
      "args": ["-y", "atag-mcp"]
    }
  }
}

VS Code (Claude extension)

{
  "mcp": {
    "servers": {
      "atag-mcp": {
        "type": "stdio",
        "command": "npx",
        "args": ["-y", "atag-mcp"]
      }
    }
  }
}

Local development install

npm install
npm run build
# then point your config to dist/index.js directly

Usage examples

Ask Claude:

  • "What ATAG criteria apply to an image insertion dialog?" → uses get-guidance
  • "Show me all Level A criteria from Part B" → uses get-criteria-by-level
  • "Explain guideline B.3.1" → uses get-guideline
  • "What does 'editing-view' mean in ATAG?" → uses get-glossary-term
  • "Search ATAG for keyboard access" → uses search-atag

Development

npm run dev          # Run server directly with tsx (no compile step)
npm test             # Run all tests
npm run test:watch   # Watch mode
npm run validate-data  # Validate data/atag.json structure
npm run check-updates  # Check if W3C spec has changed

Branching and commits

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Atag: common questions

Is Atag MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Atag safety report
How do I install Atag?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Atag need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Atag maintained?
The last commit was 120 days ago (2026-07-07). The latest release is v1.0.2.
How does Atag compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 13 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.