@treeui/mcp 0.4.0 → 0.5.0

package/README.md

@@ -5,13 +5,37 @@ TreeUI ships a local Model Context Protocol server so coding agents can:
 - search the TreeUI component catalog
 - retrieve setup guidance for consumers
 - compare similar components such as `TSelect` vs `TCombobox`
+- look up `--tree-*` design tokens before hardcoding a value
 - read normalized machine-oriented metadata generated from `docs/ai`
 
 ## What it serves
 
-- a generated catalog built from `docs/ai/*.yaml`
-- MCP resources for catalog, setup, selection, recipes, and per-component metadata
-- MCP tools for search, recommendation, setup lookup, and recipe search
+- a generated catalog built from `docs/ai/*.yaml` and `@treeui/tokens`
+- MCP resources for catalog, setup, selection, recipes, tokens, and per-component metadata
+- MCP tools for search, recommendation, setup lookup, recipe search, and token search
+
+## Token search
+
+`search_tokens` matches a query against the CSS variable, the token
+category/path, and the value the token actually ships, so a literal found in
+consumer code resolves back to the token that already provides it:
+
+```
+search_tokens("space")               -> --tree-space-0 … --tree-space-16
+search_tokens("status")              -> --tree-color-status-success | warning | error | info
+search_tokens("#0969da")             -> --tree-color-brand-primary (light #0969da | dark #539bf5)
+search_tokens("64rem")               -> --tree-breakpoint-lg (1024px)
+search_tokens("--tree-gradient-brand") -> --tree-gradient-brand
+```
+
+Themed tokens report every theme value, and `rem`/`px` length queries are
+matched in both units.
+
+The token entries are derived from `treeTokens`/`treeThemes` in
+`@treeui/tokens` using the same path-to-variable-name rule as
+`packages/tokens/src/css.ts`, so they cannot drift from the shipped stylesheet.
+`catalog.test.ts` enforces that by diffing the emitted variables and values
+against `createFoundationCss()` and `createThemeCss()`.
 
 ## Local usage in this repository