@cascivo/mcp 0.1.0 → 0.1.1

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@cascivo/mcp",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "private": false,
-  "description": "MCP server exposing the cascade component registry to AI agents",
+  "description": "MCP server exposing the cascivo component registry to AI agents",
   "keywords": [
     "ai",
     "cascivo",
@@ -48,7 +48,7 @@
   "devDependencies": {
     "@types/node": "^25",
     "typescript": "^5",
-    "vite-plus": "^0.1.24"
+    "vite-plus": "^0.2.1"
   },
   "scripts": {
     "build": "vp pack && node -e \"const fs=require('fs');const f='dist/index.mjs';const c=fs.readFileSync(f,'utf8');if(!c.startsWith('#!/'))fs.writeFileSync(f,'#!/usr/bin/env node\\n'+c);fs.copyFileSync('../../registry.json','dist/registry.json')\" && chmod +x dist/index.mjs",

package/readme.body.md

@@ -17,17 +17,40 @@ The server speaks the MCP stdio transport. By default it reads the `registry.jso
 
 ## Tools
 
-| Tool                | Input                                 | Returns                                                  |
-| ------------------- | ------------------------------------- | -------------------------------------------------------- |
-| `list_components`   | `{ category? }`                       | All component manifests, optionally filtered by category |
-| `get_component`     | `{ name }`                            | The full manifest for one component                      |
-| `search_components` | `{ query }`                           | Components matching name, tags, or description           |
-| `add_to_project`    | `{ name, outputDir? }`                | Runs `cascivo add <name>` as a child process             |
-| `create_theme`      | `{ primary, neutral, accent, name? }` | A custom theme as CSS (semantic token layer)             |
-| `scaffold_page`     | `{ description, components? }`        | A JSX page layout string                                 |
+| Tool                | Input                                 | Returns                                                                              |
+| ------------------- | ------------------------------------- | ------------------------------------------------------------------------------------ |
+| `list_components`   | `{ category? }`                       | All component manifests, optionally filtered by category                             |
+| `get_component`     | `{ name }`                            | The full manifest for one component                                                  |
+| `search_components` | `{ query }`                           | Components matching name, tags, or description                                       |
+| `add_to_project`    | `{ name, outputDir? }`                | Runs `cascivo add <name>` as a child process                                         |
+| `create_theme`      | `{ primary, neutral, accent, name? }` | A custom theme as CSS (semantic token layer)                                         |
+| `scaffold_page`     | `{ description, components? }`        | A JSX page layout string                                                             |
+| `scaffold_view`     | `{ description, components? }`        | A validated starter `ViewConfig` + the bound-vocabulary `grammar` for its components |
+| `validate_view`     | `{ config }`                          | Validation errors (component, prop type/enum, refs) with exact paths                 |
+| `get_view_grammar`  | `{ components? }`                     | Bound-vocabulary grammar + generation prompt for valid `ViewConfig` JSON             |
 
 `category` is one of `inputs`, `display`, `overlay`, `navigation`, `feedback`.
 
+### Bound-vocabulary generation (anti-hallucination)
+
+`get_view_grammar` derives — from the `component.meta.ts` manifests — a **system
+prompt** plus a compact **allowed-vocabulary grammar** (each component → its
+props → enum/size/variant values) for emitting valid `ViewConfig` JSON rendered
+by `@cascivo/render` `<CascadeView />`. This is [OpenUI](https://openui.com)'s
+"generate the system prompt from the component library" mechanism (see
+[`docs/ROADMAP-V40.md`](../../docs/ROADMAP-V40.md)): because the grammar is
+**derived**, not authored, an LLM is structurally prevented from inventing
+components, props, or enum values, and the grammar can never drift from the
+components. Pair it with `validate_view` (which now also checks prop types/enums)
+as the enforcement backstop.
+
+```ts
+import { buildGenerationPrompt, loadRegistry } from '@cascivo/mcp'
+
+const prompt = buildGenerationPrompt(loadRegistry(), { components: ['Badge', 'Button'] })
+// → use as the system prompt; the model can only emit Badge/Button with their real props.
+```
+
 ## Programmatic use
 
 ```ts