@restforgejs/mcp-server 1.2.0

package/dist/tools/codegen/generate-payload.js

@@ -0,0 +1,145 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerCodegenGeneratePayload(server) {
+    server.registerTool('codegen_generate_payload', {
+        title: 'Generate Payload',
+        description: `Generate a payload spec file (metadata, fields, action specs) from a database table by introspecting its schema via restforge.
+
+USE WHEN:
+- The user asks to generate a payload, payload spec, or payload metadata file from a database table
+- The user asks things like "buatkan payload dari table X", "generate payload guest_book", "scan schema table to JSON", "create payload for endpoint generation"
+- The user wants to "introspect" or "scan" a database table into a JSON spec
+- Starting CLI codegen workflow after the project config has been validated
+- Re-generating payload after a schema change in the database
+
+DO NOT USE FOR:
+- Filling in credentials in db-connection.env -> use 'setup_write_env'
+- Validating config before generating payload -> use 'setup_validate_config'
+- Creating the project / endpoint code from a payload -> that is the next CLI step (will be wrapped in a future tool, not yet available)
+
+This tool runs: npx restforge payload --table=<table> --config=<config> in the given cwd.
+The CLI connects to the database described in the config file, reads the table schema,
+and writes a payload JSON file (e.g. table 'guest_book' -> 'guest-book.json' with underscore
+mapped to hyphen). The payload file is the input for the next codegen step (project + endpoint creation).
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The config file (default 'db-connection.env') must exist in the project and contain valid
+  database credentials. This tool does not pre-check that — if the CLI fails, the failure response
+  will surface the underlying cause.
+
+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. "install the package", "fill in the credentials", "generate the payload").
+- 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 project folder (must contain node_modules/@restforgejs/platform and the config file)'),
+            table: z
+                .string()
+                .min(1)
+                .describe('Name of the database table to introspect (e.g. guest_book)'),
+            config: z
+                .string()
+                .min(1)
+                .default('db-connection.env')
+                .describe('Config file name (relative to project) used by the CLI to connect to the database'),
+        },
+        annotations: {
+            title: 'Generate Payload',
+            readOnlyHint: false,
+            idempotentHint: false,
+        },
+    }, async ({ cwd, table, config }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: @restforgejs/platform must be present in node_modules.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        try {
+            await access(join(projectCwd, 'node_modules', '@restforgejs', 'platform'));
+        }
+        catch {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge package is not installed in this project.
+
+Project path: ${projectCwd}
+Expected location: node_modules/@restforgejs/platform
+Requested table: ${table}
+Requested config: ${config}
+
+For the assistant:
+- The user needs to install the RESTForge package before a payload can be generated from a table schema.
+- Use the appropriate package-installation tool to do this, then retry generating the payload.
+- When explaining to the user, say something like "the RESTForge package isn't installed yet — should I install it first?". Do not mention internal tool names.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        const result = await execProcess('npx', ['restforge', 'payload', 'generate', `--table=${table}`, `--config=${config}`], { cwd: projectCwd, timeout: 30_000 });
+        // CLI failure: real error per §3.4; structured per §3.5.
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to generate payload.
+
+Project path: ${projectCwd}
+Table: ${table}
+Config: ${config}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- CLI output ---
+stdout:
+${result.stdout}
+
+stderr:
+${result.stderr}
+--- end CLI output ---
+
+For the assistant:
+- Tell the user that generating the payload did not complete successfully.
+- Summarise the likely cause from the CLI output in plain language (common causes: the config file is missing or has incomplete credentials, the database is unreachable, or the requested table does not exist in the database). Do not paste the raw stdout/stderr unless the user explicitly asks.
+- Offer to retry once the underlying issue is resolved. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Success: one-line summary + labeled facts + fenced raw output per §3.5.
+        // The CLI itself prints the output filename in stdout; we do not try to re-derive it here.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Payload generated successfully.
+
+Project path: ${projectCwd}
+Table: ${table}
+Config: ${config}
+Output: payload file generated by restforge (see CLI output below for the exact filename; underscores in the table name are mapped to hyphens, e.g. 'guest_book' -> 'guest-book.json').
+
+--- CLI output ---
+${result.stdout}
+--- end CLI output ---
+
+For the assistant:
+- Confirm to the user that the payload spec for the requested table is ready.
+- Mention in plain language that the payload is the input for the next codegen step (generating the project and endpoint code from this payload). That follow-up step is part of the CLI workflow but is not wrapped as a tool yet.
+- Suggest that the user can review or edit the generated payload file before the next step.
+- Keep the reply concise. Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=generate-payload.js.map

package/dist/tools/codegen/generate-payload.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"generate-payload.js","sourceRoot":"","sources":["../../../src/tools/codegen/generate-payload.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAC1C,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAE1C,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,8BAA8B,CAAC,MAAiB;IAC9D,MAAM,CAAC,YAAY,CACjB,0BAA0B,EAC1B;QACE,KAAK,EAAE,kBAAkB;QACzB,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uGA6BoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,2GAA2G,CAAC;YACxH,KAAK,EAAE,CAAC;iBACL,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,4DAA4D,CAAC;YACzE,MAAM,EAAE,CAAC;iBACN,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,OAAO,CAAC,mBAAmB,CAAC;iBAC5B,QAAQ,CAAC,mFAAmF,CAAC;SACjG;QACD,WAAW,EAAE;YACX,KAAK,EAAE,kBAAkB;YACzB,YAAY,EAAE,KAAK;YACnB,cAAc,EAAE,KAAK;SACtB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,KAAK,EAAE,MAAM,EAAE,EAAE,EAAE;QAC/B,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,6EAA6E;QAC7E,oEAAoE;QACpE,IAAI,CAAC;YACH,MAAM,MAAM,CAAC,IAAI,CAAC,UAAU,EAAE,cAAc,EAAE,cAAc,EAAE,UAAU,CAAC,CAAC,CAAC;QAC7E,CAAC;QAAC,MAAM,CAAC;YACP,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;;mBAEP,KAAK;oBACJ,MAAM;;;;;gKAKsI;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,MAAM,MAAM,GAAG,MAAM,WAAW,CAC9B,KAAK,EACL,CAAC,WAAW,EAAE,SAAS,EAAE,UAAU,EAAE,WAAW,KAAK,EAAE,EAAE,YAAY,MAAM,EAAE,CAAC,EAC9E,EAAE,GAAG,EAAE,UAAU,EAAE,OAAO,EAAE,MAAM,EAAE,CACrC,CAAC;QAEF,yDAAyD;QACzD,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;SACjB,KAAK;UACJ,MAAM;WACL,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;4FAM6E;qBAC/E;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,0EAA0E;QAC1E,2FAA2F;QAC3F,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;SACjB,KAAK;UACJ,MAAM;;;;EAId,MAAM,CAAC,MAAM;;;;;;;+HAOgH;iBACpH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/get-dashboard-catalog.d.ts

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

package/dist/tools/codegen/get-dashboard-catalog.js

@@ -0,0 +1,213 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerCodegenGetDashboardCatalog(server) {
+    server.registerTool('codegen_get_dashboard_catalog', {
+        title: 'Get Dashboard Catalog',
+        description: `Get authoritative JSON catalog of dashboard payload spec (payload shape with discriminator, widget structure with mutex \`query\`/\`queries\`, params contract with allowed types, scalar collapse rules, naming convention with \`dash-\` prefix, URL pattern \`POST /api/{project}/{name}/dashboard\`, file reference convention, placeholder convention with \`:paramName\`).
+
+USE WHEN:
+- The user asks about dashboard payload structure, widget definition, or how dashboard endpoints work
+- The user mentions specific dashboard concepts: \`widgets\`, \`params\`, \`query\` vs \`queries\`, scalar collapse, dashboard prefix \`dash-\`
+- Pertanyaan dalam bentuk seperti "bagaimana struktur payload dashboard", "apa beda dashboard dengan endpoint biasa", "kapan pakai query vs queries", "kenapa nama dashboard harus pakai dash-"
+- The user asks about the URL pattern for dashboard endpoints (\`POST /api/{project}/{name}/dashboard\`)
+- The user asks why dashboard names must start with \`dash-\` prefix
+- The user asks about response shape: when is value a scalar, when is it object, when is it array (scalar collapse rules)
+- The user asks about placeholder \`:paramName\` in widget SQL — declaration requirements, escaping (\`::\` Postgres cast)
+- Before authoring a dashboard payload manually (via Write tool) — to ground field naming, allowed/forbidden fields, widget structure
+- Before invoking 'codegen_validate_dashboard_payload' or 'codegen_create_dashboard' — to verify payload conforms to schema
+- The user is unsure whether their use case is a dashboard or a CRUD endpoint
+
+DO NOT USE FOR:
+- Validating an actual dashboard payload file -> use 'codegen_validate_dashboard_payload'
+- Generating a dashboard module from a payload -> use 'codegen_create_dashboard'
+- Looking up CRUD payload field validation rules -> use 'codegen_get_field_validation_catalog'
+- Looking up CRUD query declarative spec (\`datatablesQuery\`, \`viewQuery\`, \`viewName\`, \`exportQuery\`, \`detailQuery\`) -> use 'codegen_get_query_declarative_catalog'
+- Generating a CRUD payload from a database table -> use 'codegen_generate_payload'
+- Validating CRUD payload drift against the database -> use 'codegen_validate_payload'
+- Common widget patterns examples (Metric+Donut, Metric+Sparkline, Metric+Goal) — not in catalog scope; refer to the documentationUrl returned in the response
+- Frontend integration examples (Metronic, AdminLTE, etc.) — not in catalog scope; refer to documentationUrl
+- Separation of Concerns rationale for forbidden frontend fields — not in catalog scope; refer to documentationUrl
+- Multi-database SQL dialect adaptation inside widget queries — not in catalog scope; refer to documentationUrl
+- Performance characteristics (Promise.allSettled execution, in-memory SQL embedding) — not in catalog scope; refer to documentationUrl
+
+This tool runs: npx restforge dashboard:catalog in the given cwd.
+The catalog is sourced from restforge (single source of truth) so it stays in sync with
+the restforge runtime version installed in the project.
+
+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. "look up the dashboard catalog", "edit the dashboard payload", "install the package").
+- Speak in plain language. Summarise the catalog (number of allowed top-level fields, forbidden frontend fields, param types, scalar collapse rules); do not paste the entire JSON unless the user explicitly asks for it.
+- When the user is unsure whether their use case is dashboard or CRUD, briefly explain the discriminator: \`widgets\` array means dashboard (multi-query aggregator), \`tableName\` means CRUD (single-table REST endpoint). They cannot mix.
+- When a precondition is not met (e.g. the package is not installed), frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the project folder (must contain node_modules/@restforgejs/platform)'),
+        },
+        annotations: {
+            title: 'Get Dashboard Catalog',
+            readOnlyHint: true,
+            idempotentHint: true,
+        },
+    }, async ({ cwd }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: @restforgejs/platform must be installed before this CLI command can run.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        try {
+            await access(join(projectCwd, 'node_modules', '@restforgejs', 'platform'));
+        }
+        catch {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge package is not installed in this project.
+
+Project path: ${projectCwd}
+Expected location: node_modules/@restforgejs/platform
+
+For the assistant:
+- The dashboard catalog can only be retrieved once the RESTForge package is installed locally.
+- Suggest installing the package first, then retry getting the catalog.
+- When explaining to the user, say something like "the RESTForge package isn't installed yet — should I install it first?". Do not mention internal tool names.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Run subprocess with NODE_ENV=production to suppress legacy banner output
+        // (mirrors the pattern used by setup_get_config_schema and other catalog tools).
+        const result = await execProcess('npx', ['restforge', 'catalog', 'dashboard'], {
+            cwd: projectCwd,
+            timeout: 15_000,
+            env: { NODE_ENV: 'production' },
+            stripFinalNewline: true,
+        });
+        // CLI failure: real error per §3.4; structured per §3.5.
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to retrieve the dashboard catalog.
+
+Project path: ${projectCwd}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- CLI output ---
+stdout:
+${result.stdout}
+
+stderr:
+${result.stderr}
+--- end CLI output ---
+
+For the assistant:
+- Tell the user that the dashboard catalog could not be retrieved.
+- A common cause is an older RESTForge version that does not yet expose this command. If the CLI output mentions an unknown command, suggest upgrading the package as a likely fix.
+- Do not paste the raw stdout/stderr unless the user explicitly asks. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Validate JSON output. Parse failure is a real error per §3.4 (CLI succeeded but produced invalid output).
+        let parsed;
+        try {
+            parsed = JSON.parse(result.stdout);
+        }
+        catch (err) {
+            const msg = err instanceof Error ? err.message : String(err);
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to parse dashboard catalog JSON.
+
+Project path: ${projectCwd}
+Reason: ${msg}
+
+--- Raw stdout ---
+${result.stdout}
+--- end Raw stdout ---
+
+For the assistant:
+- The CLI returned output that is not valid JSON.
+- Summarise this to the user in plain language; do not paste the raw stdout unless they explicitly ask.
+- Suggest checking that the installed package version is compatible. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Extract summary counts for labeled facts. Use defensive access — if the catalog shape
+        // changes upstream, we still produce a sensible response rather than crash.
+        const root = (parsed ?? {});
+        const summary = (root.summary ?? {});
+        const totalAllowedTopLevelFields = typeof summary.totalAllowedTopLevelFields === 'number'
+            ? summary.totalAllowedTopLevelFields
+            : 'unknown';
+        const totalForbiddenFrontendFields = typeof summary.totalForbiddenFrontendFields === 'number'
+            ? summary.totalForbiddenFrontendFields
+            : 'unknown';
+        const totalParamTypes = typeof summary.totalParamTypes === 'number' ? summary.totalParamTypes : 'unknown';
+        const totalScalarCollapseRules = typeof summary.totalScalarCollapseRules === 'number'
+            ? summary.totalScalarCollapseRules
+            : 'unknown';
+        const sourceLabel = typeof root.source === 'string' ? root.source : 'dashboard-catalog';
+        // Re-stringify for consistent pretty formatting (independent of CLI --pretty flag).
+        const prettyJson = JSON.stringify(parsed, null, 2);
+        // Success: one-line summary + labeled facts + fenced JSON output per §3.5.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Dashboard catalog retrieved successfully.
+
+Project path: ${projectCwd}
+Source: restforge (${sourceLabel}) — single source of truth for the installed runtime version
+totalAllowedTopLevelFields: ${totalAllowedTopLevelFields}
+totalForbiddenFrontendFields: ${totalForbiddenFrontendFields}
+totalParamTypes: ${totalParamTypes}
+totalScalarCollapseRules: ${totalScalarCollapseRules}
+
+--- Dashboard Catalog (JSON) ---
+${prettyJson}
+--- end Dashboard Catalog (JSON) ---
+
+For the assistant:
+- Confirm to the user that the catalog is available. Summarise in plain language: how many allowed top-level fields, forbidden frontend fields, param types, and scalar collapse rules are included.
+- Do not paste the full JSON block unless the user explicitly asks for it. If the user only asked to "see the catalog", offer to drill into a specific aspect (widget structure, params contract, naming convention, scalar collapse rules) instead of dumping everything.
+- Use this catalog as ground truth when the user is:
+  * Asking "how is a dashboard payload structured?"
+  * Authoring a dashboard payload manually (via the Write tool)
+  * Confused between dashboard payload (\`widgets\`) and CRUD payload (\`tableName\`)
+  * Asking about the \`dash-\` prefix in dashboard names
+  * Asking when to use \`query\` vs \`queries\`
+  * Asking about response shape (scalar collapse rules)
+  * Asking about \`:paramName\` placeholders in widget SQL
+- Filter notes for catalog consumers (avoid common pitfalls):
+  * \`payloadShape.discriminator\` is the way to tell whether a payload is a dashboard or a CRUD endpoint. \`widgets\` present means dashboard. \`tableName\` present means CRUD. A payload with both is rejected by the validator.
+  * \`widgetSpec.exclusiveQueryFields\` is a mutex rule: every widget MUST declare exactly one of \`query\` (singular, response always wraps as \`{ items: [...] }\`) OR \`queries\` (object, per-key shape determined by scalar collapse rules). Both or neither is rejected.
+  * \`paramSpec.perEntryFields[0].allowedValues\` is a closed enum of four values: \`string\`, \`number\`, \`boolean\`, \`date\`. Other type strings are rejected by the validator.
+  * \`scalarCollapseRules\` apply ONLY to \`widget.queries.<key>\`. For \`widget.query\` (singular) the response is ALWAYS wrapped as \`{ items: [...] }\` regardless of SQL result shape.
+  * \`namingConvention.dashboardName.regex\` is \`^dash-[a-zA-Z0-9_-]+$\`. minLength is 6 because \`dash-\` is 5 characters and at least one suffix character is required.
+  * \`placeholderConvention.regex\` uses a negative lookbehind \`(?<!:):\` so Postgres cast syntax \`::\` is NOT scanned as a placeholder. Every placeholder used in widget SQL must be declared in the top-level \`params\` object, otherwise the validator rejects the payload.
+- Knowledge boundary — the catalog does NOT cover the following; refer the user to \`documentationUrl\` (in the response JSON) instead of fabricating from training data:
+  * Common widget patterns with concrete SQL examples (Metric+Donut, Metric+Sparkline, Metric+Goal).
+  * Frontend mapping examples — how the response is rendered in Metronic, AdminLTE, or other UI frameworks.
+  * Separation of Concerns rationale for the forbidden frontend fields (\`widgetType\`, \`layout\`, \`title\`, \`subtitle\`, \`color\`).
+  * Multi-database SQL dialect adaptation inside widget queries.
+  * Performance characteristics (Promise.allSettled execution, in-memory SQL embedding, zero disk I/O at request time).
+- Do not mention internal tool names.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=get-dashboard-catalog.js.map

package/dist/tools/codegen/get-dashboard-catalog.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get-dashboard-catalog.js","sourceRoot":"","sources":["../../../src/tools/codegen/get-dashboard-catalog.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAC1C,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAE1C,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,kCAAkC,CAAC,MAAiB;IAClE,MAAM,CAAC,YAAY,CACjB,+BAA+B,EAC/B;QACE,KAAK,EAAE,uBAAuB;QAC9B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2IAoCwH;QACrI,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,uFAAuF,CAAC;SACrG;QACD,WAAW,EAAE;YACX,KAAK,EAAE,uBAAuB;YAC9B,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,EAAE,EAAE;QAChB,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+FAA+F;QAC/F,oEAAoE;QACpE,IAAI,CAAC;YACH,MAAM,MAAM,CAAC,IAAI,CAAC,UAAU,EAAE,cAAc,EAAE,cAAc,EAAE,UAAU,CAAC,CAAC,CAAC;QAC7E,CAAC;QAAC,MAAM,CAAC;YACP,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;;;;;;gKAMsI;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,2EAA2E;QAC3E,iFAAiF;QACjF,MAAM,MAAM,GAAG,MAAM,WAAW,CAC9B,KAAK,EACL,CAAC,WAAW,EAAE,SAAS,EAAE,WAAW,CAAC,EACrC;YACE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;YACf,GAAG,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE;YAC/B,iBAAiB,EAAE,IAAI;SACxB,CACF,CAAC;QAEF,yDAAyD;QACzD,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;WACf,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;0GAM2F;qBAC7F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,4GAA4G;QAC5G,IAAI,MAAe,CAAC;QACpB,IAAI,CAAC;YACH,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;QACrC,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,MAAM,GAAG,GAAG,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC;YAC7D,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;UAChB,GAAG;;;EAGX,MAAM,CAAC,MAAM;;;;;;yGAM0F;qBAC5F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,wFAAwF;QACxF,4EAA4E;QAC5E,MAAM,IAAI,GAAG,CAAC,MAAM,IAAI,EAAE,CAA4B,CAAC;QACvD,MAAM,OAAO,GAAG,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAA4B,CAAC;QAChE,MAAM,0BAA0B,GAC9B,OAAO,OAAO,CAAC,0BAA0B,KAAK,QAAQ;YACpD,CAAC,CAAC,OAAO,CAAC,0BAA0B;YACpC,CAAC,CAAC,SAAS,CAAC;QAChB,MAAM,4BAA4B,GAChC,OAAO,OAAO,CAAC,4BAA4B,KAAK,QAAQ;YACtD,CAAC,CAAC,OAAO,CAAC,4BAA4B;YACtC,CAAC,CAAC,SAAS,CAAC;QAChB,MAAM,eAAe,GACnB,OAAO,OAAO,CAAC,eAAe,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,eAAe,CAAC,CAAC,CAAC,SAAS,CAAC;QACpF,MAAM,wBAAwB,GAC5B,OAAO,OAAO,CAAC,wBAAwB,KAAK,QAAQ;YAClD,CAAC,CAAC,OAAO,CAAC,wBAAwB;YAClC,CAAC,CAAC,SAAS,CAAC;QAChB,MAAM,WAAW,GAAG,OAAO,IAAI,CAAC,MAAM,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,mBAAmB,CAAC;QAExF,oFAAoF;QACpF,MAAM,UAAU,GAAG,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;QAEnD,2EAA2E;QAC3E,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;qBACL,WAAW;8BACF,0BAA0B;gCACxB,4BAA4B;mBACzC,eAAe;4BACN,wBAAwB;;;EAGlD,UAAU;;;;;;;;;;;;;;;;;;;;;;;;;;;sCA2B0B;iBAC3B;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/get-dbschema-catalog.d.ts

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

package/dist/tools/codegen/get-dbschema-catalog.js

@@ -0,0 +1,244 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerCodegenGetDbschemaCatalog(server) {
+    server.registerTool('codegen_get_dbschema_catalog', {
+        title: 'Get dbschema-kit Catalog',
+        description: `Get authoritative JSON catalog of the dbschema-kit defineModel API: defineModel options, field types (with modifier formats), constraints (standalone vs value-bearing), relation types (belongsTo, hasMany, hasOne), referential actions (cascade/restrict/setNull/noAction), check operations (in/gt/gte/lt/lte/eq/neq), shorthand syntax rules and examples, naming rules (table/constraint), and dialect support (postgres/mysql/oracle/sqlite). The catalog is the single source of truth for schema-as-code authoring.
+
+USE WHEN:
+- The user asks how to define a database schema with dbschema-kit, the factory function pattern, or the \`defineModel\` API
+- Pertanyaan dalam bentuk: "bagaimana sintaks defineModel", "apa saja field type yang didukung", "bagaimana cara declare foreign key di schema", "constraint apa saja yang ada di shorthand"
+- The user mentions dbschema-kit concepts: \`defineModel\`, factory function, shorthand syntax, \`belongsTo\`/\`hasMany\`/\`hasOne\`, \`pk\`/\`fk:\`/\`unique\`, \`checks\`, \`primaryKey\`, \`relations\`, \`referentialActions\`, \`onDelete\`/\`onUpdate\`
+- Before authoring a schema file (via Write/Edit tools) — to ground field types, constraint syntax, and relation declarations
+- Before invoking 'codegen_dbschema_init' or 'codegen_dbschema_validate' — to verify the planned approach matches the API
+- The user asks about referential actions: \`cascade\`, \`restrict\`, \`setNull\`, \`noAction\`
+- The user asks about check operations: \`in\`, \`gt\`, \`gte\`, \`lt\`, \`lte\`, \`eq\`, \`neq\`
+- The user asks about audit columns: \`created_at\`, \`created_by\`, \`updated_at\`, \`updated_by\` — the 4-column RESTForge convention shared between SDF and RDF. Trigger phrases: "audit columns", "kolom audit", "kolom created_by updated_by", "konvensi audit"
+- The user asks which dialects are supported (postgres, mysql, oracle, sqlite)
+- The user is unsure about field shorthand like \`string:36 pk\` or \`decimal:15,2 default:0\`
+
+DO NOT USE FOR:
+- Validating an actual schema definition file -> use 'codegen_dbschema_validate'
+- Listing models from existing schema files -> use 'codegen_dbschema_models'
+- Generating DDL from schema files -> use 'codegen_dbschema_generate_ddl'
+- Migrating schema to a database -> use 'codegen_dbschema_migrate'
+- Introspecting an existing database into schema files -> use 'codegen_dbschema_introspect'
+- Looking up CRUD payload field validation rules -> use 'codegen_get_field_validation_catalog'
+- Looking up dashboard payload spec -> use 'codegen_get_dashboard_catalog'
+- Looking up CRUD query declarative spec -> use 'codegen_get_query_declarative_catalog'
+- Querying live database tables -> use 'codegen_list_tables' / 'codegen_describe_table'
+
+This tool runs: npx restforge catalog dbschema [--section=<X>] [--name=<Y>] [--kind=<Z>] in the given cwd.
+The catalog is sourced from restforge (single source of truth) so it stays in sync with
+the dbschema-kit version installed in the project.
+
+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. "look up the schema catalog", "create a new schema file", "validate the schema").
+- Speak in plain language. Summarise the catalog (number of field types, constraints, relations, dialects); do not paste the entire JSON unless the user explicitly asks for it.
+- The catalog is sourced from restforge (single source of truth) so it stays in sync with the dbschema-kit version installed in the project.
+- When the user asks about a specific construct (e.g. "how does belongsTo work"), use the catalog as ground truth and match the API exactly. Do not invent flags or behaviors not present in the catalog.
+- When a precondition is not met (e.g. the package is not installed), frame it as a question or next-step suggestion rather than an error.`,
+        inputSchema: {
+            cwd: z
+                .string()
+                .min(1)
+                .describe('Absolute path of the project folder (must contain node_modules/@restforgejs/platform)'),
+            section: z
+                .enum([
+                'defineModelOptions',
+                'fieldTypes',
+                'constraints',
+                'relationTypes',
+                'referentialActions',
+                'checkOperations',
+                'auditColumns',
+                'shorthandSyntax',
+                'namingRules',
+                'dialectSupport',
+            ])
+                .optional()
+                .describe('Filter to a single catalog section. When omitted, the full catalog is returned.'),
+            name: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Filter array sections by exact name (e.g. "string", "belongsTo", "cascade"). Use together with section.'),
+            kind: z
+                .enum(['standalone', 'value'])
+                .optional()
+                .describe('Filter constraints by kind. Only valid with section=constraints.'),
+        },
+        annotations: {
+            title: 'Get dbschema-kit Catalog',
+            readOnlyHint: true,
+            idempotentHint: true,
+        },
+    }, async ({ cwd, section, name, kind }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: @restforgejs/platform must be installed before this CLI command can run.
+        // Treated as a non-error precondition per the authoring guide §3.4.
+        try {
+            await access(join(projectCwd, 'node_modules', '@restforgejs', 'platform'));
+        }
+        catch {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: the RESTForge package is not installed in this project.
+
+Project path: ${projectCwd}
+Expected location: node_modules/@restforgejs/platform
+Requested section: ${section ?? 'all'}
+Requested name filter: ${name ?? 'none'}
+Requested kind filter: ${kind ?? 'none'}
+
+For the assistant:
+- The dbschema-kit catalog can only be retrieved once the RESTForge package is installed locally.
+- Suggest installing the package first, then retry getting the catalog.
+- When explaining to the user, say something like "the RESTForge package isn't installed yet — should I install it first?". Do not mention internal tool names.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Forward only the arguments the user supplied. CLI defaults remain in
+        // effect when the user does not specify them. per §3.5
+        const cliArgs = ['restforge', 'catalog', 'dbschema'];
+        if (section !== undefined)
+            cliArgs.push(`--section=${section}`);
+        if (name !== undefined)
+            cliArgs.push(`--name=${name}`);
+        if (kind !== undefined)
+            cliArgs.push(`--kind=${kind}`);
+        const result = await execProcess('npx', cliArgs, {
+            cwd: projectCwd,
+            timeout: 15_000,
+            env: { NODE_ENV: 'production' },
+            stripFinalNewline: true,
+        });
+        // CLI failure: real error per §3.4; structured per §3.5.
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to retrieve the dbschema-kit catalog.
+
+Project path: ${projectCwd}
+Section filter: ${section ?? 'all'}
+Name filter: ${name ?? 'none'}
+Kind filter: ${kind ?? 'none'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- CLI output ---
+stdout:
+${result.stdout}
+
+stderr:
+${result.stderr}
+--- end CLI output ---
+
+For the assistant:
+- Tell the user that the schema catalog could not be retrieved.
+- A common cause is an older RESTForge version that does not yet expose this command. If the CLI output mentions an unknown command, suggest upgrading the package as a likely fix.
+- Another common cause is an invalid filter combination (e.g. kind without section=constraints). The CLI surfaces the rule in its error message.
+- Do not paste the raw stdout/stderr unless the user explicitly asks. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Validate JSON output. Parse failure is a real error per §3.4 (CLI succeeded but produced invalid output).
+        let parsed;
+        try {
+            parsed = JSON.parse(result.stdout);
+        }
+        catch (err) {
+            const msg = err instanceof Error ? err.message : String(err);
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to parse dbschema-kit catalog JSON.
+
+Project path: ${projectCwd}
+Reason: ${msg}
+
+--- Raw stdout ---
+${result.stdout}
+--- end Raw stdout ---
+
+For the assistant:
+- The CLI returned output that is not valid JSON.
+- Summarise this to the user in plain language; do not paste the raw stdout unless they explicitly ask.
+- Suggest checking that the installed package version is compatible. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Defensive labeled facts: tolerate shape changes upstream.
+        const root = (parsed ?? {});
+        const summary = (root.summary ?? {});
+        const totalFieldTypes = typeof summary.totalFieldTypes === 'number' ? summary.totalFieldTypes : 'unknown';
+        const totalConstraints = typeof summary.totalConstraints === 'number' ? summary.totalConstraints : 'unknown';
+        const totalRelationTypes = typeof summary.totalRelationTypes === 'number' ? summary.totalRelationTypes : 'unknown';
+        const totalReferentialActions = typeof summary.totalReferentialActions === 'number'
+            ? summary.totalReferentialActions
+            : 'unknown';
+        const totalCheckOperations = typeof summary.totalCheckOperations === 'number' ? summary.totalCheckOperations : 'unknown';
+        const totalAuditColumns = typeof summary.totalAuditColumns === 'number' ? summary.totalAuditColumns : 'unknown';
+        const totalDialects = typeof summary.totalDialects === 'number' ? summary.totalDialects : 'unknown';
+        const sourceLabel = typeof root.source === 'string' ? root.source : 'dbschema-catalog';
+        const prettyJson = JSON.stringify(parsed, null, 2);
+        // Success: one-line summary + labeled facts + fenced JSON output per §3.5.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `dbschema-kit catalog retrieved successfully.
+
+Project path: ${projectCwd}
+Source: restforge (${sourceLabel}) — single source of truth for the installed runtime version
+Section filter: ${section ?? 'all'}
+Name filter: ${name ?? 'none'}
+Kind filter: ${kind ?? 'none'}
+totalFieldTypes: ${totalFieldTypes}
+totalConstraints: ${totalConstraints}
+totalRelationTypes: ${totalRelationTypes}
+totalReferentialActions: ${totalReferentialActions}
+totalCheckOperations: ${totalCheckOperations}
+totalAuditColumns: ${totalAuditColumns}
+totalDialects: ${totalDialects}
+
+--- dbschema-kit Catalog (JSON) ---
+${prettyJson}
+--- end dbschema-kit Catalog (JSON) ---
+
+For the assistant:
+- Confirm to the user that the catalog is available. Summarise in plain language: how many field types, constraints, relation types, referential actions, check operations, and dialects are listed.
+- Do not paste the full JSON unless the user explicitly asks. If the user only asked to "see the catalog", offer to drill into a specific section (field types, constraints, relations, shorthand syntax, naming rules) instead of dumping everything.
+- Use this catalog as ground truth when the user is:
+  * Asking "how is a schema file structured?" or "what does defineModel accept?"
+  * Authoring a schema file manually (via the Write/Edit tools)
+  * Asking about a specific construct (a field type, a constraint, a relation, a referential action, a check operation)
+  * Asking about shorthand syntax like \`string:36 pk\` or \`decimal:15,2 default:0\`
+  * Asking which dialects are supported and what differs between them
+- The catalog is dialect-agnostic (it describes the API). Dialect-specific differences (column type rendering, identifier quoting, FK syntax) are applied at DDL generation time, not at schema authoring time.
+- Match the API exactly. Do not invent flags, options, or behaviors that are not present in the catalog. If something the user wants is not in the catalog, say so honestly rather than fabricating.
+- After grounding from the catalog, the natural next step depends on user intent:
+  * Author a new file -> the schema-init action.
+  * Validate existing files -> the schema-validate action.
+  * Apply schema to DB -> dry-run first, then migrate.
+- Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=get-dbschema-catalog.js.map

package/dist/tools/codegen/get-dbschema-catalog.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get-dbschema-catalog.js","sourceRoot":"","sources":["../../../src/tools/codegen/get-dbschema-catalog.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAC1C,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAE1C,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,iCAAiC,CAAC,MAAiB;IACjE,MAAM,CAAC,YAAY,CACjB,8BAA8B,EAC9B;QACE,KAAK,EAAE,0BAA0B;QACjC,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2IAmCwH;QACrI,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,uFAAuF,CAAC;YACpG,OAAO,EAAE,CAAC;iBACP,IAAI,CAAC;gBACJ,oBAAoB;gBACpB,YAAY;gBACZ,aAAa;gBACb,eAAe;gBACf,oBAAoB;gBACpB,iBAAiB;gBACjB,cAAc;gBACd,iBAAiB;gBACjB,aAAa;gBACb,gBAAgB;aACjB,CAAC;iBACD,QAAQ,EAAE;iBACV,QAAQ,CAAC,iFAAiF,CAAC;YAC9F,IAAI,EAAE,CAAC;iBACJ,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,yGAAyG,CAAC;YACtH,IAAI,EAAE,CAAC;iBACJ,IAAI,CAAC,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC;iBAC7B,QAAQ,EAAE;iBACV,QAAQ,CAAC,kEAAkE,CAAC;SAChF;QACD,WAAW,EAAE;YACX,KAAK,EAAE,0BAA0B;YACjC,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,OAAO,EAAE,IAAI,EAAE,IAAI,EAAE,EAAE,EAAE;QACrC,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+FAA+F;QAC/F,oEAAoE;QACpE,IAAI,CAAC;YACH,MAAM,MAAM,CAAC,IAAI,CAAC,UAAU,EAAE,cAAc,EAAE,cAAc,EAAE,UAAU,CAAC,CAAC,CAAC;QAC7E,CAAC;QAAC,MAAM,CAAC;YACP,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;;qBAEL,OAAO,IAAI,KAAK;yBACZ,IAAI,IAAI,MAAM;yBACd,IAAI,IAAI,MAAM;;;;;gKAKyH;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,uEAAuE;QACvE,uDAAuD;QACvD,MAAM,OAAO,GAAG,CAAC,WAAW,EAAE,SAAS,EAAE,UAAU,CAAC,CAAC;QACrD,IAAI,OAAO,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,aAAa,OAAO,EAAE,CAAC,CAAC;QAChE,IAAI,IAAI,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC;QACvD,IAAI,IAAI,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,UAAU,IAAI,EAAE,CAAC,CAAC;QAEvD,MAAM,MAAM,GAAG,MAAM,WAAW,CAC9B,KAAK,EACL,OAAO,EACP;YACE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;YACf,GAAG,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE;YAC/B,iBAAiB,EAAE,IAAI;SACxB,CACF,CAAC;QAEF,yDAAyD;QACzD,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;kBACR,OAAO,IAAI,KAAK;eACnB,IAAI,IAAI,MAAM;eACd,IAAI,IAAI,MAAM;WAClB,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;;0GAO2F;qBAC7F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,4GAA4G;QAC5G,IAAI,MAAe,CAAC;QACpB,IAAI,CAAC;YACH,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;QACrC,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,MAAM,GAAG,GAAG,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC;YAC7D,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;UAChB,GAAG;;;EAGX,MAAM,CAAC,MAAM;;;;;;yGAM0F;qBAC5F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,4DAA4D;QAC5D,MAAM,IAAI,GAAG,CAAC,MAAM,IAAI,EAAE,CAA4B,CAAC;QACvD,MAAM,OAAO,GAAG,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAA4B,CAAC;QAChE,MAAM,eAAe,GACnB,OAAO,OAAO,CAAC,eAAe,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,eAAe,CAAC,CAAC,CAAC,SAAS,CAAC;QACpF,MAAM,gBAAgB,GACpB,OAAO,OAAO,CAAC,gBAAgB,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,gBAAgB,CAAC,CAAC,CAAC,SAAS,CAAC;QACtF,MAAM,kBAAkB,GACtB,OAAO,OAAO,CAAC,kBAAkB,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,kBAAkB,CAAC,CAAC,CAAC,SAAS,CAAC;QAC1F,MAAM,uBAAuB,GAC3B,OAAO,OAAO,CAAC,uBAAuB,KAAK,QAAQ;YACjD,CAAC,CAAC,OAAO,CAAC,uBAAuB;YACjC,CAAC,CAAC,SAAS,CAAC;QAChB,MAAM,oBAAoB,GACxB,OAAO,OAAO,CAAC,oBAAoB,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,oBAAoB,CAAC,CAAC,CAAC,SAAS,CAAC;QAC9F,MAAM,iBAAiB,GACrB,OAAO,OAAO,CAAC,iBAAiB,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,iBAAiB,CAAC,CAAC,CAAC,SAAS,CAAC;QACxF,MAAM,aAAa,GACjB,OAAO,OAAO,CAAC,aAAa,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,aAAa,CAAC,CAAC,CAAC,SAAS,CAAC;QAChF,MAAM,WAAW,GAAG,OAAO,IAAI,CAAC,MAAM,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,kBAAkB,CAAC;QAEvF,MAAM,UAAU,GAAG,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;QAEnD,2EAA2E;QAC3E,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;qBACL,WAAW;kBACd,OAAO,IAAI,KAAK;eACnB,IAAI,IAAI,MAAM;eACd,IAAI,IAAI,MAAM;mBACV,eAAe;oBACd,gBAAgB;sBACd,kBAAkB;2BACb,uBAAuB;wBAC1B,oBAAoB;qBACvB,iBAAiB;iBACrB,aAAa;;;EAG5B,UAAU;;;;;;;;;;;;;;;;;;6BAkBiB;iBAClB;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/get-field-validation-catalog.d.ts

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