@restforgejs/mcp-server 1.2.1 → 1.2.2

package/dist/tools/designer/list-plugins.d.ts

@@ -0,0 +1,2 @@
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+export declare function registerDesignerListPlugins(server: McpServer): void;

package/dist/tools/designer/list-plugins.js

@@ -0,0 +1,141 @@
+import { z } from 'zod';
+import { resolve } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerDesignerListPlugins(server) {
+    server.registerTool('designer_list_plugins', {
+        title: 'List Designer Plugins',
+        description: `List the RESTForge Designer frontend plugins available in the current environment, by running restforge-designer plugins list. Each plugin defines a frontend tech stack / template the designer can generate against.
+
+USE WHEN:
+- The user asks which designer plugins are available, or wants the catalog of frontend templates
+- The user asks things like "plugin apa yang tersedia", "daftar plugin designer", "list frontend plugins", "what designer plugins do I have", "tampilkan plugin frontend", "which frontend templates can I use"
+- Before initialising a project or generating frontend code, to choose which plugin to target
+- The user mentions designer plugins generically and wants an overview
+
+DO NOT USE FOR:
+- Inspecting the metadata, schema, or fields of ONE specific plugin -> use 'designer_inspect_plugin'
+- Validating a UDF payload against a plugin -> use 'designer_validate_payload'
+- Previewing the files a payload would generate -> use 'designer_preview_files'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer plugins list [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI prints a table of available plugins (auto-detected, or from --plugins-dir when supplied). It does not modify any file and does not require a license.
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "list the available plugins", "inspect a plugin", "generate the frontend code").
+- Speak in plain language. Summarise the plugins (names, count); do not paste raw CLI output unless the user explicitly asks.
+- When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the working directory where the binary is run'),
+            pluginsDir: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Override path to the plugins folder. When omitted, the binary auto-detects the plugins directory.'),
+        },
+        annotations: {
+            title: 'List Designer Plugins',
+            readOnlyHint: true,
+            idempotentHint: true,
+        },
+    }, async ({ cwd, pluginsDir }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: the restforge-designer binary must be reachable on PATH.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        const probe = await execProcess('restforge-designer', ['--version'], {
+            cwd: projectCwd,
+            timeout: 10_000,
+        });
+        if (!probe.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the available plugins can be listed.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+- Once it is installed, retry listing the plugins.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Forward only the arguments the user supplied. per §3.5 / D6
+        const args = ['plugins', 'list'];
+        if (pluginsDir)
+            args.push(`--plugins-dir=${pluginsDir}`);
+        const result = await execProcess('restforge-designer', args, {
+            cwd: projectCwd,
+            timeout: 15_000,
+        });
+        // D7: read-only tool. Pre-flight confirmed the binary spawns, so only an
+        // unexpected crash/timeout (no real exit code -> -1) is a real error.
+        if (result.exitCode === -1) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Listing Designer plugins did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+
+--- stderr ---
+${result.stderr}
+--- end stderr ---
+
+For the assistant:
+- The Designer CLI did not finish (likely a crash or timeout), so there is no plugin list to report.
+- Tell the user the list could not be retrieved and offer to retry. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4 — unexpected crash/timeout
+            };
+        }
+        // D7: single response for ANY real exit code. A non-zero exit is an actionable
+        // negative verdict (e.g. plugins directory not found) to relay, not a failure.
+        const stderrBlock = result.stderr
+            ? `\n--- stderr ---\n${result.stderr}\n--- end stderr ---\n`
+            : '';
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Listing Designer plugins ran.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The Designer CLI ran to completion. Read the CLI output above and classify the result:
+  (a) Positive result — the output is a table of available plugins. Summarise the plugins in plain language (names and how many) and, if the user is choosing one, suggest inspecting a specific plugin for its details.
+  (b) Actionable negative verdict — no plugins were found, or the plugins directory override could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Explain the situation (e.g. the plugins folder is empty or the override path is wrong) and offer next steps.
+- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
+- Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=list-plugins.js.map

package/dist/tools/designer/list-plugins.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"list-plugins.js","sourceRoot":"","sources":["../../../src/tools/designer/list-plugins.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEpC,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,2BAA2B,CAAC,MAAiB;IAC3D,MAAM,CAAC,YAAY,CACjB,uBAAuB,EACvB;QACE,KAAK,EAAE,uBAAuB;QAC9B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;uGAwBoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,UAAU,EAAE,CAAC;iBACV,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,mGAAmG,CAAC;SACjH;QACD,WAAW,EAAE;YACX,KAAK,EAAE,uBAAuB;YAC9B,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,UAAU,EAAE,EAAE,EAAE;QAC5B,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+EAA+E;QAC/E,oEAAoE;QACpE,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,CAAC,WAAW,CAAC,EAAE;YACnE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QACH,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC;YACnB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;eAChB,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;mDAKwB;qBACtC;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,MAAM,CAAC,CAAC;QACjC,IAAI,UAAU;YAAE,IAAI,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAEzD,MAAM,MAAM,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,IAAI,EAAE;YAC3D,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QAEH,yEAAyE;QACzE,sEAAsE;QACtE,IAAI,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,EAAE,CAAC;YAC3B,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;eAChB,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;wGAKyF;qBAC3F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,+EAA+E;QAC/E,+EAA+E;QAC/E,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;YAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;YAC5D,CAAC,CAAC,EAAE,CAAC;QACP,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;qBAEG,UAAU;eAChB,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;kIAMqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/designer/preview-files.d.ts

@@ -0,0 +1,2 @@
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+export declare function registerDesignerPreviewFiles(server: McpServer): void;

package/dist/tools/designer/preview-files.js

@@ -0,0 +1,150 @@
+import { z } from 'zod';
+import { resolve } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerDesignerPreviewFiles(server) {
+    server.registerTool('designer_preview_files', {
+        title: 'Preview Designer Files',
+        description: `Preview (dry-run) the frontend files that the RESTForge Designer would generate from a UI Definition File (UDF) payload, by running restforge-designer preview. This lists what would be produced WITHOUT writing anything to disk.
+
+USE WHEN:
+- The user asks which files would be generated, or wants a dry-run before generating frontend code
+- The user asks things like "file apa yang akan di-generate", "preview output frontend designer", "dry-run generate", "what files will the designer produce", "tunjukkan hasil generate tanpa menulis file", "preview the designer output"
+- Before actually generating the frontend code, to inspect the planned output and confirm it looks right
+- The user mentions a designer/frontend UDF payload and wants to see the resulting file layout first
+
+DO NOT USE FOR:
+- Validating that a UDF payload is structurally correct against the plugin schema -> use 'designer_validate_payload'
+- Actually generating and writing the frontend files (preview is read-only; the real generation tool writes files)
+- Listing the available designer plugins -> use 'designer_list_plugins'
+- Inspecting one plugin's metadata -> use 'designer_inspect_plugin'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer preview --payload=<payload> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI reads the UDF payload JSON, resolves the target plugin (auto-detected or from --plugins-dir), and prints the list of files it would generate. It does not modify any file and does not require a license.
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "preview the generated files", "validate the UI definition", "generate the frontend code").
+- Speak in plain language. Summarise the planned file list; do not paste raw CLI output unless the user explicitly asks.
+- When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the working directory where the binary is run'),
+            payload: z
+                .string()
+                .min(1)
+                .describe('Path to the UDF payload JSON file (relative to cwd or absolute)'),
+            pluginsDir: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Override path to the plugins folder. When omitted, the binary auto-detects the plugins directory.'),
+        },
+        annotations: {
+            title: 'Preview Designer Files',
+            readOnlyHint: true,
+            idempotentHint: true,
+        },
+    }, async ({ cwd, payload, pluginsDir }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: the restforge-designer binary must be reachable on PATH.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        const probe = await execProcess('restforge-designer', ['--version'], {
+            cwd: projectCwd,
+            timeout: 10_000,
+        });
+        if (!probe.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the generated files can be previewed.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+- Once it is installed, retry the preview.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Forward only the arguments the user supplied. per §3.5 / D6
+        const args = ['preview', `--payload=${payload}`];
+        if (pluginsDir)
+            args.push(`--plugins-dir=${pluginsDir}`);
+        const result = await execProcess('restforge-designer', args, {
+            cwd: projectCwd,
+            timeout: 30_000,
+        });
+        // D7: read-only tool. Pre-flight confirmed the binary spawns, so only an
+        // unexpected crash/timeout (no real exit code -> -1) is a real error.
+        if (result.exitCode === -1) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Designer preview did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+
+--- stderr ---
+${result.stderr}
+--- end stderr ---
+
+For the assistant:
+- The Designer CLI did not finish (likely a crash or timeout), so there is no preview to report.
+- Tell the user the preview could not be completed and offer to retry. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4 — unexpected crash/timeout
+            };
+        }
+        // D7: single response for ANY real exit code. A non-zero exit is an actionable
+        // negative verdict (invalid payload, plugin/file not found) to relay, not a failure.
+        const stderrBlock = result.stderr
+            ? `\n--- stderr ---\n${result.stderr}\n--- end stderr ---\n`
+            : '';
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Designer preview ran.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The Designer CLI ran to completion. Read the CLI output above and classify the result:
+  (a) Positive result — the output lists the files that would be generated. Summarise the planned files in plain language (how many, what kinds) and offer the next step: generate the frontend code for real.
+  (b) Actionable negative verdict — the payload is invalid, the payload file was not found, or the target plugin / plugins directory could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Summarise the concrete problem (which path or field is wrong) and offer to retry after the user fixes it; validating the payload first can help pinpoint structural errors.
+- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
+- Soft note: if preview fails with an appConfig/plugin error (e.g. the plugin or app config "not found") while the SAME payload passes validation, the payload may rely on 'extends' / 'include' references that preview does not appear to merge the way validation does. As a possible workaround, suggest pointing the preview at a self-contained payload (inline appConfig and pages) or an already-merged file. This is a tentative hint, not a guaranteed rule — do not state it as certain or tie it to a specific version.
+- Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=preview-files.js.map

