a11y-ui-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
A11yKit: senior-first, WCAG AAA-minded UI components. Call list_components first, then get_component for source, get_ai_prompt for an implementation prompt, and check_wcag_checklist for the manual accessibility checks. Free components are MIT; Pro components return a lock notice. Everything runs locally.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | List the 18 senior-first components with tier (free/pro), WCAG criteria and tags. Filter by tier, tag or keyword. Free components include MIT source; Pro components list the spec only. |
| get_componentA | Return one component: plain HTML/CSS/JS source, a React version, WCAG criteria, accessibility notes and labels. Pro components return the spec and a lock notice instead of source. |
| get_ai_promptA | Return a paste-ready implementation prompt for Claude Code, Cursor, Lovable or a generic agent, in English or Korean. Pro components return a lock notice. |
| check_wcag_checklistA | Return the WCAG criteria that apply to a component, each with the manual check a human must run and the component-specific accessibility notes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a largely distinct role: catalog listing, single-component retrieval, prompt generation, and WCAG checklist lookup. The only overlap is that get_component also returns WCAG criteria, which check_wcag_checklist expands with manual checks and notes, so an agent could occasionally hesitate between the two.
All four names follow a clear verb_noun pattern (list_components, get_component, get_ai_prompt, check_wcag_checklist). No mixed casing or inconsistent verb styles.
Four tools is a tight, well-scoped surface for a component catalog with three read paths plus a checklist helper. It is slightly thin (no search or tier/version discovery tool separate from list), but nothing feels redundant.
The read-only lifecycle (list, get, prompt, accessibility check) is covered, and filtering by tier/tag/keyword substitutes for a dedicated search tool. Minor gaps remain: no way to enumerate WCAG criteria globally, no versioning/changelog access, and Pro content is intentionally spec-only, which agents must work around.