@restforgejs/mcp-server 1.2.0

package/dist/tools/codegen/create-endpoint.js

@@ -0,0 +1,263 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+async function pathExists(p) {
+    try {
+        await access(p);
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+export function registerCodegenCreateEndpoint(server) {
+    server.registerTool('codegen_create_endpoint', {
+        title: 'Create Endpoint Module',
+        description: `Generate a project + endpoint module (submodule, model, metadata, demo files, optional audit migration) from an existing payload spec by wrapping restforge create. URL pattern produced: /api/{project}/{endpoint}/{action}.
+
+This tool is DESTRUCTIVE: it spawns the CLI which writes / overwrites files in 'src/modules/<project>/', 'src/models/<project>/', 'metadata/<project>/', 'examples/<project>/<endpoint>/', and updates '.restforge/projects.json'. Single-call semantics: the tool always executes; there is no preview mode. Internally the tool always passes '--force=true' to the CLI to bypass the CLI's interactive y/N readline prompt (which would deadlock in a no-TTY subprocess).
+
+Safety net: when the CLI overwrites an existing module, model, or query directory, it FIRST renames the previous version to '<name>.archive.NNN' (NNN is a sequential generation number starting at 001) inside the same folder. Rollback by restoring the most recent archive is always possible.
+
+AI responsibility — IMPORTANT: because this tool always executes and may overwrite generated files, you MUST confirm intent with the user in plain language BEFORE invoking the tool. You do NOT need to detect file conflicts programmatically — the CLI handles that and the archive mechanism keeps the previous version safe. Just confirm intent. Examples of good confirmation phrasing in user-facing chat:
+- "Saya akan generate endpoint <endpoint> di project <project> ({database}). Kalau modul/model lama sudah ada, versi sebelumnya akan disimpan sebagai '.archive.NNN'. Lanjut?"
+- "I will generate <endpoint> under project <project> using <database>. Existing files will be archived as .archive.NNN before being overwritten. Proceed?"
+
+USE WHEN:
+- The user asks to generate, create, or scaffold an endpoint, resource, or module from a payload (e.g. "buatkan endpoint untuk product", "generate resource users", "create endpoint dari payload X", "scaffold a new endpoint")
+- The user mentions "endpoint", "resource", "module" or the URL pattern /api/{project}/{resource}/{action} and wants to register it as runnable code
+- The user has authored a payload file (e.g. via 'codegen_generate_payload' or manually) and now wants to materialise it as runnable code in the project
+- Pertanyaan dalam bentuk: "tambahkan endpoint X ke project Y", "buat module baru di project Z", "scaffold endpoint baru pakai payload ini", "generate kode dari payload ini"
+- The user asks to add a new endpoint to an existing project (registry already has the project, just adding more endpoints)
+- The user asks to bootstrap a brand-new project together with its first endpoint
+- The user asks about regenerating an existing endpoint after the payload changed (this triggers overwrite + archive flow inside the CLI; previous versions become '.archive.NNN' in place)
+- After 'codegen_validate_payload' confirmed the payload is valid — this is the natural follow-up that turns a verified payload into runnable code
+
+DO NOT USE FOR:
+- Generating the payload JSON itself from a database table -> use 'codegen_generate_payload'
+- Validating a payload before generation -> use 'codegen_validate_payload'
+- Inspecting per-column differences between payload and database -> use 'codegen_diff_payload'
+- Syncing payload changes back into existing payload files after schema drift -> use 'codegen_sync_payload'
+- Looking up the field validation catalog before authoring the payload -> use 'codegen_get_field_validation_catalog'
+- Looking up the query declarative catalog before authoring the payload -> use 'codegen_get_query_declarative_catalog'
+- Deleting a project or endpoint — out of scope; the user must run 'npx restforge drop' manually
+- Generating a processor (Kafka consumer, etc.) — out of scope; the CLI has separate 'processor' and 'consumer-create' subcommands not covered by this MCP server yet
+- Generating a dashboard endpoint — out of scope; the CLI has a separate 'dashboard' subcommand
+- Listing all registered projects in the registry — out of scope here; use the CLI's 'list' subcommand directly
+- Database DDL changes (CREATE TABLE, ALTER TABLE) — not in this tool's scope. The audit migration sub-step DOES create a single audit table when the payload uses the 'audit' fieldPolicy strategy, but that is the only DDL it touches.
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The payload file must exist at <cwd>/payload/<payload>.json before calling this tool.
+- The CLI itself rejects reserved project names (src, lib, node_modules, config, utils, models, controllers, middleware, routes) and reserved endpoint names (health, status, admin, api, auth, login, logout, register, index, main, app, config, test, docs, swagger, graphql, websocket, socket). When in doubt, ask the user to pick a different name before invoking this tool.
+
+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. "the endpoint generator", "the project generator", "generate the payload first", "validate the payload first").
+- Speak in plain language. Summarise the result; do not paste raw CLI output unless the user explicitly asks.
+- This tool is destructive: it can overwrite existing module / model / query files. BEFORE invoking this tool, ALWAYS confirm with the user in plain language. Example: "Saya akan generate endpoint <endpoint> di project <project>. Kalau file lama sudah ada, akan ditimpa (versi lama disimpan sebagai .archive.NNN). Lanjut?". Do not detect conflicts programmatically; the CLI handles that and creates the archive.
+- After the tool runs, summarise the result. Read the CLI output and identify any archive activity (the CLI uses the '.archive.NNN' naming convention in the filesystem and reports archive activity in its output, but the exact wording may evolve). When archives are created, tell the user that previous versions are preserved in case rollback is needed.
+- 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 a payload/ directory with the named payload file)'),
+            project: z
+                .string()
+                .min(1)
+                .max(50)
+                .regex(/^[a-zA-Z0-9][a-zA-Z0-9_-]*$/, 'must start with a letter or number; only letters, numbers, dashes, underscores allowed')
+                .describe('Project name. Letters/numbers/dash/underscore, max 50 chars, cannot start or end with dash or underscore. Auto-lowercased by the CLI. Reserved names rejected by the CLI: src, lib, node_modules, config, utils, models, controllers, middleware, routes.'),
+            endpoint: z
+                .string()
+                .min(1)
+                .max(50)
+                .regex(/^[a-zA-Z0-9][a-zA-Z0-9_-]*$/, 'must start with a letter or number; only letters, numbers, dashes, underscores allowed')
+                .describe('Endpoint name (also called "resource" — the URL pattern is /api/{project}/{endpoint}/{action}). Same shape as project. Auto-lowercased by the CLI. Reserved names rejected by the CLI: health, status, admin, api, auth, login, logout, register, index, main, app, config, test, docs, swagger, graphql, websocket, socket. Naming convention: kebab-case or snake-case recommended.'),
+            payload: z
+                .string()
+                .min(1)
+                .max(50)
+                .regex(/^[a-zA-Z0-9][a-zA-Z0-9_-]*$/, 'must start with a letter or number; only letters, numbers, dashes, underscores allowed')
+                .describe('Payload file name without the .json extension. The file must exist at <cwd>/payload/<payload>.json. Same shape rules as project.'),
+            database: z
+                .enum(['postgres', 'oracle', 'mysql'])
+                .optional()
+                .describe('Database type for the generated code. Default postgres.'),
+            createDemo: z
+                .boolean()
+                .optional()
+                .describe('Default true (CLI default). When true, generate demo files (curl, postman, insomnia) for testing the endpoint.'),
+            skipSqlValidation: z
+                .boolean()
+                .optional()
+                .describe('Default false (CLI default). When true, skip SQL keyword validation in the payload. Useful when payload includes generated SQL fragments that the validator flags as suspicious.'),
+            noAuditMigration: z
+                .boolean()
+                .optional()
+                .describe('Default false (CLI default). When true, skip executing the audit table migration even if the payload has fieldPolicy.*.strategies containing "audit". The migration SQL file is still written to migrations/audit/ as documentation.'),
+        },
+        annotations: {
+            title: 'Create Endpoint Module',
+            readOnlyHint: false, // tool spawns CLI that writes module/model/metadata/demo files and updates the registry
+            destructiveHint: true, // can overwrite existing files (CLI archives them as .archive.NNN first)
+            idempotentHint: false, // re-running creates new archive files and may execute audit migration again
+        },
+    }, async ({ cwd, project, endpoint, payload, database, createDemo, skipSqlValidation, noAuditMigration }) => {
+        const projectCwd = resolve(cwd);
+        const dbType = database ?? 'postgres';
+        // Pre-flight 1: @restforgejs/platform must be installed. Treated as a non-error precondition per §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 project: ${project}
+Requested endpoint: ${endpoint}
+Requested payload: ${payload}
+Requested database: ${dbType}
+
+For the assistant:
+- The endpoint generator can only run once the RESTForge package is installed locally.
+- Suggest installing the package first, then retry generating the endpoint.
+- 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
+            };
+        }
+        // Pre-flight 2: payload file must exist. Treated as a non-error precondition per §3.4.
+        const payloadPath = join(projectCwd, 'payload', `${payload}.json`);
+        if (!(await pathExists(payloadPath))) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Precondition not met: payload file not found.
+
+Project path: ${projectCwd}
+Expected payload file: ${payloadPath}
+Requested project: ${project}
+Requested endpoint: ${endpoint}
+Requested database: ${dbType}
+
+For the assistant:
+- The endpoint generator needs the payload file to exist before it can run.
+- Suggest generating or creating the payload first. The payload generator tool can introspect a database table into a payload JSON, or the user can author it manually in the payload/ folder.
+- When explaining to the user, say something like "the payload file '${payload}.json' isn't in the payload/ folder yet — should I generate it from a database table first, or do you have one to put there?". Do not mention internal tool names.`,
+                    },
+                ],
+                isError: false, // per §3.4
+            };
+        }
+        // Build CLI invocation. --force=true is hardcoded: it bypasses the interactive readline
+        // prompt that would otherwise deadlock the subprocess. Conflict detection and archive
+        // creation are delegated to the CLI (single source of truth — see conflict-checker.js).
+        const cliArgs = [
+            'restforge',
+            'endpoint',
+            'create',
+            `--project=${project}`,
+            `--name=${endpoint}`,
+            `--payload=${payload}`,
+            `--database=${dbType}`,
+            '--force=true',
+        ];
+        if (createDemo !== undefined)
+            cliArgs.push(`--create-demo=${createDemo}`);
+        if (skipSqlValidation !== undefined)
+            cliArgs.push(`--skip-sql-validation=${skipSqlValidation}`);
+        if (noAuditMigration !== undefined)
+            cliArgs.push(`--no-audit-migration=${noAuditMigration}`);
+        const result = await execProcess('npx', cliArgs, {
+            cwd: projectCwd,
+            timeout: 120_000,
+            env: { NODE_ENV: 'production' }, // suppress legacy banner output
+            stripFinalNewline: true,
+        });
+        // Branch C: CLI failure — real error per §3.4; structured per §3.5.
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to create the endpoint module.
+
+Project path: ${projectCwd}
+Project: ${project}
+Endpoint: ${endpoint}
+Payload: payload/${payload}.json
+Database: ${dbType}
+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 creating the endpoint module did not complete successfully.
+- Summarise the most likely cause from the CLI output in plain language. Common causes:
+  * Reserved name rejected by the validator (project or endpoint name is in the reserved list) — suggest picking a different name.
+  * Database mismatch with the existing project registry entry — the CLI refuses to switch the database for an existing project. Suggest sticking with the originally registered database, or confirm with the user that switching is really intended.
+  * Payload validation failed (e.g. SQL keywords flagged) — suggest validating the payload first to surface the specific issue, or rerunning with skipSqlValidation=true if the SQL fragments are intentional.
+  * Audit migration failed (e.g. cannot connect to the database) — suggest checking the database connection config, or rerunning with noAuditMigration=true to skip the live migration (the SQL file will still be written for manual execution).
+- Do not paste the raw stdout/stderr unless the user explicitly asks. Do not mention internal tool names.
+- Offer to retry once the underlying issue is resolved.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Branch D: CLI success — one-line summary + labeled facts + fenced output per §3.5.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Endpoint module created successfully.
+
+Project path: ${projectCwd}
+Project: ${project}
+Endpoint: ${endpoint}
+Payload: payload/${payload}.json
+Database: ${dbType}
+
+Generated artefacts (commonly produced by the CLI):
+- src/modules/${project}/${endpoint}.js (submodule)
+- src/models/${project}/${endpoint}.js (model)
+- src/models/${project}/query/ (if payload uses file reference queries)
+- metadata/${project}/${endpoint}.json (and related metadata)
+- examples/${project}/${endpoint}/* (if createDemo=true)
+- migrations/audit/<table>_audit.sql (if payload uses fieldPolicy 'audit' strategy)
+- .restforge/projects.json (registry update)
+
+--- CLI output ---
+${result.stdout}
+--- end CLI output ---
+
+For the assistant:
+- Confirm to the user in plain language that the project and endpoint were generated. Mention the project, endpoint, and database used.
+- Do not paste the entire CLI output unless the user explicitly asks; summarise instead.
+- Suggest natural follow-up actions appropriate to context: review the generated files, run the project to test the new endpoint, generate a processor or test, etc. Do not mention internal tool names.
+- Read the CLI output to identify any archive activity. The CLI uses the '.archive.NNN' naming convention in the filesystem; it also reports archive activity in its output, though the exact phrasing may evolve. When archives are created, tell the user that the previous version of each overwritten file is preserved as an archive file in the same folder, and explain where to find them if rollback is needed.
+- Read the CLI output to identify any audit migration activity (the CLI reports it when the payload uses a fieldPolicy 'audit' strategy). When present, summarise it briefly to the user (e.g. that the audit table for the related table was created or updated).
+- Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=create-endpoint.js.map

package/dist/tools/codegen/create-endpoint.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"create-endpoint.js","sourceRoot":"","sources":["../../../src/tools/codegen/create-endpoint.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,KAAK,UAAU,UAAU,CAAC,CAAS;IACjC,IAAI,CAAC;QACH,MAAM,MAAM,CAAC,CAAC,CAAC,CAAC;QAChB,OAAO,IAAI,CAAC;IACd,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;AACH,CAAC;AAED,MAAM,UAAU,6BAA6B,CAAC,MAAiB;IAC7D,MAAM,CAAC,YAAY,CACjB,yBAAyB,EACzB;QACE,KAAK,EAAE,wBAAwB;QAC/B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uGA4CoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,4IAA4I,CAAC;YACzJ,OAAO,EAAE,CAAC;iBACP,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,GAAG,CAAC,EAAE,CAAC;iBACP,KAAK,CAAC,6BAA6B,EAAE,wFAAwF,CAAC;iBAC9H,QAAQ,CAAC,2PAA2P,CAAC;YACxQ,QAAQ,EAAE,CAAC;iBACR,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,GAAG,CAAC,EAAE,CAAC;iBACP,KAAK,CAAC,6BAA6B,EAAE,wFAAwF,CAAC;iBAC9H,QAAQ,CAAC,uXAAuX,CAAC;YACpY,OAAO,EAAE,CAAC;iBACP,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,GAAG,CAAC,EAAE,CAAC;iBACP,KAAK,CAAC,6BAA6B,EAAE,wFAAwF,CAAC;iBAC9H,QAAQ,CAAC,kIAAkI,CAAC;YAC/I,QAAQ,EAAE,CAAC;iBACR,IAAI,CAAC,CAAC,UAAU,EAAE,QAAQ,EAAE,OAAO,CAAC,CAAC;iBACrC,QAAQ,EAAE;iBACV,QAAQ,CAAC,yDAAyD,CAAC;YACtE,UAAU,EAAE,CAAC;iBACV,OAAO,EAAE;iBACT,QAAQ,EAAE;iBACV,QAAQ,CAAC,gHAAgH,CAAC;YAC7H,iBAAiB,EAAE,CAAC;iBACjB,OAAO,EAAE;iBACT,QAAQ,EAAE;iBACV,QAAQ,CAAC,kLAAkL,CAAC;YAC/L,gBAAgB,EAAE,CAAC;iBAChB,OAAO,EAAE;iBACT,QAAQ,EAAE;iBACV,QAAQ,CAAC,sOAAsO,CAAC;SACpP;QACD,WAAW,EAAE;YACX,KAAK,EAAE,wBAAwB;YAC/B,YAAY,EAAE,KAAK,EAAK,wFAAwF;YAChH,eAAe,EAAE,IAAI,EAAG,yEAAyE;YACjG,cAAc,EAAE,KAAK,EAAG,6EAA6E;SACtG;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,QAAQ,EAAE,UAAU,EAAE,iBAAiB,EAAE,gBAAgB,EAAE,EAAE,EAAE;QACvG,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAChC,MAAM,MAAM,GAAG,QAAQ,IAAI,UAAU,CAAC;QAEtC,uGAAuG;QACvG,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;sBACN,QAAQ;qBACT,OAAO;sBACN,MAAM;;;;;gKAKoI;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,uFAAuF;QACvF,MAAM,WAAW,GAAG,IAAI,CAAC,UAAU,EAAE,SAAS,EAAE,GAAG,OAAO,OAAO,CAAC,CAAC;QACnE,IAAI,CAAC,CAAC,MAAM,UAAU,CAAC,WAAW,CAAC,CAAC,EAAE,CAAC;YACrC,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;yBACD,WAAW;qBACf,OAAO;sBACN,QAAQ;sBACR,MAAM;;;;;uEAK2C,OAAO,oKAAoK;qBACrO;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,wFAAwF;QACxF,sFAAsF;QACtF,wFAAwF;QACxF,MAAM,OAAO,GAAG;YACd,WAAW;YACX,UAAU;YACV,QAAQ;YACR,aAAa,OAAO,EAAE;YACtB,UAAU,QAAQ,EAAE;YACpB,aAAa,OAAO,EAAE;YACtB,cAAc,MAAM,EAAE;YACtB,cAAc;SACf,CAAC;QACF,IAAI,UAAU,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAC1E,IAAI,iBAAiB,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,yBAAyB,iBAAiB,EAAE,CAAC,CAAC;QAChG,IAAI,gBAAgB,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,wBAAwB,gBAAgB,EAAE,CAAC,CAAC;QAE7F,MAAM,MAAM,GAAG,MAAM,WAAW,CAC9B,KAAK,EACL,OAAO,EACP;YACE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,OAAO;YAChB,GAAG,EAAE,EAAE,QAAQ,EAAE,YAAY,EAAE,EAAE,gCAAgC;YACjE,iBAAiB,EAAE,IAAI;SACxB,CACF,CAAC;QAEF,oEAAoE;QACpE,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;WACf,OAAO;YACN,QAAQ;mBACD,OAAO;YACd,MAAM;WACP,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;;;;;;wDAWyC;qBAC3C;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,qFAAqF;QACrF,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;WACf,OAAO;YACN,QAAQ;mBACD,OAAO;YACd,MAAM;;;gBAGF,OAAO,IAAI,QAAQ;eACpB,OAAO,IAAI,QAAQ;eACnB,OAAO;aACT,OAAO,IAAI,QAAQ;aACnB,OAAO,IAAI,QAAQ;;;;;EAK9B,MAAM,CAAC,MAAM;;;;;;;;;6BASc;iBAClB;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/dbschema-generate-ddl.d.ts

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

package/dist/tools/codegen/dbschema-generate-ddl.js

@@ -0,0 +1,187 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerCodegenDbschemaGenerateDdl(server) {
+    server.registerTool('codegen_dbschema_generate_ddl', {
+        title: 'Generate DDL from dbschema-kit Files',
+        description: `Generate dialect-specific DDL SQL (CREATE TABLE, CREATE INDEX, optional DROP TABLE) from dbschema-kit definition files in topological order, by wrapping restforge schema generate-ddl. Output goes to stdout (returned in the response) or to a file when 'out' is set. Tables are emitted in topological order so parent tables are created before children; DROP order is reversed.
+
+USE WHEN:
+- The user asks to generate DDL, "buatkan SQL DDL", "generate CREATE TABLE statements"
+- Pertanyaan dalam bentuk: "convert schema ke postgres SQL", "generate DDL untuk MySQL", "buatkan migration script"
+- Before applying schema to a database — for preview/review (safer than running migrate directly)
+- The user wants a portable SQL file for sharing with a DBA or for git versioning
+- The user asks for cross-dialect compatibility ("apakah schema bisa untuk postgres dan mysql")
+- Migration script preparation
+- After validating schema and the user wants to see the SQL output
+
+DO NOT USE FOR:
+- Applying DDL to a live database -> use 'codegen_dbschema_migrate'
+- Generating CRUD payload SQL -> out of scope (different layer)
+- Generating ad-hoc query SQL -> out of scope
+- Generating DDL for tables not defined in schema files -> out of scope (only schema-as-code files are processed)
+- Validating schema correctness -> use 'codegen_dbschema_validate'
+
+This tool runs: npx restforge schema generate-ddl <path> --dialect=<X> [--out=<file>] [--drop=<bool>] in the given cwd.
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The schema path must exist and contain valid schema files. If the CLI fails, the failure response surfaces 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. "generate the DDL", "preview the SQL", "apply the schema").
+- Speak in plain language. Summarise the result (dialect, output target, drop mode); do not paste raw DDL unless the user explicitly asks.
+- Output is dialect-aware: column types, FK syntax, default value translation, and identifier quoting all change per dialect. Do not assume cross-dialect equivalence.
+- The order is topological — parent tables before child tables. DROP order is reversed.
+- For preview before applying, this is the safe path. To actually apply, suggest the migrate action next.
+- When 'out' is set, the file is written; if it exists, it is overwritten. Confirm with the user if a destructive overwrite is intended.
+- If the user wants multi-dialect output, suggest invoking once per dialect.
+- 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)'),
+            path: z
+                .string()
+                .min(1)
+                .describe('Path to schema file or folder relative to cwd (e.g. "schema", "schema/supplier.js").'),
+            dialect: z
+                .enum(['postgres', 'mysql', 'oracle', 'sqlite'])
+                .describe('Target SQL dialect.'),
+            out: z
+                .string()
+                .min(1)
+                .optional()
+                .describe('Output file path relative to cwd (e.g. "db/migrations/001-init.sql"). When omitted, the DDL is returned in the response (stdout). Existing files at this path are overwritten.'),
+            drop: z
+                .boolean()
+                .optional()
+                .describe('Default false. When true, prepend DROP TABLE statements (in reverse topological order) before the CREATE statements.'),
+        },
+        annotations: {
+            title: 'Generate DDL from dbschema-kit Files',
+            idempotentHint: true, // pure transformation; same input -> same output (file overwrite is in-place)
+        },
+    }, async ({ cwd, path, dialect, out, drop }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: @restforgejs/platform must be present in node_modules. per §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 schema path: ${path}
+Requested dialect: ${dialect}
+Requested out: ${out ?? '(stdout)'}
+Requested drop: ${drop ?? false}
+
+For the assistant:
+- The user needs to install the RESTForge package before DDL can be generated.
+- Suggest installing the package first, then retry generating the DDL.
+- 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',
+            'schema',
+            'generate-ddl',
+            path,
+            `--dialect=${dialect}`,
+        ];
+        if (out !== undefined)
+            cliArgs.push(`--out=${out}`);
+        if (drop !== undefined)
+            cliArgs.push(`--drop=${drop}`);
+        const result = await execProcess('npx', cliArgs, {
+            cwd: projectCwd,
+            timeout: 30_000,
+            env: { NODE_ENV: 'production' },
+            stripFinalNewline: true,
+        });
+        // Branch C: CLI failure — real error per §3.4. per §3.5
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to generate DDL.
+
+Project path: ${projectCwd}
+Schema path: ${path}
+Dialect: ${dialect}
+Output: ${out ?? '(stdout)'}
+Drop tables: ${drop ?? false}
+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 DDL did not complete successfully.
+- Summarise the most likely cause from the CLI output in plain language. Common causes:
+  * Schema validation failure — a file has invalid syntax or a broken FK reference. Suggest running the validate action first to surface the specific issue.
+  * Schema folder not found — the CLI cannot locate the path. Suggest verifying the folder name.
+  * Invalid dialect — only postgres, mysql, oracle, sqlite are supported.
+  * Output path issue (parent folder missing) — the CLI does not auto-create intermediate folders. Suggest creating them first.
+  * Unknown command 'schema generate-ddl' — the installed RESTForge version may be older than this CLI subcommand; suggest upgrading the package.
+- Do not paste the raw stdout/stderr unless the user explicitly asks. Do not mention internal tool names.
+- Offer to retry once the issue is resolved.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Branch B: success — labeled facts + fenced raw output per §3.5.
+        // When 'out' is set, stdout contains a short status message; when not, stdout contains the full DDL.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `DDL generated successfully.
+
+Project path: ${projectCwd}
+Schema path: ${path}
+Dialect: ${dialect}
+Drop tables: ${drop ?? false}
+Output: ${out ?? '(stdout)'}
+
+--- CLI output ---
+${result.stdout}
+--- end CLI output ---
+
+For the assistant:
+- Confirm to the user that the DDL was generated. Mention the dialect and (if applicable) the output file path in plain language.
+- DDL is dialect-specific — column types, FK syntax, identifier quoting, and default value translation differ across postgres/mysql/oracle/sqlite. Do not assume cross-dialect equivalence.
+- The order is topological — parent tables before child tables. When drop=true, DROP statements are emitted in reverse order before the CREATE block.
+- When 'out' was set, the file is written; existing files at that path are overwritten. Mention the file path so the user can review or commit it.
+- For preview before applying, this is the safe path. To apply the schema to a live database, suggest the migrate action next.
+- If the user wants multi-dialect output, mention that the action can be invoked once per dialect.
+- Do not paste the full DDL unless the user explicitly asks.
+- Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=dbschema-generate-ddl.js.map

package/dist/tools/codegen/dbschema-generate-ddl.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dbschema-generate-ddl.js","sourceRoot":"","sources":["../../../src/tools/codegen/dbschema-generate-ddl.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,sCAAsC;QAC7C,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uGAiCoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,uFAAuF,CAAC;YACpG,IAAI,EAAE,CAAC;iBACJ,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,sFAAsF,CAAC;YACnG,OAAO,EAAE,CAAC;iBACP,IAAI,CAAC,CAAC,UAAU,EAAE,OAAO,EAAE,QAAQ,EAAE,QAAQ,CAAC,CAAC;iBAC/C,QAAQ,CAAC,qBAAqB,CAAC;YAClC,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,gLAAgL,CAAC;YAC7L,IAAI,EAAE,CAAC;iBACJ,OAAO,EAAE;iBACT,QAAQ,EAAE;iBACV,QAAQ,CAAC,sHAAsH,CAAC;SACpI;QACD,WAAW,EAAE;YACX,KAAK,EAAE,sCAAsC;YAC7C,cAAc,EAAE,IAAI,EAAE,8EAA8E;SACrG;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,IAAI,EAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,EAAE,EAAE;QAC1C,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,sFAAsF;QACtF,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;;yBAED,IAAI;qBACR,OAAO;iBACX,GAAG,IAAI,UAAU;kBAChB,IAAI,IAAI,KAAK;;;;;gKAKiI;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,uEAAuE;QACvE,uDAAuD;QACvD,MAAM,OAAO,GAAG;YACd,WAAW;YACX,QAAQ;YACR,cAAc;YACd,IAAI;YACJ,aAAa,OAAO,EAAE;SACvB,CAAC;QACF,IAAI,GAAG,KAAK,SAAS;YAAE,OAAO,CAAC,IAAI,CAAC,SAAS,GAAG,EAAE,CAAC,CAAC;QACpD,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,wDAAwD;QACxD,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;eACX,IAAI;WACR,OAAO;UACR,GAAG,IAAI,UAAU;eACZ,IAAI,IAAI,KAAK;WACjB,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;;;;;;;6CAY8B;qBAChC;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,kEAAkE;QAClE,qGAAqG;QACrG,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;eACX,IAAI;WACR,OAAO;eACH,IAAI,IAAI,KAAK;UAClB,GAAG,IAAI,UAAU;;;EAGzB,MAAM,CAAC,MAAM;;;;;;;;;;;6BAWc;iBAClB;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/dbschema-init.d.ts

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

package/dist/tools/codegen/dbschema-init.js

@@ -0,0 +1,158 @@
+import { z } from 'zod';
+import { access } from 'node:fs/promises';
+import { resolve, join } from 'node:path';
+import { execProcess } from '../../lib/exec.js';
+export function registerCodegenDbschemaInit(server) {
+    server.registerTool('codegen_dbschema_init', {
+        title: 'Init dbschema-kit Skeleton File',
+        description: `Create a new schema definition skeleton file at the given path, by wrapping restforge schema init. The generated file uses the factory function pattern with a minimal starter (id, code, name, is_active fields). The user is expected to edit the file afterwards to add the real domain fields, indexes, uniques, and relations.
+
+USE WHEN:
+- The user asks to create a new schema file, schema skeleton, or defineModel template
+- Pertanyaan dalam bentuk: "buatkan file schema untuk tabel X", "init schema definition", "create dbschema skeleton", "buat starter file schema"
+- Before any schema-as-code workflow when no schema files exist yet
+- The user wants to start declarative schema definition from scratch
+- The user asks for a starter template they can edit
+- After 'codegen_get_dbschema_catalog' grounding and the user is ready to author
+- The user mentions a new domain entity (e.g. "I need a customer_invoice table") and wants a schema file as a starting point
+
+DO NOT USE FOR:
+- Editing an existing schema file -> use Edit/Write tools directly
+- Generating schema files from a live database -> use 'codegen_dbschema_introspect'
+- Creating a CRUD payload (different concept) -> use 'codegen_generate_payload'
+- Validating the schema -> use 'codegen_dbschema_validate'
+- Generating DDL -> use 'codegen_dbschema_generate_ddl'
+
+This tool runs: npx restforge schema init <path> in the given cwd.
+The CLI writes a JavaScript factory function file to the target path. The path must end with '.js' and the file must NOT already exist.
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The target file must NOT already exist (CLI fails otherwise — the user can pick a different name or remove the existing file first).
+- The parent folder of the target path must exist (CLI does not create intermediate folders).
+
+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. "create a starter schema file", "look up the schema catalog", "validate the schema").
+- Speak in plain language. Confirm the file was created, mention the file path and the derived table name; do not paste the raw CLI output unless the user explicitly asks.
+- The skeleton is intentionally minimal — only id, code, name, is_active fields. The user will need to edit it for their actual domain.
+- If the user wants multiple files (e.g. category.js, supplier.js, customer.js), invoke this action once per file. Do not assume one call covers multiple files.
+- 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)'),
+            path: z
+                .string()
+                .min(1)
+                .describe('Target file path relative to cwd (must end with .js, file must NOT already exist). Examples: "schema/supplier.js", "db/models/inventory/products.js".'),
+        },
+        annotations: {
+            title: 'Init dbschema-kit Skeleton File',
+            destructiveHint: false, // creates a new file; CLI refuses to overwrite an existing one
+            idempotentHint: false, // each call attempts to create a new file; second call on the same path fails
+        },
+    }, async ({ cwd, path }) => {
+        const projectCwd = resolve(cwd);
+        // Precondition check: @restforgejs/platform must be present in node_modules. per §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 path: ${path}
+
+For the assistant:
+- The user needs to install the RESTForge package before a schema skeleton file can be created.
+- Suggest installing the package first, then retry creating the skeleton.
+- 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
+            };
+        }
+        // Subprocess call. The CLI handles all filesystem validation
+        // (extension, parent folder existence, target file non-existence). per §3.5
+        const cliArgs = ['restforge', 'schema', 'init', path];
+        const result = await execProcess('npx', cliArgs, {
+            cwd: projectCwd,
+            timeout: 10_000,
+            env: { NODE_ENV: 'production' },
+            stripFinalNewline: true,
+        });
+        // Branch C: CLI failure — real error per §3.4; structured per §3.5.
+        if (!result.success) {
+            return {
+                content: [
+                    {
+                        type: 'text',
+                        text: `Failed to create the schema skeleton file.
+
+Project path: ${projectCwd}
+Target path: ${path}
+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 creating the schema skeleton did not complete successfully.
+- Summarise the most likely cause from the CLI output in plain language. Common causes:
+  * The target file already exists — suggest picking a different filename or removing the existing file first.
+  * The path does not end with '.js' — schema files use the JavaScript factory function pattern; suggest correcting the extension.
+  * The parent folder does not exist — the CLI does not auto-create intermediate folders. Suggest creating the folder first.
+  * Unknown command 'schema init' — the installed RESTForge version may be older than this CLI subcommand; suggest upgrading the package.
+- Do not paste the raw stdout/stderr unless the user explicitly asks. Do not mention internal tool names.`,
+                    },
+                ],
+                isError: true, // per §3.4
+            };
+        }
+        // Derive the table name from filename (CLI applies the same rule).
+        // This is informational only — the labeled fact mirrors what the CLI will print to stdout.
+        const lastSegment = path.split(/[/\\]/).pop() ?? path;
+        const derivedTableName = lastSegment.endsWith('.js')
+            ? lastSegment.slice(0, -3)
+            : lastSegment;
+        // Branch B: success — labeled facts + fenced raw output per §3.5.
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: `Schema skeleton file created successfully.
+
+Project path: ${projectCwd}
+Target file: ${path}
+Table name (derived from filename): ${derivedTableName}
+
+--- CLI output ---
+${result.stdout}
+--- end CLI output ---
+
+For the assistant:
+- Confirm to the user that the skeleton file was created. Mention the file path and the derived table name in plain language.
+- The skeleton is a starting point only: it has minimal fields (id, code, name, is_active). Suggest opening the file and adding the actual fields, indexes, uniques, and relations that match the user's domain.
+- Use the schema catalog as ground truth when helping the user fill in the model (field types, constraints, relations, shorthand syntax).
+- After the user edits the file, suggest validating the schema next as a sanity check (without mentioning the internal tool name).
+- If the user wants several entities, this action creates one file per call. For multiple entities, invoke once per file.
+- Match the user's language.`,
+                },
+            ],
+        };
+    });
+}
+//# sourceMappingURL=dbschema-init.js.map

package/dist/tools/codegen/dbschema-init.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dbschema-init.js","sourceRoot":"","sources":["../../../src/tools/codegen/dbschema-init.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,2BAA2B,CAAC,MAAiB;IAC3D,MAAM,CAAC,YAAY,CACjB,uBAAuB,EACvB;QACE,KAAK,EAAE,iCAAiC;QACxC,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2IAgCwH;QACrI,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,uFAAuF,CAAC;YACpG,IAAI,EAAE,CAAC;iBACJ,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,uJAAuJ,CAAC;SACrK;QACD,WAAW,EAAE;YACX,KAAK,EAAE,iCAAiC;YACxC,eAAe,EAAE,KAAK,EAAE,+DAA+D;YACvF,cAAc,EAAE,KAAK,EAAG,8EAA8E;SACvG;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,IAAI,EAAE,EAAE,EAAE;QACtB,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,sFAAsF;QACtF,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;;kBAER,IAAI;;;;;gKAK0I;qBACnJ;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,6DAA6D;QAC7D,4EAA4E;QAC5E,MAAM,OAAO,GAAG,CAAC,WAAW,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,CAAC,CAAC;QAEtD,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,oEAAoE;QACpE,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;YACpB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;gBAEJ,UAAU;eACX,IAAI;WACR,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;;EAI1B,MAAM,CAAC,MAAM;;;EAGb,MAAM,CAAC,MAAM;;;;;;;;;;0GAU2F;qBAC7F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,WAAW;aAC3B,CAAC;QACJ,CAAC;QAED,mEAAmE;QACnE,2FAA2F;QAC3F,MAAM,WAAW,GAAG,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,GAAG,EAAE,IAAI,IAAI,CAAC;QACtD,MAAM,gBAAgB,GAAG,WAAW,CAAC,QAAQ,CAAC,KAAK,CAAC;YAClD,CAAC,CAAC,WAAW,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC;YAC1B,CAAC,CAAC,WAAW,CAAC;QAEhB,kEAAkE;QAClE,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;gBAEF,UAAU;eACX,IAAI;sCACmB,gBAAgB;;;EAGpD,MAAM,CAAC,MAAM;;;;;;;;;6BASc;iBAClB;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/codegen/dbschema-introspect.d.ts

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