Your agent asks the design system.

garn-mcp is a standalone package — no clone, no build. It bundles a metadata snapshot of the garn version it was published against, so it runs straight from npx. Install the version matching the source you copied in.

The garn CLI writes the config for you, version-matched to what is in your project:

npx garn-ui mcp install

Or register it by hand — Claude Code:

claude mcp add garn -- npx -y garn-mcp

Cursor and every other client take the same command as a JSON entry:

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

Point the server at a newer or custom metadata directory with GARN_INFO_DIR=/path/to/out in its env.

• garn_search

  Find components by keyword, pattern or category. Ranked — this is where a task starts.

• garn_view

  The full reference for one component. `sections` slices it so a lookup costs a few hundred tokens, not thousands.

• garn_get_examples

  Type-checked example code, filterable by role — ask for the canonical one and paste it.

• garn_match_recipe

  An intent in, the best-fit compositions out, each with the accessibility it requires.

• garn_relations

  What pairs with, composes with, or replaces what — the graph behind every roster page.

• garn_audit

  Lint a composition against the a11y contracts, token discipline and the do/don'ts before you ever see it.

The tools are called by the agent, not by you — there is nothing to memorise. Once the server is registered, ask in plain words:

• Add a filterable data table with pinned columns and row selection.
• Which garn component should I use for a multi-step form?
• Audit this dialog against garn's accessibility contracts.
• Show me the canonical combobox example with async loading.

The same corpus is served flat, for tools that only read text. The agents page covers llms.txt, the per-component markdown, and what to put in a project's rules file.