@dforge-core/dforge-mcp 0.2.28 → 0.2.30
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 +4 -3
- package/dist/server.js +653 -243
- package/docs/creating-modules.md +1 -1
- package/package.json +46 -48
- package/resources/docs/conventions.md +2 -0
- package/resources/schemas/diagram.schema.json +101 -0
- package/resources/schemas/entity.schema.json +1 -1
- package/skills/dforge-mcp-author/SKILL.md +1 -1
- package/skills/dforge-module-build/SKILL.md +3 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @dforge-core/dforge-mcp
|
|
2
2
|
|
|
3
|
-
MCP server for dForge module authoring. Exposes
|
|
3
|
+
MCP server for dForge module authoring. Exposes 35 composable tools and the canonical schemas so AI agents (Claude Code, Cursor, Zed, etc.) can drive the full module lifecycle — scaffold → entities → actions → views → security → install — through structured tool calls instead of free-form JSON generation.
|
|
4
4
|
|
|
5
5
|
Ships with **four Claude Skills** (`skills/`): a router plus one skill per lifecycle stage — design (Phase 0), build (Phases 1-5), and ship (Phase 6). The router directory carries 25 reference files (field types, flags, traits, formulas, DSL, security, etc.) and two annotated example modules.
|
|
6
6
|
|
|
@@ -74,7 +74,7 @@ claude mcp list
|
|
|
74
74
|
# Should show: dforge — npx -y @dforge-core/dforge-mcp — connected
|
|
75
75
|
```
|
|
76
76
|
|
|
77
|
-
Or inside a Claude Code session, type `/mcp` to see all connected servers + their tools. The
|
|
77
|
+
Or inside a Claude Code session, type `/mcp` to see all connected servers + their tools. The 35 `dforge_*` tools should be listed.
|
|
78
78
|
|
|
79
79
|
### Cursor / Zed
|
|
80
80
|
|
|
@@ -157,6 +157,7 @@ The field/entity tools validate against the `@dforge-core/metadata` registry: an
|
|
|
157
157
|
| Tool | Behavior |
|
|
158
158
|
|---|---|
|
|
159
159
|
| `dforge_dependency_add` | Add a dep on another dForge module |
|
|
160
|
+
| `dforge_diagram_add` | Create or extend a named entity diagram, `docs/diagrams/<code>.json` (design-time only) — one per functional area of a large module. Takes entity keys and/or `fromFolder` (a folder's entities plus its descendants'); appends only, keeping placed positions. Rejects a key that resolves to no own or dependency entity |
|
|
160
161
|
| `dforge_dbml_import` | **DBML front-end** to `module_import` — parses DBML (Table blocks, typed columns, inline + top-level refs) into the table-spec, drops the source PK (identity provides `{entity}_id`), and imports. Pass `module` for a greenfield import |
|
|
161
162
|
|
|
162
163
|
### Writing files: preview vs `apply`
|
|
@@ -179,7 +180,7 @@ Served over MCP with descriptions and mime types, so the agent can tell what a U
|
|
|
179
180
|
|
|
180
181
|
| URI pattern | Content |
|
|
181
182
|
|---|---|
|
|
182
|
-
| `dforge://schema/<name>` | JSON Schemas: `manifest`, `entity`, `domains`, `data-views`, `folders`, `menus`, `roles`, `jobs`, `seed-data`, `traits`, `webhooks`, `triggers`, `print-templates`, `settings`, `reports` |
|
|
183
|
+
| `dforge://schema/<name>` | JSON Schemas: `manifest`, `entity`, `domains`, `data-views`, `folders`, `diagram`, `menus`, `roles`, `jobs`, `seed-data`, `traits`, `webhooks`, `triggers`, `print-templates`, `settings`, `reports` |
|
|
183
184
|
| `dforge://reference/<name>` | 25 per-element authoring references — schema shape + worked example + common-mistakes list for one element type |
|
|
184
185
|
| `dforge://example/<path>` | Files from the canonical `simple-todo` module (mandatory structure validators) |
|
|
185
186
|
| `dforge://example/matrix-budget/<path>` | Files from the `matrix` (pivot) view example |
|