@restforgejs/mcp-server 1.2.1 → 1.2.3

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

@@ -86,48 +86,48 @@ function buildDriftSummary(tables) {
 export function registerCodegenDbschemaDiff(server) {
     server.registerTool('codegen_dbschema_diff', {
         title: 'Diff dbschema-kit Files Against Database',
-        description: `Detect schema drift between dbschema-kit SDF files and the live database structure (read-only, bidirectional), by wrapping restforge schema diff. The CLI loads the SDF files, introspects the matching tables in the database, and reports differences in both directions: only-in-SDF (declared but missing in the database), only-in-DB (present in the database but not declared), and mismatched (present on both sides but different). Nothing is written to the database or the filesystem.
-
-EXIT CODE SEMANTICS (important):
-- Exit 0 = no drift; schema and database are in sync.
-- Exit 1 = drift detected. This is a NORMAL, meaningful result — NOT a failure. The response summarises the drift; treat it as the answer to "is my schema in sync?".
-- Exit 2 = system error (invalid config, connection failure, schema path not found, SDF load error).
-
-USE WHEN:
-- The user asks "is my schema in sync with the database?", "apakah schema saya sinkron dengan database?", "ada drift nggak?", "cek drift schema"
-- After editing SDF files — to check the impact against the live database before deciding what to apply
-- After a manual database change (e.g. an ad-hoc ALTER) — to see how far the database diverged from the SDF source
-- Before running 'codegen_dbschema_migrate' on an existing database — to know what differs first
-- The user wants a safe read-only comparison without modifying anything
-- Periodic drift audit of an environment (staging/production) against the SDF folder
-
-DO NOT USE FOR:
-- Applying the detected drift to the database -> use 'codegen_dbschema_apply', the incremental complement of this diff (additive ALTER by default; destructive changes need explicit opt-in).
-- Full CREATE/DROP deployment of a schema -> use 'codegen_dbschema_migrate' (full apply, mutates the database — a different operation from drift detection)
-- Validating SDF file correctness without a database -> use 'codegen_dbschema_validate'
-- Reverse-engineering SDF files from the database -> use 'codegen_dbschema_introspect'
-- Listing tables or describing a single table -> use 'codegen_list_tables' / 'codegen_describe_table'
-- Comparing RDF payload files against the database -> use 'codegen_diff_payload'
-
-This tool runs: npx restforge schema diff --path=<path> --config=<config> --json [--table=<name>] in the given cwd. The --json flag is always sent; the tool parses the JSON drift report (version, summary, per-table sections).
-
-Soft-delete note: the diff is soft-delete aware but non-strict. Drift in the softDelete block is reported as-is in the table's softDelete section without blocking the diff — unlike introspect, which can block on a broken soft-delete contract.
-
-Limitations:
-- The sqlite dialect is not supported by schema diff.
-- A table declared in SDF but absent in the database is reported as only-in-SDF drift, not as an error.
-
-Preconditions:
-- The project must have @restforgejs/platform installed in node_modules.
-- The config file (default 'db-connection.env') must exist and contain valid database credentials.
-- SDF files must exist at the given path. The --path flag is required by the CLI.
-
-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. "compare the schema with the database", "check for drift").
-- Drift detected is NOT an error. Present it as a factual comparison result: which tables drifted and in which direction (only-in-SDF / only-in-DB / mismatched).
-- Speak in plain language. Summarise per table; do not paste the raw JSON unless the user explicitly asks.
-- This is a read-only live comparison: the database is introspected at diff time and never modified.
+        description: `Detect schema drift between dbschema-kit SDF files and the live database structure (read-only, bidirectional), by wrapping restforge schema diff. The CLI loads the SDF files, introspects the matching tables in the database, and reports differences in both directions: only-in-SDF (declared but missing in the database), only-in-DB (present in the database but not declared), and mismatched (present on both sides but different). Nothing is written to the database or the filesystem.
+
+EXIT CODE SEMANTICS (important):
+- Exit 0 = no drift; schema and database are in sync.
+- Exit 1 = drift detected. This is a NORMAL, meaningful result — NOT a failure. The response summarises the drift; treat it as the answer to "is my schema in sync?".
+- Exit 2 = system error (invalid config, connection failure, schema path not found, SDF load error).
+
+USE WHEN:
+- The user asks "is my schema in sync with the database?", "apakah schema saya sinkron dengan database?", "ada drift nggak?", "cek drift schema"
+- After editing SDF files — to check the impact against the live database before deciding what to apply
+- After a manual database change (e.g. an ad-hoc ALTER) — to see how far the database diverged from the SDF source
+- Before running 'codegen_dbschema_migrate' on an existing database — to know what differs first
+- The user wants a safe read-only comparison without modifying anything
+- Periodic drift audit of an environment (staging/production) against the SDF folder
+
+DO NOT USE FOR:
+- Applying the detected drift to the database -> use 'codegen_dbschema_apply', the incremental complement of this diff (additive ALTER by default; destructive changes need explicit opt-in).
+- Full CREATE/DROP deployment of a schema -> use 'codegen_dbschema_migrate' (full apply, mutates the database — a different operation from drift detection)
+- Validating SDF file correctness without a database -> use 'codegen_dbschema_validate'
+- Reverse-engineering SDF files from the database -> use 'codegen_dbschema_introspect'
+- Listing tables or describing a single table -> use 'codegen_list_tables' / 'codegen_describe_table'
+- Comparing RDF payload files against the database -> use 'codegen_diff_payload'
+
+This tool runs: npx restforge schema diff --path=<path> --config=<config> --json [--table=<name>] in the given cwd. The --json flag is always sent; the tool parses the JSON drift report (version, summary, per-table sections).
+
+Soft-delete note: the diff is soft-delete aware but non-strict. Drift in the softDelete block is reported as-is in the table's softDelete section without blocking the diff — unlike introspect, which can block on a broken soft-delete contract.
+
+Limitations:
+- The sqlite dialect is not supported by schema diff.
+- A table declared in SDF but absent in the database is reported as only-in-SDF drift, not as an error.
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The config file (default 'db-connection.env') must exist and contain valid database credentials.
+- SDF files must exist at the given path. The --path flag is required by the CLI.
+
+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. "compare the schema with the database", "check for drift").
+- Drift detected is NOT an error. Present it as a factual comparison result: which tables drifted and in which direction (only-in-SDF / only-in-DB / mismatched).
+- Speak in plain language. Summarise per table; do not paste the raw JSON unless the user explicitly asks.
+- This is a read-only live comparison: the database is introspected at diff time and never modified.
 - When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
         inputSchema: {
             cwd: z
@@ -165,17 +165,17 @@ PRESENTATION GUIDANCE:
                 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 config: ${config}
-Requested schema path: ${path}
-Requested table filter: ${table ?? 'all tables'}
-
-For the assistant:
-- The user needs to install the RESTForge package before the schema can be diffed against the database.
-- Suggest installing the package first, then retry the drift check.
+                        text: `Precondition not met: the RESTForge package is not installed in this project.
+
+Project path: ${projectCwd}
+Expected location: node_modules/@restforgejs/platform
+Requested config: ${config}
+Requested schema path: ${path}
+Requested table filter: ${table ?? 'all tables'}
+
+For the assistant:
+- The user needs to install the RESTForge package before the schema can be diffed against the database.
+- Suggest installing the package first, then retry the drift check.
 - 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.`,
                     },
                 ],
@@ -211,33 +211,33 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Failed to diff schema against the database.
-
-Project path: ${projectCwd}
-Config: ${config}
-Schema path: ${path}
-Table filter: ${table ?? 'all tables'}
-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 drift check could not run. This is a system error, not a drift result.
-- Summarise the most likely cause from the CLI output in plain language. Common causes:
-  * Config file not found or invalid — suggest verifying the config path and its content.
-  * Database connection failed — suggest verifying credentials, host, and port.
-  * Schema path not found — the CLI cannot locate the path. Suggest verifying the folder or file name passed via --path.
-  * SDF load error — a schema file has invalid syntax or violates the defineModel contract. Suggest running the validate action first to surface the specific issue.
-  * Unsupported dialect — schema diff does not support sqlite. Suggest checking DB_TYPE in the config.
-  * Unknown command 'schema diff' — 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.
+                        text: `Failed to diff schema against the database.
+
+Project path: ${projectCwd}
+Config: ${config}
+Schema path: ${path}
+Table filter: ${table ?? 'all tables'}
+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 drift check could not run. This is a system error, not a drift result.
+- Summarise the most likely cause from the CLI output in plain language. Common causes:
+  * Config file not found or invalid — suggest verifying the config path and its content.
+  * Database connection failed — suggest verifying credentials, host, and port.
+  * Schema path not found — the CLI cannot locate the path. Suggest verifying the folder or file name passed via --path.
+  * SDF load error — a schema file has invalid syntax or violates the defineModel contract. Suggest running the validate action first to surface the specific issue.
+  * Unsupported dialect — schema diff does not support sqlite. Suggest checking DB_TYPE in the config.
+  * Unknown command 'schema diff' — 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 underlying issue is resolved.`,
                     },
                 ],
@@ -256,21 +256,21 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Failed to parse the schema drift report as JSON.
-
-Project path: ${projectCwd}
-Config: ${config}
-Schema path: ${path}
-Exit code: ${result.exitCode}
-Reason: ${msg}
-
---- Raw stdout ---
-${result.stdout}
---- end Raw stdout ---
-
-For the assistant:
-- The CLI returned output that is not valid JSON, so the drift result could not be read.
-- Summarise this to the user in plain language; do not paste the raw stdout unless they explicitly ask.
+                        text: `Failed to parse the schema drift report as JSON.
+
+Project path: ${projectCwd}
+Config: ${config}
+Schema path: ${path}
+Exit code: ${result.exitCode}
+Reason: ${msg}
+
+--- Raw stdout ---
+${result.stdout}
+--- end Raw stdout ---
+
+For the assistant:
+- The CLI returned output that is not valid JSON, so the drift result could not be read.
+- Summarise this to the user in plain language; do not paste the raw stdout unless they explicitly ask.
 - Suggest checking that the installed RESTForge package version is compatible. Do not mention internal tool names.`,
                     },
                 ],
@@ -292,20 +292,20 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Schema drift check completed: no drift detected.
-
-Project path: ${projectCwd}
-Config: ${config}
-Schema path: ${path}
-Table filter: ${table ?? 'all tables'}
-totalTables: ${totalTables}
-tablesWithDrift: ${tablesWithDrift}
-tablesClean: ${tablesClean}
-
-For the assistant:
-- Confirm to the user that the schema files and the database are in sync — mention the number of tables compared in plain language.
-- This was a read-only comparison; nothing in the database or the filesystem was modified.
-- No follow-up action is required. If the user expected drift, suggest double-checking that the schema path and config point at the intended files and database.
+                        text: `Schema drift check completed: no drift detected.
+
+Project path: ${projectCwd}
+Config: ${config}
+Schema path: ${path}
+Table filter: ${table ?? 'all tables'}
+totalTables: ${totalTables}
+tablesWithDrift: ${tablesWithDrift}
+tablesClean: ${tablesClean}
+
+For the assistant:
+- Confirm to the user that the schema files and the database are in sync — mention the number of tables compared in plain language.
+- This was a read-only comparison; nothing in the database or the filesystem was modified.
+- No follow-up action is required. If the user expected drift, suggest double-checking that the schema path and config point at the intended files and database.
 - Match the user's language.`,
                     },
                 ],
@@ -317,32 +317,32 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Schema drift check completed: drift detected (this is a result, not an error).
-
-Project path: ${projectCwd}
-Config: ${config}
-Schema path: ${path}
-Table filter: ${table ?? 'all tables'}
-totalTables: ${totalTables}
-tablesWithDrift: ${tablesWithDrift}
-tablesClean: ${tablesClean}
-
---- Drift summary per table ---
-${driftSummary}
---- end Drift summary ---
-
---- Drift report (JSON) ---
-${prettyJson}
---- end Drift report (JSON) ---
-
-For the assistant:
-- Present this as a factual comparison result, NOT a failure: the schema files and the database differ.
-- Summarise per drifted table in plain language: only-in-SDF means declared in the schema files but missing in the database; only-in-DB means present in the database but not declared; mismatched means present on both sides with different definitions.
-- A whole table reported as only-in-SDF fields drift usually means the table does not exist in the database yet.
-- Drift in the softDelete section is informational (non-strict) — report it as-is without treating it as a blocker.
-- Do not paste the full JSON unless the user asks; the per-table summary above is usually enough.
-- For next steps, depending on direction: additive changes can be applied incrementally via 'codegen_dbschema_apply' (preview with dryRun=true first; destructive changes need explicit user opt-in); a full re-deploy goes through the migrate action (destructive — needs explicit confirmation). When speaking to the user, describe these as actions — do not mention internal tool names.
-- This was a read-only comparison; nothing was modified.
+                    text: `Schema drift check completed: drift detected (this is a result, not an error).
+
+Project path: ${projectCwd}
+Config: ${config}
+Schema path: ${path}
+Table filter: ${table ?? 'all tables'}
+totalTables: ${totalTables}
+tablesWithDrift: ${tablesWithDrift}
+tablesClean: ${tablesClean}
+
+--- Drift summary per table ---
+${driftSummary}
+--- end Drift summary ---
+
+--- Drift report (JSON) ---
+${prettyJson}
+--- end Drift report (JSON) ---
+
+For the assistant:
+- Present this as a factual comparison result, NOT a failure: the schema files and the database differ.
+- Summarise per drifted table in plain language: only-in-SDF means declared in the schema files but missing in the database; only-in-DB means present in the database but not declared; mismatched means present on both sides with different definitions.
+- A whole table reported as only-in-SDF fields drift usually means the table does not exist in the database yet.
+- Drift in the softDelete section is informational (non-strict) — report it as-is without treating it as a blocker.
+- Do not paste the full JSON unless the user asks; the per-table summary above is usually enough.
+- For next steps, depending on direction: additive changes can be applied incrementally via 'codegen_dbschema_apply' (preview with dryRun=true first; destructive changes need explicit user opt-in); a full re-deploy goes through the migrate action (destructive — needs explicit confirmation). When speaking to the user, describe these as actions — do not mention internal tool names.
+- This was a read-only comparison; nothing was modified.
 - Match the user's language.`,
                 },
             ],

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

@@ -49,52 +49,52 @@ function describeRequest(args) {
 export function registerCodegenDbschemaTemplate(server) {
     server.registerTool('codegen_dbschema_template', {
         title: 'Browse / Preview / Generate Schema Templates',
-        description: `Access the RESTForge Schema Reference collection (87 ready-made templates spanning 30+ domains: ERP, finance, inventory, e-commerce, CRM, HR, POS, and more) by wrapping restforge schema template. Use it to browse and filter the catalog, preview a template's SDF or SQL, look up the available domains/categories/sections, and scaffold real schema files for common business tables (e.g. sales_order, inventory, customer_invoice) instead of starting from an empty skeleton.
-
-FOUR MODES:
-- LIST / BROWSE (default, no show/generate/utility flag): returns a filtered catalog of templates. Combine filters: domain (csv), table (wildcard glob like "sales*"), category, pattern, section, hasSdf, noSdf.
-- SHOW (show=true, needs a SPECIFIC table name — no wildcard): prints the template's schema. lang=sdf (default) prints the dbschema-kit factory function; lang=sql prints raw DDL. example=true adds a sample-data section (only meaningful together with show).
-- GENERATE (generate=true, needs a SPECIFIC table AND path): writes the template to the filesystem. A master-detail template writes TWO files (e.g. sales_order.js + sales_order_item.js). force=true overwrites existing destination files; without force the CLI refuses to overwrite.
-- UTILITY (stats / listDomains / listCategories / listSections): collection statistics and the lookup lists that feed the filters above.
-
-PLATFORM DEPENDENCY (important): this feature is backed by a native binary (sdf-tools.exe) that is currently WINDOWS-ONLY. On a non-Windows host, or if the binary is missing from the installed package, the CLI exits with code 3 and this tool reports that the template collection is unavailable on this platform — that is NOT a user error. In that case, author the SDF by hand (ground it with 'codegen_get_dbschema_catalog') or reverse-engineer it from an existing database with 'codegen_dbschema_introspect'.
-
-USE WHEN:
-- The user asks for an example schema, a starter for a common table, or "what tables/templates are available"
-- Pertanyaan dalam bentuk: "ada template schema untuk sales order nggak?", "buatkan schema inventory dari template", "contoh schema invoice", "template apa saja untuk domain ERP", "scaffold tabel pelanggan dari contoh"
-- The user wants to scaffold a real, fleshed-out table (sales_order, product, customer, journal_entry, ...) rather than the minimal id/code/name/is_active skeleton from 'codegen_dbschema_init'
-- Exploring the catalog by domain/category/pattern, or doing SDF gap analysis (noSdf=true)
-- The user wants to preview a template's SDF or SQL before committing it to a file
-
-DO NOT USE FOR:
-- Creating a minimal empty starter file (id/code/name/is_active only) -> use 'codegen_dbschema_init'
-- Editing an existing schema file -> use Edit/Write tools directly
-- Reverse-engineering SDF from a live database -> use 'codegen_dbschema_introspect'
-- Validating a schema file -> use 'codegen_dbschema_validate'
-- Generating DDL from an already-authored SDF -> use 'codegen_dbschema_generate_ddl'
-- Looking up defineModel syntax / field types / constraints -> use 'codegen_get_dbschema_catalog'
-
-This tool runs: npx restforge schema template [filters/mode flags] in the given cwd. Boolean flags (show, generate, stats, hasSdf, noSdf, example, force, listDomains, listCategories, listSections) are sent as bare flags only when true; string/enum flags (domain, table, category, pattern, section, lang, path, format) are sent as --flag=value when supplied.
-
-OUTPUT: the tool relays the CLI's text output as-is; it does not parse it. The native binary's --format=json is honoured by the list/stats/listDomains/listCategories/listSections modes (machine-readable JSON text) but NOT by show (which always prints schema code) or generate (which prints a written-files summary). Pass format=json only when you specifically want the JSON form of a list/utility result; otherwise the default human-readable text is easier to summarise.
-
-CLI constraints (the CLI enforces these; this tool does not pre-validate, it forwards and relays the CLI's own error):
-- show and generate require a specific table name (no wildcard).
-- generate requires path.
-- example is only meaningful together with show.
-- force only matters with generate (overwrite existing files).
-- master-detail templates generate two files.
-
-Preconditions:
-- The project must have @restforgejs/platform installed in node_modules.
-- The template feature requires the Windows-only sdf-tools.exe binary shipped with the package (exit 3 otherwise — see PLATFORM DEPENDENCY).
-
-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. "browse the schema templates", "preview the sales order template", "scaffold the table from a template").
-- Speak in plain language. Summarise list/stats output (counts, the templates relevant to the user's task); do not paste the entire table or JSON unless the user explicitly asks.
-- For generate: confirm the files that were written and their paths (a master-detail template creates two files). Suggest validating the generated schema next.
-- For the Windows-only exit 3 case: explain plainly that the ready-made template collection is not available on this platform, then offer the alternatives (author the SDF by hand with the catalog as reference, or reverse-engineer from an existing database). Do not present it as a failure of the user's request.
+        description: `Access the RESTForge Schema Reference collection (87 ready-made templates spanning 30+ domains: ERP, finance, inventory, e-commerce, CRM, HR, POS, and more) by wrapping restforge schema template. Use it to browse and filter the catalog, preview a template's SDF or SQL, look up the available domains/categories/sections, and scaffold real schema files for common business tables (e.g. sales_order, inventory, customer_invoice) instead of starting from an empty skeleton.
+
+FOUR MODES:
+- LIST / BROWSE (default, no show/generate/utility flag): returns a filtered catalog of templates. Combine filters: domain (csv), table (wildcard glob like "sales*"), category, pattern, section, hasSdf, noSdf.
+- SHOW (show=true, needs a SPECIFIC table name — no wildcard): prints the template's schema. lang=sdf (default) prints the dbschema-kit factory function; lang=sql prints raw DDL. example=true adds a sample-data section (only meaningful together with show).
+- GENERATE (generate=true, needs a SPECIFIC table AND path): writes the template to the filesystem. A master-detail template writes TWO files (e.g. sales_order.js + sales_order_item.js). force=true overwrites existing destination files; without force the CLI refuses to overwrite.
+- UTILITY (stats / listDomains / listCategories / listSections): collection statistics and the lookup lists that feed the filters above.
+
+PLATFORM DEPENDENCY (important): this feature is backed by a native binary (sdf-tools.exe) that is currently WINDOWS-ONLY. On a non-Windows host, or if the binary is missing from the installed package, the CLI exits with code 3 and this tool reports that the template collection is unavailable on this platform — that is NOT a user error. In that case, author the SDF by hand (ground it with 'codegen_get_dbschema_catalog') or reverse-engineer it from an existing database with 'codegen_dbschema_introspect'.
+
+USE WHEN:
+- The user asks for an example schema, a starter for a common table, or "what tables/templates are available"
+- Pertanyaan dalam bentuk: "ada template schema untuk sales order nggak?", "buatkan schema inventory dari template", "contoh schema invoice", "template apa saja untuk domain ERP", "scaffold tabel pelanggan dari contoh"
+- The user wants to scaffold a real, fleshed-out table (sales_order, product, customer, journal_entry, ...) rather than the minimal id/code/name/is_active skeleton from 'codegen_dbschema_init'
+- Exploring the catalog by domain/category/pattern, or doing SDF gap analysis (noSdf=true)
+- The user wants to preview a template's SDF or SQL before committing it to a file
+
+DO NOT USE FOR:
+- Creating a minimal empty starter file (id/code/name/is_active only) -> use 'codegen_dbschema_init'
+- Editing an existing schema file -> use Edit/Write tools directly
+- Reverse-engineering SDF from a live database -> use 'codegen_dbschema_introspect'
+- Validating a schema file -> use 'codegen_dbschema_validate'
+- Generating DDL from an already-authored SDF -> use 'codegen_dbschema_generate_ddl'
+- Looking up defineModel syntax / field types / constraints -> use 'codegen_get_dbschema_catalog'
+
+This tool runs: npx restforge schema template [filters/mode flags] in the given cwd. Boolean flags (show, generate, stats, hasSdf, noSdf, example, force, listDomains, listCategories, listSections) are sent as bare flags only when true; string/enum flags (domain, table, category, pattern, section, lang, path, format) are sent as --flag=value when supplied.
+
+OUTPUT: the tool relays the CLI's text output as-is; it does not parse it. The native binary's --format=json is honoured by the list/stats/listDomains/listCategories/listSections modes (machine-readable JSON text) but NOT by show (which always prints schema code) or generate (which prints a written-files summary). Pass format=json only when you specifically want the JSON form of a list/utility result; otherwise the default human-readable text is easier to summarise.
+
+CLI constraints (the CLI enforces these; this tool does not pre-validate, it forwards and relays the CLI's own error):
+- show and generate require a specific table name (no wildcard).
+- generate requires path.
+- example is only meaningful together with show.
+- force only matters with generate (overwrite existing files).
+- master-detail templates generate two files.
+
+Preconditions:
+- The project must have @restforgejs/platform installed in node_modules.
+- The template feature requires the Windows-only sdf-tools.exe binary shipped with the package (exit 3 otherwise — see PLATFORM DEPENDENCY).
+
+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. "browse the schema templates", "preview the sales order template", "scaffold the table from a template").
+- Speak in plain language. Summarise list/stats output (counts, the templates relevant to the user's task); do not paste the entire table or JSON unless the user explicitly asks.
+- For generate: confirm the files that were written and their paths (a master-detail template creates two files). Suggest validating the generated schema next.
+- For the Windows-only exit 3 case: explain plainly that the ready-made template collection is not available on this platform, then offer the alternatives (author the SDF by hand with the catalog as reference, or reverse-engineer from an existing database). Do not present it as a failure of the user's request.
 - When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
         inputSchema: {
             cwd: z
@@ -198,14 +198,14 @@ PRESENTATION GUIDANCE:
                 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 user needs to install the RESTForge package before the schema template collection can be used.
-- Suggest installing the package first, then retry.
+                        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 user needs to install the RESTForge package before the schema template collection can be used.
+- Suggest installing the package first, then retry.
 - 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.`,
                     },
                 ],
@@ -287,26 +287,26 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `The schema template collection is unavailable on this platform.
-
-Project path: ${projectCwd}
-Requested: ${requestSummary}
-Command: ${result.command}
-Exit code: 3
-
---- CLI output ---
-stdout:
-${result.stdout}
-
-stderr:
-${result.stderr}
---- end CLI output ---
-
-For the assistant:
-- This is NOT a mistake by the user and NOT a bug in the request. The template feature is backed by a native binary (sdf-tools.exe) that currently only runs on Windows; exit 3 means either the host is not Windows, or the binary is missing from the installed package.
-- Do not retry the same call — it will fail again on this host. Instead, offer the alternatives:
-  * Author the schema by hand: look up the defineModel syntax, field types, and constraints (the schema catalog is the ground truth), then create the file and validate it.
-  * Reverse-engineer the schema from an existing database table, if one already exists.
+                        text: `The schema template collection is unavailable on this platform.
+
+Project path: ${projectCwd}
+Requested: ${requestSummary}
+Command: ${result.command}
+Exit code: 3
+
+--- CLI output ---
+stdout:
+${result.stdout}
+
+stderr:
+${result.stderr}
+--- end CLI output ---
+
+For the assistant:
+- This is NOT a mistake by the user and NOT a bug in the request. The template feature is backed by a native binary (sdf-tools.exe) that currently only runs on Windows; exit 3 means either the host is not Windows, or the binary is missing from the installed package.
+- Do not retry the same call — it will fail again on this host. Instead, offer the alternatives:
+  * Author the schema by hand: look up the defineModel syntax, field types, and constraints (the schema catalog is the ground truth), then create the file and validate it.
+  * Reverse-engineer the schema from an existing database table, if one already exists.
 - Explain plainly to the user that the ready-made template collection is not available on this platform, then propose one of the alternatives above. Do not mention internal tool names.`,
                     },
                 ],
@@ -320,28 +320,28 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Failed to run the schema template command.
-
-Project path: ${projectCwd}
-Requested: ${requestSummary}
-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 template command did not complete successfully.
-- Summarise the most likely cause from the CLI output in plain language. Common causes:
-  * Usage error (exit 2) — an invalid flag combination. Recall the CLI constraints: show/generate need a specific table name (no wildcard); generate also needs path; example only works with show; an unknown enum value for category/pattern/lang/format is rejected.
-  * Binary spawn failure (exit 1) — sdf-tools.exe could not be launched; suggest re-checking the installed package integrity.
-  * For generate specifically: the destination file already exists and force was not set (the CLI refuses to overwrite) — suggest a different path or passing force=true after confirming with the user.
-  * Unknown command 'schema template' — the installed RESTForge version may be older than this CLI subcommand; suggest upgrading the package.
+                        text: `Failed to run the schema template command.
+
+Project path: ${projectCwd}
+Requested: ${requestSummary}
+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 template command did not complete successfully.
+- Summarise the most likely cause from the CLI output in plain language. Common causes:
+  * Usage error (exit 2) — an invalid flag combination. Recall the CLI constraints: show/generate need a specific table name (no wildcard); generate also needs path; example only works with show; an unknown enum value for category/pattern/lang/format is rejected.
+  * Binary spawn failure (exit 1) — sdf-tools.exe could not be launched; suggest re-checking the installed package integrity.
+  * For generate specifically: the destination file already exists and force was not set (the CLI refuses to overwrite) — suggest a different path or passing force=true after confirming with the user.
+  * Unknown command 'schema template' — 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.`,
                     },
                 ],
@@ -356,25 +356,25 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Schema template command completed successfully.
-
-Project path: ${projectCwd}
-Requested: ${requestSummary}
-${format ? `Format: ${format}\n` : ''}
---- CLI output ---
-${result.stdout}
---- end CLI output ---
-
-For the assistant:
+                    text: `Schema template command completed successfully.
+
+Project path: ${projectCwd}
+Requested: ${requestSummary}
+${format ? `Format: ${format}\n` : ''}
+--- CLI output ---
+${result.stdout}
+--- end CLI output ---
+
+For the assistant:
 ${generated
-                        ? `- Confirm to the user which files were written and their paths — the CLI output above lists each generated file. A master-detail template writes two files (the master plus its detail/line table).
-- Suggest opening the generated file(s) and then validating the schema as a sanity check (without naming the internal tool).
+                        ? `- Confirm to the user which files were written and their paths — the CLI output above lists each generated file. A master-detail template writes two files (the master plus its detail/line table).
+- Suggest opening the generated file(s) and then validating the schema as a sanity check (without naming the internal tool).
 - The generated schema is a real, fleshed-out starting point from the reference collection, not an empty skeleton; the user may still want to adjust field names/sizes to their exact domain.`
                         : show === true
-                            ? `- This is a preview only; nothing was written to the filesystem.
+                            ? `- This is a preview only; nothing was written to the filesystem.
 - Read the schema above and summarise it in plain language if the user asked a question. If they want to keep it, offer to generate it to a file (which would write the actual file).`
-                            : `- Read the output above and summarise it for the user (e.g. how many templates matched, the ones relevant to their task, or the requested list/statistics).
-- Do not paste the entire table or JSON if it is long; surface only what the user needs. If they then want a specific template, offer to preview it (show) or scaffold it to a file (generate).`}
+                            : `- Read the output above and summarise it for the user (e.g. how many templates matched, the ones relevant to their task, or the requested list/statistics).
+- Do not paste the entire table or JSON if it is long; surface only what the user needs. If they then want a specific template, offer to preview it (show) or scaffold it to a file (generate).`}
 - Match the user's language.`,
                 },
             ],

package/dist/tools/codegen/index.js

@@ -2,6 +2,7 @@ import { registerCodegenGeneratePayload } from './generate-payload.js';
 import { registerCodegenValidatePayload } from './validate-payload.js';
 import { registerCodegenDiffPayload } from './diff-payload.js';
 import { registerCodegenSyncPayload } from './sync-payload.js';
+import { registerCodegenMigratePayload } from './migrate-payload.js';
 import { registerCodegenGetFieldValidationCatalog } from './get-field-validation-catalog.js';
 import { registerCodegenGetQueryDeclarativeCatalog } from './get-query-declarative-catalog.js';
 import { registerCodegenGetDashboardCatalog } from './get-dashboard-catalog.js';
@@ -26,6 +27,7 @@ export function registerCodegenTools(server) {
     registerCodegenValidatePayload(server);
     registerCodegenDiffPayload(server);
     registerCodegenSyncPayload(server);
+    registerCodegenMigratePayload(server);
     registerCodegenGetFieldValidationCatalog(server);
     registerCodegenGetQueryDeclarativeCatalog(server);
     registerCodegenGetDashboardCatalog(server);

package/dist/tools/codegen/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/tools/codegen/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,wCAAwC,EAAE,MAAM,mCAAmC,CAAC;AAC7F,OAAO,EAAE,yCAAyC,EAAE,MAAM,oCAAoC,CAAC;AAC/F,OAAO,EAAE,kCAAkC,EAAE,MAAM,4BAA4B,CAAC;AAChF,OAAO,EAAE,6BAA6B,EAAE,MAAM,sBAAsB,CAAC;AACrE,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,uCAAuC,EAAE,MAAM,iCAAiC,CAAC;AAC1F,OAAO,EAAE,yBAAyB,EAAE,MAAM,kBAAkB,CAAC;AAC7D,OAAO,EAAE,4BAA4B,EAAE,MAAM,qBAAqB,CAAC;AACnE,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,iCAAiC,EAAE,MAAM,2BAA2B,CAAC;AAC9E,OAAO,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AACjE,OAAO,EAAE,+BAA+B,EAAE,MAAM,wBAAwB,CAAC;AACzE,OAAO,EAAE,6BAA6B,EAAE,MAAM,sBAAsB,CAAC;AACrE,OAAO,EAAE,kCAAkC,EAAE,MAAM,4BAA4B,CAAC;AAChF,OAAO,EAAE,iCAAiC,EAAE,MAAM,0BAA0B,CAAC;AAC7E,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AACjE,OAAO,EAAE,4BAA4B,EAAE,MAAM,qBAAqB,CAAC;AACnE,OAAO,EAAE,+BAA+B,EAAE,MAAM,wBAAwB,CAAC;AAEzE,MAAM,UAAU,oBAAoB,CAAC,MAAiB;IACpD,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,wCAAwC,CAAC,MAAM,CAAC,CAAC;IACjD,yCAAyC,CAAC,MAAM,CAAC,CAAC;IAClD,kCAAkC,CAAC,MAAM,CAAC,CAAC;IAC3C,6BAA6B,CAAC,MAAM,CAAC,CAAC;IACtC,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,uCAAuC,CAAC,MAAM,CAAC,CAAC;IAChD,yBAAyB,CAAC,MAAM,CAAC,CAAC;IAClC,4BAA4B,CAAC,MAAM,CAAC,CAAC;IACrC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,iCAAiC,CAAC,MAAM,CAAC,CAAC;IAC1C,2BAA2B,CAAC,MAAM,CAAC,CAAC;IACpC,+BAA+B,CAAC,MAAM,CAAC,CAAC;IACxC,6BAA6B,CAAC,MAAM,CAAC,CAAC;IACtC,kCAAkC,CAAC,MAAM,CAAC,CAAC;IAC3C,iCAAiC,CAAC,MAAM,CAAC,CAAC;IAC1C,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,2BAA2B,CAAC,MAAM,CAAC,CAAC;IACpC,4BAA4B,CAAC,MAAM,CAAC,CAAC;IACrC,+BAA+B,CAAC,MAAM,CAAC,CAAC;AAC1C,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/tools/codegen/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,6BAA6B,EAAE,MAAM,sBAAsB,CAAC;AACrE,OAAO,EAAE,wCAAwC,EAAE,MAAM,mCAAmC,CAAC;AAC7F,OAAO,EAAE,yCAAyC,EAAE,MAAM,oCAAoC,CAAC;AAC/F,OAAO,EAAE,kCAAkC,EAAE,MAAM,4BAA4B,CAAC;AAChF,OAAO,EAAE,6BAA6B,EAAE,MAAM,sBAAsB,CAAC;AACrE,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,uCAAuC,EAAE,MAAM,iCAAiC,CAAC;AAC1F,OAAO,EAAE,yBAAyB,EAAE,MAAM,kBAAkB,CAAC;AAC7D,OAAO,EAAE,4BAA4B,EAAE,MAAM,qBAAqB,CAAC;AACnE,OAAO,EAAE,0BAA0B,EAAE,MAAM,mBAAmB,CAAC;AAC/D,OAAO,EAAE,iCAAiC,EAAE,MAAM,2BAA2B,CAAC;AAC9E,OAAO,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AACjE,OAAO,EAAE,+BAA+B,EAAE,MAAM,wBAAwB,CAAC;AACzE,OAAO,EAAE,6BAA6B,EAAE,MAAM,sBAAsB,CAAC;AACrE,OAAO,EAAE,kCAAkC,EAAE,MAAM,4BAA4B,CAAC;AAChF,OAAO,EAAE,iCAAiC,EAAE,MAAM,0BAA0B,CAAC;AAC7E,OAAO,EAAE,8BAA8B,EAAE,MAAM,uBAAuB,CAAC;AACvE,OAAO,EAAE,2BAA2B,EAAE,MAAM,oBAAoB,CAAC;AACjE,OAAO,EAAE,4BAA4B,EAAE,MAAM,qBAAqB,CAAC;AACnE,OAAO,EAAE,+BAA+B,EAAE,MAAM,wBAAwB,CAAC;AAEzE,MAAM,UAAU,oBAAoB,CAAC,MAAiB;IACpD,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,6BAA6B,CAAC,MAAM,CAAC,CAAC;IACtC,wCAAwC,CAAC,MAAM,CAAC,CAAC;IACjD,yCAAyC,CAAC,MAAM,CAAC,CAAC;IAClD,kCAAkC,CAAC,MAAM,CAAC,CAAC;IAC3C,6BAA6B,CAAC,MAAM,CAAC,CAAC;IACtC,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,uCAAuC,CAAC,MAAM,CAAC,CAAC;IAChD,yBAAyB,CAAC,MAAM,CAAC,CAAC;IAClC,4BAA4B,CAAC,MAAM,CAAC,CAAC;IACrC,0BAA0B,CAAC,MAAM,CAAC,CAAC;IACnC,iCAAiC,CAAC,MAAM,CAAC,CAAC;IAC1C,2BAA2B,CAAC,MAAM,CAAC,CAAC;IACpC,+BAA+B,CAAC,MAAM,CAAC,CAAC;IACxC,6BAA6B,CAAC,MAAM,CAAC,CAAC;IACtC,kCAAkC,CAAC,MAAM,CAAC,CAAC;IAC3C,iCAAiC,CAAC,MAAM,CAAC,CAAC;IAC1C,8BAA8B,CAAC,MAAM,CAAC,CAAC;IACvC,2BAA2B,CAAC,MAAM,CAAC,CAAC;IACpC,4BAA4B,CAAC,MAAM,CAAC,CAAC;IACrC,+BAA+B,CAAC,MAAM,CAAC,CAAC;AAC1C,CAAC"}

package/dist/tools/codegen/migrate-payload.d.ts

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