package/dist/tools/designer/preview-files.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"preview-files.js","sourceRoot":"","sources":["../../../src/tools/designer/preview-files.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEpC,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,4BAA4B,CAAC,MAAiB;IAC5D,MAAM,CAAC,YAAY,CACjB,wBAAwB,EACxB;QACE,KAAK,EAAE,wBAAwB;QAC/B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;uGAyBoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,OAAO,EAAE,CAAC;iBACP,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,iEAAiE,CAAC;YAC9E,UAAU,EAAE,CAAC;iBACV,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,mGAAmG,CAAC;SACjH;QACD,WAAW,EAAE;YACX,KAAK,EAAE,wBAAwB;YAC/B,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,OAAO,EAAE,UAAU,EAAE,EAAE,EAAE;QACrC,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+EAA+E;QAC/E,oEAAoE;QACpE,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,CAAC,WAAW,CAAC,EAAE;YACnE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QACH,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC;YACnB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;2CAKgB;qBAC9B;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,aAAa,OAAO,EAAE,CAAC,CAAC;QACjD,IAAI,UAAU;YAAE,IAAI,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAEzD,MAAM,MAAM,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,IAAI,EAAE;YAC3D,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QAEH,yEAAyE;QACzE,sEAAsE;QACtE,IAAI,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,EAAE,CAAC;YAC3B,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;2GAK4F;qBAC9F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,+EAA+E;QAC/E,qFAAqF;QACrF,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;YAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;YAC5D,CAAC,CAAC,EAAE,CAAC;QACP,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;qBAEG,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;;kIAOqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/designer/scaffold-plugin.d.ts

@@ -0,0 +1,2 @@
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+export declare function registerDesignerScaffoldPlugin(server: McpServer): void;

package/dist/tools/designer/scaffold-plugin.js

@@ -0,0 +1,162 @@
+import { z } from 'zod';
+import { resolve } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerDesignerScaffoldPlugin(server) {
+    server.registerTool('designer_scaffold_plugin', {
+        title: 'Scaffold Designer Plugin',
+        description: `Scaffold a new custom RESTForge Designer frontend plugin from a template, by running restforge-designer plugins scaffold. This WRITES a new plugin folder to disk that the user can then customise.
+
+USE WHEN:
+- The user asks to create a new custom designer/frontend plugin from scratch
+- The user asks things like "buat plugin custom baru", "scaffold folder plugin designer", "mulai plugin frontend dari template", "create a new designer plugin", "scaffold a frontend plugin", "bikin plugin frontend baru"
+- The user wants a starter plugin folder they can edit to build their own frontend generator template
+- The user names a new plugin id and wants the folder structure generated for it
+
+DO NOT USE FOR:
+- Generating a frontend application from a UDF payload -> use 'designer_generate'
+- Initialising a project from an existing plugin -> use 'designer_init_project'
+- Listing the available plugins -> use 'designer_list_plugins'
+- Inspecting one existing plugin's metadata -> use 'designer_inspect_plugin'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer plugins scaffold --id=<id> --output=<output> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI creates a new plugin folder named after the given id under the output directory. It does NOT require a license (scaffolding is license-free).
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "scaffold a new plugin", "list the available plugins", "generate the frontend code").
+- Speak in plain language. Confirm what was created and where; do not paste raw CLI output unless the user explicitly asks.
+- When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the working directory where the binary is run'),
+            id: z
+                .string()
+                .min(1)
+                .describe('The id of the new plugin to scaffold (e.g. my-custom-plugin)'),
+            output: z
+                .string()
+                .min(1)
+                .describe('Path to the output folder where the new plugin will be created (relative to cwd or absolute)'),
+            pluginsDir: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Override path to the plugins folder. When omitted, the binary auto-detects the plugins directory.'),
+        },
+        annotations: {
+            title: 'Scaffold Designer Plugin',
+            destructiveHint: false, // creates a new plugin folder; does not delete or overwrite existing data
+            idempotentHint: false, // each call attempts to create a new plugin folder
+        },
+    }, async ({ cwd, id, output, pluginsDir }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: the restforge-designer binary must be reachable on PATH.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        const probe = await execProcess('restforge-designer', ['--version'], {
+            cwd: projectCwd,
+            timeout: 10_000,
+        });
+        if (!probe.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before a plugin can be scaffolded.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+- Once it is installed, retry scaffolding the plugin.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Forward only the arguments the user supplied. Required flags are always sent. per §3.5 / D6
+        const args = ['plugins', 'scaffold', `--id=${id}`, `--output=${output}`];
+        if (pluginsDir)
+            args.push(`--plugins-dir=${pluginsDir}`);
+        const result = await execProcess('restforge-designer', args, {
+            cwd: projectCwd,
+            timeout: 30_000,
+        });
+        // D9: write tool. A non-zero exit (incl. -1 crash/timeout) means the write did
+        // not complete cleanly — the plugin folder may be missing or partial, so the
+        // model needs to recover -> isError: true.
+        if (result.exitCode !== 0) {
+            const stderrBlock = result.stderr
+                ? `\n--- stderr ---\n${result.stderr}\n--- end stderr ---\n`
+                : '';
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Scaffolding the Designer plugin did not complete.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The scaffold did not finish successfully, so the plugin folder may not exist or may be partial. Read the CLI output above and explain the most likely cause to the user in plain language. Common causes:
+  * The output directory already exists or is not writable — suggest a different output path or clearing the existing folder.
+  * The plugin id is invalid (bad characters) — suggest a simpler id.
+  * Exit code -1 — the command crashed or timed out; offer to retry.
+- Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
+                    },
+                ],
+                isError: true, // per §3.4 / D9 — write did not complete
+            };
+        }
+        // D9: success — exit 0. Labeled facts + fenced raw output per §3.5.
+        const stderrBlock = result.stderr
+            ? `\n--- stderr ---\n${result.stderr}\n--- end stderr ---\n`
+            : '';
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Designer plugin scaffolded successfully.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- Confirm to the user that the new plugin folder was created. Mention the plugin id and the output location in plain language.
+- The scaffold is a starting point: the user will edit the generated plugin files (templates, schema) to build their own frontend generator.
+- Suggest a sensible next step, e.g. inspecting or listing the plugins to confirm the new one is picked up, or authoring a UDF payload that targets it.
+- Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=scaffold-plugin.js.map

package/dist/tools/designer/scaffold-plugin.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"scaffold-plugin.js","sourceRoot":"","sources":["../../../src/tools/designer/scaffold-plugin.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEpC,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,8BAA8B,CAAC,MAAiB;IAC9D,MAAM,CAAC,YAAY,CACjB,0BAA0B,EAC1B;QACE,KAAK,EAAE,0BAA0B;QACjC,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;uGAyBoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,EAAE,EAAE,CAAC;iBACF,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,8DAA8D,CAAC;YAC3E,MAAM,EAAE,CAAC;iBACN,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,8FAA8F,CAAC;YAC3G,UAAU,EAAE,CAAC;iBACV,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,mGAAmG,CAAC;SACjH;QACD,WAAW,EAAE;YACX,KAAK,EAAE,0BAA0B;YACjC,eAAe,EAAE,KAAK,EAAE,0EAA0E;YAClG,cAAc,EAAE,KAAK,EAAG,mDAAmD;SAC5E;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,EAAE,EAAE,MAAM,EAAE,UAAU,EAAE,EAAE,EAAE;QACxC,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+EAA+E;QAC/E,oEAAoE;QACpE,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,CAAC,WAAW,CAAC,EAAE;YACnE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QACH,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC;YACnB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;aAClB,EAAE;UACL,MAAM;eACD,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;sDAK2B;qBACzC;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8FAA8F;QAC9F,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,UAAU,EAAE,QAAQ,EAAE,EAAE,EAAE,YAAY,MAAM,EAAE,CAAC,CAAC;QACzE,IAAI,UAAU;YAAE,IAAI,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAEzD,MAAM,MAAM,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,IAAI,EAAE;YAC3D,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QAEH,+EAA+E;QAC/E,6EAA6E;QAC7E,2CAA2C;QAC3C,IAAI,MAAM,CAAC,QAAQ,KAAK,CAAC,EAAE,CAAC;YAC1B,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;gBAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;gBAC5D,CAAC,CAAC,EAAE,CAAC;YACP,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;aAClB,EAAE;UACL,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;kIAMqH;qBACrH;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,yCAAyC;aACzD,CAAC;QACJ,CAAC;QAED,oEAAoE;QACpE,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;YAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;YAC5D,CAAC,CAAC,EAAE,CAAC;QACP,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;qBAEG,UAAU;aAClB,EAAE;UACL,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;kIAKqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/designer/validate-payload.d.ts

@@ -0,0 +1,2 @@
+import type { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+export declare function registerDesignerValidatePayload(server: McpServer): void;

package/dist/tools/designer/validate-payload.js

@@ -0,0 +1,158 @@
+import { z } from 'zod';
+import { resolve } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerDesignerValidatePayload(server) {
+    server.registerTool('designer_validate_payload', {
+        title: 'Validate Designer Payload',
+        description: `Validate a frontend UI Definition File (UDF) payload against the schema of the RESTForge Designer plugin it targets, by running restforge-designer validate.
+
+USE WHEN:
+- The user asks to validate, check, or verify a frontend designer payload / UI definition (UDF) file
+- The user asks things like "validasi UDF", "cek payload frontend", "is this UI definition valid", "validate designer payload", "apakah payload UDF benar", "check the frontend payload against the plugin schema"
+- Before previewing or generating frontend code from a UDF, to confirm the payload is structurally valid against the plugin schema
+- The user mentions a designer/frontend payload JSON and wants to know whether it conforms to the plugin it targets
+- Routine pre-generation sanity check on a UDF file
+
+DO NOT USE FOR:
+- Validating a backend RDF payload against the database schema -> use 'codegen_validate_payload'
+- Validating an SDF (database schema definition) -> use 'codegen_dbschema_validate'
+- Validating raw SQL -> use 'codegen_validate_sql'
+- Generating the frontend code itself (this only validates, it does not write files)
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer validate --payload=<payload> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI reads the UDF payload JSON, resolves the target plugin (auto-detected or from --plugins-dir), and reports whether
+the payload is valid against that plugin's schema, listing structural errors when it is not. It does not modify any file and
+does not require a license.
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "validate the UI definition", "preview the generated files", "generate the frontend code").
+- Speak in plain language. Summarise the result; do not paste raw CLI output unless the user explicitly asks.
+- When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the working directory where the binary is run'),
+            payload: z
+                .string()
+                .min(1)
+                .describe('Path to the UDF payload JSON file (relative to cwd or absolute)'),
+            pluginsDir: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Override path to the plugins folder. When omitted, the binary auto-detects the plugins directory.'),
+        },
+        annotations: {
+            title: 'Validate Designer Payload',
+            readOnlyHint: true,
+            idempotentHint: true,
+        },
+    }, async ({ cwd, payload, pluginsDir }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: the restforge-designer binary must be reachable on PATH.
+        // Treated as a non-error precondition per the authoring guide §3.4. The probe
+        // distinguishes "binary missing" (precondition) from "binary ran and reported
+        // something" (which falls through to the real execution below).
+        const probe = await execProcess('restforge-designer', ['--version'], {
+            cwd: projectCwd,
+            timeout: 10_000,
+        });
+        if (!probe.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before a frontend payload can be validated.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+- Once it is installed, retry validating the payload.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Forward only the arguments the user supplied. The plugins directory is
+        // auto-detected by the binary when --plugins-dir is omitted. per §3.5
+        const args = ['validate', `--payload=${payload}`];
+        if (pluginsDir)
+            args.push(`--plugins-dir=${pluginsDir}`);
+        const result = await execProcess('restforge-designer', args, {
+            cwd: projectCwd,
+            timeout: 30_000,
+        });
+        // D7: this is a read-only tool. The pre-flight already confirmed the binary
+        // spawns, so an unexpected crash/timeout (no real exit code -> -1) is the only
+        // real error here -> isError: true. Any genuine exit code is a verdict to relay.
+        if (result.exitCode === -1) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Designer payload validation did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+
+--- stderr ---
+${result.stderr}
+--- end stderr ---
+
+For the assistant:
+- The Designer CLI did not finish (likely a crash or timeout), so there is no validation verdict to report.
+- Tell the user the check could not be completed and offer to retry. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4 — unexpected crash/timeout
+            };
+        }
+        // D7: single response for ANY real exit code (success branch no longer split on
+        // result.success). A non-zero exit means the CLI reported an actionable negative
+        // verdict (invalid payload, plugin/file not found), which is a legitimate result
+        // to relay — NOT a tool failure. The model classifies from the fenced output.
+        const stderrBlock = result.stderr
+            ? `\n--- stderr ---\n${result.stderr}\n--- end stderr ---\n`
+            : '';
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Designer payload validation ran.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The Designer CLI ran to completion. Read the CLI output above and classify the result:
+  (a) Positive result — the payload is VALID against the target plugin schema. Confirm this in plain language and suggest the next step: preview the files that would be generated from this payload, or generate the frontend code. Describe steps by what they do.
+  (b) Actionable negative verdict — the payload is INVALID (the output lists structural errors), or the payload file was not found, or the target plugin / plugins directory could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Summarise the concrete problems (which fields, components, or paths are wrong) and offer to re-check after the user fixes them.
+- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
+- Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=validate-payload.js.map