Skip to main content
Glama
forgekit-radix-mcp

forgekit-radix-mcp

by effinrich

forgekit-radix-mcp

Radix Primitives' APIs and accessibility contracts, exposed to AI coding agents.

Coding agents (Claude Code, Cursor) routinely hallucinate Radix prop names, drop required parts, and miss the ARIA/keyboard contract of a primitive. There's no machine-readable source of truth for how to use Radix correctly — only prose docs an agent has to guess from.

forgekit-radix-mcp is an MCP server that gives an agent the real thing: each primitive's parts, props, and — the part nobody else ships — its accessibility contract and the common mistakes to avoid.

My coding agent stopped hallucinating Radix props — and now it knows a tooltip isn't a label.

Part of ForgeKit. MIT licensed.

Why

Props can be inferred from types. The accessibility contract can't — that's hand-authored knowledge: which Provider is required, which part supplies the accessible name, what the keyboard model is, and the misuse that quietly breaks a11y (a Tooltip used as a label, a Popover that auto-opens a nested Tooltip, a Select with an empty-string item value). This server encodes that so agents generate correct, accessible Radix code on the first try.

Related MCP server: MCP Vue UI Kit Server

Install

npm i -g forgekit-radix-mcp
# or run on demand
npx forgekit-radix-mcp

Register with an MCP client

Claude Code / Cursor (stdio server):

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

Tools

Tool

Returns

list_primitives

Every documented primitive + one-line description

get_primitive

Parts, props by part, a11y contract, and a correct example

get_a11y_contract

Just the accessibility contract — highest-signal payload

Example

Agent call:

get_primitive  { "name": "Tooltip" }

Returns (abridged):

{
  "name": "Tooltip",
  "import": "import { Tooltip } from 'radix-ui';",
  "parts": ["Provider", "Root", "Trigger", "Portal", "Content", "Arrow"],
  "a11yContract": {
    "roles": "Content renders role=\"tooltip\"; Trigger gets aria-describedby when open",
    "keyboard": ["Tab: focus the trigger → opens instantly", "Escape: closes"],
    "focus": "Opens on focus AND hover; focus never moves into the tooltip",
    "requires": ["Tooltip.Provider must wrap the app once"],
    "commonMistakes": [
      "Using a tooltip for essential/interactive content (use Popover/HoverCard)",
      "Wrapping a disabled button directly — it fires no focus/hover events",
      "Using a tooltip as the only label for an icon button"
    ]
  },
  "correctExample": "<Tooltip.Provider> ... </Tooltip.Provider>"
}

Coverage

26 primitives. Dialog · AlertDialog · Popover · Tooltip · HoverCard · DropdownMenu · ContextMenu · Menubar · NavigationMenu · Select · Tabs · Accordion · Collapsible · Checkbox · RadioGroup · Switch · Toggle · ToggleGroup · Slider · Toast · Progress · Avatar · Label · Separator · AspectRatio · ScrollArea.

Data reflects the radix-ui public API and the WAI-ARIA Authoring Practices.

Pairs with WorkOS AuthKit MCP

For agents that act on behalf of a user, AuthKit MCP handles secured, tool-scoped access — forgekit-radix-mcp is a read-only knowledge server that slots cleanly behind it.

Development

npm install
npm run build
npm test

Available Tools

3 tools
get_a11y_contractA

Get just the accessibility contract for a primitive — roles, keyboard interactions, focus behavior, structural requirements, and the common mistakes to avoid. The highest-signal payload when wiring a component accessibly.

Inputs: name (required).

get_primitiveA

Get full metadata for a Radix primitive: composable parts, props by part, the accessibility contract, and a correct minimal example. Use before writing or editing any Radix component.

Inputs: name (required).

list_primitivesA

List every documented Radix primitive with a one-line description. Call this first to discover what is available.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: listing all primitives, getting full metadata for one, and retrieving only the accessibility contract. No ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_primitives, get_primitive, get_a11y_contract. Perfectly predictable.

    Tool Count5/5

    3 tools is ideal for a focused server that provides read-only access to primitive metadata. Each tool is essential and the set is well-scoped.

    Completeness4/5

    Covers discovery (list), full retrieval (get), and targeted contract retrieval for accessibility. Minor gap: no search or filtering, but the set is functionally complete for the intended use case.

    Related MCP Connectors

    Related MCP Servers