Atag MCP

Name: Atag MCP
Author: MMasey

by MMaseyversion 1.0.2i★ 1iRuns on your computer

Registry nameio.github.MMasey/atag-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
UsageiVery new↓ 46/wk · ★ 1

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 2 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add atag -- npx -y atag-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account MMasey, which owns the repo
✓ Pass
Still maintained
Code last changed 4 months ago
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 82% of the other 19064 servers in this category
Published to the registry more recently than 13% of the other 19064 servers in this category
Basic checks equal to or better than 100% of the other 19064 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Atag MCP safe?

It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 4 months ago, and the latest version (1.0.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, Claude Flow, Tldraw

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.

by koala73Widely used★ 90.4KUpdated 5 days ago

Runs in the cloud✓ worldmonitor.app

Install

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

by ruvnetWidely used↓ 14.3K/wk★ 81.4KUpdated 14 months ago

Runs on your computer

Install

Tldraw

Draw and visually collaborate with your agents on tldraw's canvas.

by tldrawWidely used★ 51.4KUpdated 8 months ago

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Tool	Description
`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

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/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.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

This project follows git flow with Conventional Commits:

main — released code only; every merge to main is tagged and published
develop — integration branch; day-to-day work lands here
feature/ — branched from and merged back to develop
release/ — branched from develop, merged to main (tagged) and back to develop
hotfix/ — branched from main for urgent fixes, merged to both main and develop

Commit messages use conventional prefixes: feat:, fix:, docs:, test:, ci:, chore:, refactor: (with ! or a BREAKING CHANGE: footer for breaking changes).

Releasing

Versioning uses standard npm version bumps. Pushing a v* tag triggers the GitHub Actions publish workflow, which runs tests and publishes to npm automatically.

npm version patch   # bug fixes:    1.0.0 → 1.0.1

npm version minor # new features: 1.0.0 → 1.1.0 npm version major # breaking: 1.0.0 → 2.0.0

git push && git push --tags

When bumping the version, also update the version fields in server.json to match — the MCP Registry validates them against the published npm package. After the npm publish succeeds, refresh the registry listing with:

mcp-publisher login github

mcp-publisher publish

Publishing requires the NPM_TOKEN repository secret (a granular npm access token with write access to atag-mcp). If the token expires or is rotated, add the new one under the same secret name, then run the manual Check npm token workflow (Actions tab) to verify it authenticates before tagging a release.

Keeping data current

The ATAG 2.0 spec is captured in data/atag.json. The GitHub Actions workflow (.github/workflows/update-atag.yml) runs weekly and opens an issue if the W3C spec content changes.

To update manually:

Review changes at https://www.w3.org/TR/ATAG20/
Edit data/atag.json with the changes
Run npm run validate-data to check structure
Run npm run check-updates -- --save to update the stored hash

Data

Version: ATAG 2.0
Specification: https://www.w3.org/TR/ATAG20/
Parts: 2 (Part A + Part B)
Principles: 8
Guidelines: 24
Success Criteria: 63
Glossary Terms: 18

License

MIT

Atag MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

World Monitor

Claude Flow

Tldraw

README from the maker

ATAG MCP

What is ATAG?

Why this exists

Tools

Setup

Claude Desktop

VS Code (Claude extension)

Local development install

then point your config to dist/index.js directly

Usage examples

Development

Branching and commits

Releasing

Keeping data current

Data

License