@kazee-ds/mcp 0.1.7 → 0.1.8
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 +44 -42
- package/dist/catalog.json +9854 -12
- package/package.json +5 -5
- package/src/guides.mjs +1 -1
package/README.md
CHANGED
|
@@ -1,42 +1,44 @@
|
|
|
1
|
-
# Kazee Design System MCP
|
|
2
|
-
|
|
3
|
-
Read-only, offline stdio tools for the public React and Vue APIs. No Storybook process is required. The server never installs packages, executes commands, scans a project or reads registry credentials.
|
|
4
|
-
|
|
5
|
-
## Configuration
|
|
6
|
-
|
|
7
|
-
After confirming MCP `0.1.
|
|
8
|
-
|
|
9
|
-
```json
|
|
10
|
-
{
|
|
11
|
-
"mcpServers": {
|
|
12
|
-
"kazee": {
|
|
13
|
-
"command": "npx",
|
|
14
|
-
"args": ["-y", "@kazee-ds/mcp@0.1.
|
|
15
|
-
}
|
|
16
|
-
}
|
|
17
|
-
}
|
|
18
|
-
```
|
|
19
|
-
|
|
20
|
-
Before publication, use `node` with the absolute `bin/kazee-mcp.mjs` path from a local checkout or installed `.tgz` package. Other clients use their own MCP configuration format. Preserve existing servers; restart/reconnect the client after configuration changes. Public npm downloads need no read token; the running server itself needs no network connection. Keep actual tokens out of `.mcp.json`.
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
1
|
+
# Kazee Design System MCP
|
|
2
|
+
|
|
3
|
+
Read-only, offline stdio tools for the public React and Vue APIs. No Storybook process is required. The server never installs packages, executes commands, scans a project or reads registry credentials.
|
|
4
|
+
|
|
5
|
+
## Configuration
|
|
6
|
+
|
|
7
|
+
After confirming MCP `0.1.8` publication, merge this entry into the application's Claude Code `.mcp.json`:
|
|
8
|
+
|
|
9
|
+
```json
|
|
10
|
+
{
|
|
11
|
+
"mcpServers": {
|
|
12
|
+
"kazee": {
|
|
13
|
+
"command": "npx",
|
|
14
|
+
"args": ["-y", "@kazee-ds/mcp@0.1.8"]
|
|
15
|
+
}
|
|
16
|
+
}
|
|
17
|
+
}
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Before publication, use `node` with the absolute `bin/kazee-mcp.mjs` path from a local checkout or installed `.tgz` package. Other clients use their own MCP configuration format. Preserve existing servers; restart/reconnect the client after configuration changes. Public npm downloads need no read token; the running server itself needs no network connection. Keep actual tokens out of `.mcp.json`.
|
|
21
|
+
|
|
22
|
+
MCP `0.1.8` adds verified catalog `0.5.5` (React/Vue/styles `0.5.5`, tokens `0.4.4`, lint `0.4.2`) with contrasting field/control boundaries and decorative subtle borders. Earlier catalogs retain their original token values.
|
|
23
|
+
|
|
24
|
+
## Tools
|
|
25
|
+
|
|
26
|
+
MCP `0.1.8` retains registry-verified catalogs `0.2.0`, `0.3.0`, `0.4.0`, `0.5.1`, `0.5.2`, `0.5.3`, `0.5.4`, and `0.5.5`. The `0.5.4` catalog uses React/Vue/styles `0.5.4`, tokens `0.4.3` and lint `0.4.2`, with consistent subtle borders (`#DBDBDB` in light mode). The `0.5.3` catalog uses React/Vue/styles `0.5.3` and tokens/lint `0.4.2`, with guarded Toast keyboard handling. The `0.5.2` catalog uses React/Vue/styles `0.5.2` and tokens/lint `0.4.1`; the retained `0.5.1` catalog keeps its original tokens/lint `0.4.0`. These snapshots come from actual npm archives with checksum provenance, including Toast/ToastProvider and optional close/progress controls.
|
|
27
|
+
|
|
28
|
+
Use the exact installed framework version. The separate `0.5.5-workspace` preview is for checkout review and matching local packed artifacts. Confirm this MCP patch is published, update the exact client pin and reconnect before using its new verified catalogs through npx. Older MCP `0.1.4` retains verified catalogs only through `0.4.0` and labels `0.5.1` as a workspace candidate.
|
|
29
|
+
|
|
30
|
+
Public npm installation needs no read token. Historical snapshots retain their original registry provenance and are never overwritten. See the [version matrix](https://gitlab.com/kazee.indonesia/kazee-design-system/-/blob/main/docs/versions.md).
|
|
31
|
+
|
|
32
|
+
1. `get_catalog_versions`: exact supported versions and provenance.
|
|
33
|
+
2. `list_components`: browse/search by framework, version, function or keyword.
|
|
34
|
+
3. `get_component_docs`: public props, discriminated variants, related types, Vue events/slots and composition limits.
|
|
35
|
+
4. `get_component_examples`: complete, typechecked TSX/Vue examples.
|
|
36
|
+
5. `get_theme_variables`: semantic light/dark CSS variables and resolved values.
|
|
37
|
+
6. `get_installation`: pinned package commands, global CSS and lint guidance.
|
|
38
|
+
7. `get_guides`: agent workflow, framework differences, styling and application composition.
|
|
39
|
+
|
|
40
|
+
All tools carry read-only annotations. `kazee://guides/workflow` and `kazee://catalog/versions` are also exposed as resources.
|
|
41
|
+
|
|
42
|
+
Always supply the exact installed framework package version, obtained from its public package manifest or lockfile. The server rejects unknown versions instead of substituting newer APIs. Both `0.2.0` (eight components per framework) and `0.3.0` (32 per framework) use declarations and tokens extracted from published GitLab registry archives. Their provenance retains SHA-256 archive hashes. The retained catalogs correct the stale candidate label shipped in MCP `0.1.0`. Publishing a new MCP catalog is a separate release step. Registry verification records a build-time check, not live registry availability.
|
|
43
|
+
|
|
44
|
+
Examples use public `@kazee-ds/react` / `@kazee-ds/vue` imports. The package does not provide shadcn-style component source installation or hosted HTTP transport. MCP supplies reference material; AGENTS.md and consumer lint guide and enforce usage. Successful tool calls do not establish agent instruction-following or production adoption.
|