@svgrid/mcp 2.0.1 → 2.2.1
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 +20 -0
- package/dist/data.js +392 -101
- package/dist/index.js +37 -9
- package/dist/project-tools.js +391 -0
- package/package.json +6 -2
package/README.md
CHANGED
|
@@ -26,6 +26,26 @@ Point any MCP-capable client - Claude Desktop, Claude Code, Cursor, Zed - at thi
|
|
|
26
26
|
| `get_doc` | Markdown for a single doc by slug. |
|
|
27
27
|
| `search_docs` | Case-insensitive substring search across the docs. |
|
|
28
28
|
| `get_api_reference` | The curated public-API surface, grouped by category. |
|
|
29
|
+
| `introspect_source` | Studio: infer an `EntitySchema` from a Drizzle file or sample rows. |
|
|
30
|
+
| `scaffold_entity` | Studio: generate SvelteKit files for a single entity. |
|
|
31
|
+
|
|
32
|
+
### Studio: drive the app model (agent co-designer)
|
|
33
|
+
|
|
34
|
+
The `studio_*` tools let an agent build and edit the **same validated project model the visual designer uses** - add entities, screens, blocks, components, wire data sources, theme, RBAC, auth, the typed data layer, and the deploy target - then generate the full runnable app or export the `studio.config.json` the designer can Load. Every edit runs through the model's own functions + `validateProject`, so the agent can't produce an invalid app.
|
|
35
|
+
|
|
36
|
+
| Tool | Purpose |
|
|
37
|
+
| --- | --- |
|
|
38
|
+
| `studio_new_project` / `studio_load_project` | Start fresh, or load an existing `studio.config.json`. |
|
|
39
|
+
| `studio_describe_project` / `studio_get_config` | Inspect the model / export it as `studio.config.json`. |
|
|
40
|
+
| `studio_capabilities` | List block kinds, component keys, theme presets, data-source kinds, deploy targets. |
|
|
41
|
+
| `studio_add_entity` | Add a table/model (+ default screen), by schema or introspection. |
|
|
42
|
+
| `studio_add_screen` / `studio_add_block` / `studio_add_component` | Compose screens from data blocks + UI components. |
|
|
43
|
+
| `studio_set_entity_source` | Bind an entity to memory / SQL / Supabase / REST / PGlite. |
|
|
44
|
+
| `studio_set_theme` / `studio_set_access` / `studio_set_auth` / `studio_set_data_layer` / `studio_set_deploy_target` | Configure app-wide features. |
|
|
45
|
+
| `studio_validate` | Report errors + warnings. |
|
|
46
|
+
| `studio_generate_app` | Emit every file of the runnable SvelteKit app. |
|
|
47
|
+
|
|
48
|
+
A typical session: `studio_new_project` → `studio_add_entity` (×N) → `studio_set_entity_source` → `studio_set_data_layer` → `studio_set_auth` → `studio_generate_app` → write the files and run `svelte-check`.
|
|
29
49
|
|
|
30
50
|
## Run
|
|
31
51
|
|