@wizeworks/silicaui-mcp 0.36.0 → 0.37.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +35 -2
- package/dist/data/components.json +2861 -0
- package/dist/server.js +56 -10
- package/dist/server.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -58,13 +58,46 @@ add to `.cursor/mcp.json`:
|
|
|
58
58
|
No API key, account, or network access required after install — everything the
|
|
59
59
|
server answers with is bundled in the package.
|
|
60
60
|
|
|
61
|
+
## The three delivery paths
|
|
62
|
+
|
|
63
|
+
Silica UI is one design system consumed three different ways, and the server
|
|
64
|
+
tells every connecting client so up front (via MCP `instructions`, which clients
|
|
65
|
+
surface before the first tool call) — because the choice is made *before* any
|
|
66
|
+
tool gets called, and getting it wrong is the most common way an integration
|
|
67
|
+
breaks.
|
|
68
|
+
|
|
69
|
+
| Path | Package | You write | Interactive? |
|
|
70
|
+
| --- | --- | --- | --- |
|
|
71
|
+
| **CSS** | `@wizeworks/silicaui` | Plain HTML + classes: `<button class="btn btn-primary">` | No — no JS ships |
|
|
72
|
+
| **React** | `@wizeworks/silicaui-react` | `<Button color="primary" size="lg">` | Yes, via Base UI |
|
|
73
|
+
| **HTML / node-tree** | `@wizeworks/silicaui-html` + `@wizeworks/silicaui-behaviors` | A node tree that projects to HTML with `data-sui-*` markers | Yes, once the behaviors runtime loads |
|
|
74
|
+
|
|
75
|
+
`get_component` answers on all three. Called without a `package`, it returns
|
|
76
|
+
every path's shape side by side so an assistant can see how they differ rather
|
|
77
|
+
than guessing which one it wants:
|
|
78
|
+
|
|
79
|
+
```jsonc
|
|
80
|
+
// get_component({ name: "Button" })
|
|
81
|
+
{
|
|
82
|
+
"name": "button",
|
|
83
|
+
"note": "\"Button\" exists on 3 delivery paths … they are not interchangeable.",
|
|
84
|
+
"paths": [
|
|
85
|
+
{ "package": "@wizeworks/silicaui", "root": "btn", "classes": ["btn", "btn-outline", …], "colorVariants": ["btn-primary", …] },
|
|
86
|
+
{ "package": "@wizeworks/silicaui-react", "props": [ … ], "usageExample": "…" },
|
|
87
|
+
{ "package": "@wizeworks/silicaui-html", "category": "content", "label": "Button", "container": false, "behaviors": [] }
|
|
88
|
+
]
|
|
89
|
+
}
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Pass `package` to get just one.
|
|
93
|
+
|
|
61
94
|
## Tools
|
|
62
95
|
|
|
63
96
|
| Tool | Purpose |
|
|
64
97
|
| --- | --- |
|
|
65
98
|
| `list_packages` | The Silica UI package family, purpose, install command, version. |
|
|
66
|
-
| `list_components({ package? })` | Component names + categories, optionally filtered to one package. |
|
|
67
|
-
| `get_component({ name })` | A component's real props (from source) + a real usage example
|
|
99
|
+
| `list_components({ package? })` | Component names + categories across all three paths, optionally filtered to one package. |
|
|
100
|
+
| `get_component({ name, package? })` | A component's real shape on each path: CSS root class + classes + color variants, React props (from source) + a real usage example, or the `-html` macro and its behaviors. |
|
|
68
101
|
| `list_classes({ component? })` | Exact, literal CSS class names — extracted from the actual class generators. |
|
|
69
102
|
| `get_tokens()` | Semantic color list, light/dark values, typography tokens. |
|
|
70
103
|
| `list_blocks({ category?, tag? })` | Composed page blocks (hero, FAQ, feature grid, …), summary only. |
|