Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues