@drzl/cli 4.24.4 → 4.25.0

package/dist/cli.js

@@ -19,12 +19,13 @@ import {
   loadConfig,
   matchesAny,
   matchesTable,
+  mcpOutDir,
   nearestKey,
   nestjsOutDir,
   tableAliases,
   tableFilterWarnings,
   trpcOutDir
-} from "./chunk-QNYJFUVS.js";
+} from "./chunk-J7NGXOAQ.js";
 
 // src/cli.ts
 import { qualifiedTableName as qualifiedTableName2, SchemaAnalyzer as SchemaAnalyzer2 } from "@drzl/analyzer";
@@ -336,6 +337,22 @@ function jsonSchemaOptions(g, cfg, outDir) {
   };
 }
 
+// src/mcp-options.ts
+function mcpOptions(g, cfg) {
+  return {
+    outputDir: mcpOutDir(g, cfg),
+    sdk: g.sdk,
+    serverName: g.serverName,
+    serverVersion: g.serverVersion,
+    stdio: g.stdio,
+    naming: g.naming,
+    outputHeader: g.outputHeader,
+    format: g.format,
+    importExtension: g.importExtension,
+    validation: g.validation
+  };
+}
+
 // src/nestjs-options.ts
 function nestjsOptions(g, cfg) {
   return {
@@ -487,6 +504,20 @@ var GENERATORS = [
     outputDir: (g, cfg) => graphqlOutDir(g, cfg),
     options: (g, cfg) => graphqlOptions(g, cfg)
   },
+  {
+    kind: "mcp",
+    // The one `optionalDependency` in this package's manifest, and temporarily so. A package that
+    // has never existed cannot publish through npm's trusted-publisher OIDC flow, so naming it as
+    // a hard dependency in the release that introduces it breaks `npm i @drzl/cli` for everyone
+    // until the first publish lands. `scripts/verify/stages/33-registry-deps.sh` gates that rule.
+    // It moves into `dependencies` beside the other fourteen once it is on the registry; tsup
+    // externalises all three dependency fields, so nothing about what runs changes when it does.
+    specifier: "@drzl/generator-mcp",
+    load: () => import("@drzl/generator-mcp"),
+    construct: (m, analysis) => new m.MCPGenerator(analysis),
+    outputDir: (g, cfg) => mcpOutDir(g, cfg),
+    options: (g, cfg) => mcpOptions(g, cfg)
+  },
   {
     kind: "service",
     specifier: "@drzl/generator-service",