@agiflowai/scaffold-mcp 1.0.27 → 1.2.0

package/dist/index.d.mts

@@ -2,8 +2,6 @@ import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { CallToolResult } from "@modelcontextprotocol/sdk/types.js";
 import { z } from "zod";
 import { JsonSchema } from "@composio/json-schema-to-zod";
-import "express";
-
 //#region src/server/index.d.ts
 interface ServerOptions {
   adminEnabled?: boolean;
@@ -22,7 +20,7 @@ declare enum TransportMode {
   STDIO = "stdio",
   HTTP = "http",
   SSE = "sse",
-  CLI = "cli",
+  CLI = "cli"
 }
 /**
  * Transport configuration options
@@ -268,15 +266,10 @@ declare class UseBoilerplateTool {
 //#region src/tools/UseScaffoldMethodTool.d.ts
 declare class UseScaffoldMethodTool {
   static readonly TOOL_NAME = "use-scaffold-method";
-  private static readonly TEMP_LOG_DIR;
   private fileSystemService;
   private scaffoldingMethodsService;
   private isMonolith;
   constructor(templatesPath: string, isMonolith?: boolean);
-  /**
-   * Write scaffold execution info to temp log file for hook processing
-   */
-  private writePendingScaffoldLog;
   /**
    * Get the tool definition for MCP
    */
@@ -292,6 +285,7 @@ declare class WriteToFileTool {
   static readonly TOOL_NAME = "write-to-file";
   private fileSystemService;
   constructor();
+  private resolveWorkspaceFilePath;
   /**
    * Get the tool definition for MCP
    */
@@ -713,7 +707,6 @@ declare class FileSystemService implements IFileSystemService {
 }
 //#endregion
 //#region src/services/ScaffoldConfigLoader.d.ts
-
 declare class ScaffoldConfigLoader implements IScaffoldConfigLoader {
   private fileSystem;
   private templateService;
@@ -938,11 +931,7 @@ declare class VariableReplacementService implements IVariableReplacementService
 //#region src/types/tools.d.ts
 declare const scaffoldArgsSchema: z.ZodObject<{
   appName: z.ZodString;
-}, "strip", z.ZodTypeAny, {
-  appName: string;
-}, {
-  appName: string;
-}>;
+}, z.core.$strip>;
 type ScaffoldArgs = z.infer<typeof scaffoldArgsSchema>;
 interface Tool {
   name: string;

package/dist/index.mjs

@@ -1,5 +1,4 @@
-import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, r as SseTransportHandler, t as TransportMode } from "./src-CSfEg-8i.mjs";
-import { a as ScaffoldProcessingService, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-D6BkKQyK.mjs";
-import { a as GenerateFeatureScaffoldTool, c as ScaffoldGeneratorService, i as ListBoilerplatesTool, l as BoilerplateService, n as UseScaffoldMethodTool, o as GenerateBoilerplateTool, r as UseBoilerplateTool, s as GenerateBoilerplateFileTool, t as WriteToFileTool, u as BoilerplateGeneratorService } from "./tools-t-HMGLVh.mjs";
-
-export { BoilerplateGeneratorService, BoilerplateService, FileSystemService, GenerateBoilerplateFileTool, GenerateBoilerplateTool, GenerateFeatureScaffoldTool, HttpTransportHandler, ListBoilerplatesTool, ListScaffoldingMethodsTool, ScaffoldConfigLoader, ScaffoldGeneratorService, ScaffoldProcessingService, ScaffoldService, ScaffoldingMethodsService, SseTransportHandler, StdioTransportHandler, TemplateService, TransportMode, UseBoilerplateTool, UseScaffoldMethodTool, VariableReplacementService, WriteToFileTool, createServer };
+import { a as createServer, i as StdioTransportHandler, n as HttpTransportHandler, r as SseTransportHandler, t as TransportMode } from "./src-DnVktdhD.mjs";
+import { a as ScaffoldProcessingService, i as ScaffoldService, l as TemplateService, n as ScaffoldingMethodsService, o as ScaffoldConfigLoader, r as VariableReplacementService, s as FileSystemService, t as ListScaffoldingMethodsTool } from "./ListScaffoldingMethodsTool-DxdrPlcb.mjs";
+import { a as ListBoilerplatesTool, c as GenerateBoilerplateFileTool, d as BoilerplateGeneratorService, i as UseBoilerplateTool, l as ScaffoldGeneratorService, n as UseScaffoldMethodTool, o as GenerateFeatureScaffoldTool, s as GenerateBoilerplateTool, t as WriteToFileTool, u as BoilerplateService } from "./tools-Dn5KgBUI.mjs";
+export { BoilerplateGeneratorService, BoilerplateService, FileSystemService, GenerateBoilerplateFileTool, GenerateBoilerplateTool, GenerateFeatureScaffoldTool, HttpTransportHandler, ListBoilerplatesTool, ListScaffoldingMethodsTool, ScaffoldConfigLoader, ScaffoldGeneratorService, ScaffoldProcessingService, ScaffoldService, ScaffoldingMethodsService, SseTransportHandler, StdioTransportHandler, TemplateService, TransportMode, UseBoilerplateTool, UseScaffoldMethodTool, VariableReplacementService, WriteToFileTool, createServer };

package/dist/{shared-oDx2Btq0.mjs → shared-BVYIN3Is.mjs}

@@ -1,10 +1,5 @@
 import path from "node:path";
 import fs from "node:fs/promises";
-
-//#region src/hooks/shared.ts
-const MAX_SCAFFOLD_METHODS_IN_HOOK = 5;
-const MAX_REQUIRED_VARS_IN_HOOK = 3;
-const REQUIRED_VARS_METHOD_LIMIT = 2;
 async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
 	if (!filePath || toolName.toLowerCase() !== "write") return null;
 	const absoluteFilePath = path.isAbsolute(filePath) ? filePath : path.join(cwd, filePath);
@@ -18,9 +13,9 @@ async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
 	}
 }
 function formatScaffoldMethodsHookMessage(methods, options) {
-	const maxMethods = options?.maxMethods ?? MAX_SCAFFOLD_METHODS_IN_HOOK;
-	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? REQUIRED_VARS_METHOD_LIMIT;
-	const maxRequiredVars = options?.maxRequiredVars ?? MAX_REQUIRED_VARS_IN_HOOK;
+	const maxMethods = options?.maxMethods ?? 5;
+	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? 2;
+	const maxRequiredVars = options?.maxRequiredVars ?? 3;
 	const visibleMethods = methods.slice(0, maxMethods);
 	const hiddenCount = Math.max(methods.length - visibleMethods.length, 0);
 	let message = "Before writing this new file, use `use-scaffold-method` if any of these fit:\n\n";
@@ -39,6 +34,5 @@ function formatScaffoldMethodsHookMessage(methods, options) {
 	if (hiddenCount > 0) message += `\n...and ${hiddenCount} more methods. Call \`list-scaffolding-methods\` for the full list.\n`;
 	return message.trimEnd();
 }
-
 //#endregion
-export { resolveNewFileWriteTarget as n, formatScaffoldMethodsHookMessage as t };
+export { resolveNewFileWriteTarget as n, formatScaffoldMethodsHookMessage as t };

package/dist/{shared-fkWett9D.cjs → shared-QxPXh-L-.cjs}

@@ -1,13 +1,8 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
+const require_ListScaffoldingMethodsTool = require("./ListScaffoldingMethodsTool-CYZtpU-W.cjs");
 let node_path = require("node:path");
-node_path = require_ListScaffoldingMethodsTool.__toESM(node_path);
+node_path = require_ListScaffoldingMethodsTool.__toESM(node_path, 1);
 let node_fs_promises = require("node:fs/promises");
-node_fs_promises = require_ListScaffoldingMethodsTool.__toESM(node_fs_promises);
-
-//#region src/hooks/shared.ts
-const MAX_SCAFFOLD_METHODS_IN_HOOK = 5;
-const MAX_REQUIRED_VARS_IN_HOOK = 3;
-const REQUIRED_VARS_METHOD_LIMIT = 2;
+node_fs_promises = require_ListScaffoldingMethodsTool.__toESM(node_fs_promises, 1);
 async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
 	if (!filePath || toolName.toLowerCase() !== "write") return null;
 	const absoluteFilePath = node_path.default.isAbsolute(filePath) ? filePath : node_path.default.join(cwd, filePath);
@@ -21,9 +16,9 @@ async function resolveNewFileWriteTarget(cwd, toolName, filePath) {
 	}
 }
 function formatScaffoldMethodsHookMessage(methods, options) {
-	const maxMethods = options?.maxMethods ?? MAX_SCAFFOLD_METHODS_IN_HOOK;
-	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? REQUIRED_VARS_METHOD_LIMIT;
-	const maxRequiredVars = options?.maxRequiredVars ?? MAX_REQUIRED_VARS_IN_HOOK;
+	const maxMethods = options?.maxMethods ?? 5;
+	const requiredVarsMethodLimit = options?.requiredVarsMethodLimit ?? 2;
+	const maxRequiredVars = options?.maxRequiredVars ?? 3;
 	const visibleMethods = methods.slice(0, maxMethods);
 	const hiddenCount = Math.max(methods.length - visibleMethods.length, 0);
 	let message = "Before writing this new file, use `use-scaffold-method` if any of these fit:\n\n";
@@ -42,17 +37,16 @@ function formatScaffoldMethodsHookMessage(methods, options) {
 	if (hiddenCount > 0) message += `\n...and ${hiddenCount} more methods. Call \`list-scaffolding-methods\` for the full list.\n`;
 	return message.trimEnd();
 }
-
 //#endregion
-Object.defineProperty(exports, 'formatScaffoldMethodsHookMessage', {
-  enumerable: true,
-  get: function () {
-    return formatScaffoldMethodsHookMessage;
-  }
+Object.defineProperty(exports, "formatScaffoldMethodsHookMessage", {
+	enumerable: true,
+	get: function() {
+		return formatScaffoldMethodsHookMessage;
+	}
+});
+Object.defineProperty(exports, "resolveNewFileWriteTarget", {
+	enumerable: true,
+	get: function() {
+		return resolveNewFileWriteTarget;
+	}
 });
-Object.defineProperty(exports, 'resolveNewFileWriteTarget', {
-  enumerable: true,
-  get: function () {
-    return resolveNewFileWriteTarget;
-  }
-});

package/dist/{src-DuOmlC4n.cjs → src-BG_X82dw.cjs}

@@ -1,27 +1,23 @@
-const require_ListScaffoldingMethodsTool = require('./ListScaffoldingMethodsTool-DBwZzJTA.cjs');
-const require_tools = require('./tools-DsnQImJ1.cjs');
-let __agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
-let __modelcontextprotocol_sdk_server_index_js = require("@modelcontextprotocol/sdk/server/index.js");
-let __modelcontextprotocol_sdk_types_js = require("@modelcontextprotocol/sdk/types.js");
+const require_ListScaffoldingMethodsTool = require("./ListScaffoldingMethodsTool-CYZtpU-W.cjs");
+const require_tools = require("./tools-COb9iBtt.cjs");
+let _agiflowai_aicode_utils = require("@agiflowai/aicode-utils");
+let _modelcontextprotocol_sdk_server_index_js = require("@modelcontextprotocol/sdk/server/index.js");
+let _modelcontextprotocol_sdk_types_js = require("@modelcontextprotocol/sdk/types.js");
 let zod = require("zod");
-let __modelcontextprotocol_sdk_server_stdio_js = require("@modelcontextprotocol/sdk/server/stdio.js");
-let __modelcontextprotocol_sdk_server_sse_js = require("@modelcontextprotocol/sdk/server/sse.js");
+let _modelcontextprotocol_sdk_server_stdio_js = require("@modelcontextprotocol/sdk/server/stdio.js");
+let _modelcontextprotocol_sdk_server_sse_js = require("@modelcontextprotocol/sdk/server/sse.js");
 let express = require("express");
-express = require_ListScaffoldingMethodsTool.__toESM(express);
+express = require_ListScaffoldingMethodsTool.__toESM(express, 1);
 let node_crypto = require("node:crypto");
-let __modelcontextprotocol_sdk_server_streamableHttp_js = require("@modelcontextprotocol/sdk/server/streamableHttp.js");
-
+let _modelcontextprotocol_sdk_server_streamableHttp_js = require("@modelcontextprotocol/sdk/server/streamableHttp.js");
 //#region package.json
-var version = "1.0.26";
-
+var version = "1.1.0";
 //#endregion
 //#region src/instructions/server.md?raw
 var server_default = "Use this MCP server to {% if isMonolith %}create your monolith project and add features (pages, components, services, etc.){% else %}create new projects and add features (pages, components, services, etc.){% endif %}.\n\n## Workflow:\n{% if not isMonolith %}\n1. **Creating New Project**: Use `list-boilerplates` → `use-boilerplate`\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% else %}\n1. **Creating Project**: Use `use-boilerplate` (boilerplateName auto-detected from `.toolkit/settings.yaml`)\n2. **Adding Features**: Use `list-scaffolding-methods` → `use-scaffold-method`\n{% endif %}\n\n## AI Usage Guidelines:\n{% if not isMonolith %}\n- Always call `list-boilerplates` first when creating new projects to see available options\n{% endif %}\n- Always call `list-scaffolding-methods` first when adding features to understand what's available\n- Follow the exact variable schema provided - validation will fail if required fields are missing\n{% if not isMonolith %}\n- Use kebab-case for project names (e.g., \"my-new-app\")\n{% else %}\n- In monolith mode, parameters like `boilerplateName` and `templateName` are auto-detected from `.toolkit/settings.yaml`\n- You only need to provide `variables` when calling `use-boilerplate` or `use-scaffold-method`\n{% endif %}\n- The tools automatically handle file placement, imports, and code generation\n- Check the returned JSON schemas to understand required vs optional variables\n{% if adminEnabled %}\n\n## Admin Mode (Template Generation):\n\nWhen creating custom boilerplate templates for frameworks not yet supported:\n\n1. **Create Boilerplate Configuration**: Use `generate-boilerplate` to add a new boilerplate entry to a template's scaffold.yaml\n   - Specify template name, boilerplate name, description, target folder, and variable schema\n   - This creates the scaffold.yaml structure following the nextjs-15 pattern\n   - Optional: Add detailed instruction about file purposes and design patterns\n\n2. **Create Feature Configuration**: Use `generate-feature-scaffold` to add a new feature entry to a template's scaffold.yaml\n   - Specify template name, feature name, generator, description, and variable schema\n   - This creates the scaffold.yaml structure for feature scaffolds (pages, components, etc.)\n   - Optional: Add detailed instruction about file purposes and design patterns\n   - Optional: Specify patterns to match existing files this feature works with\n\n3. **Create Template Files**: Use `generate-boilerplate-file` to create the actual template files\n   - Create files referenced in the boilerplate's or feature's includes array\n   - Use {{ variableName }} syntax for Liquid variable placeholders\n   - Can copy from existing source files or provide content directly\n   - Files automatically get .liquid extension\n\n4. **Test the Template**: Use `list-boilerplates`/`list-scaffolding-methods` and `use-boilerplate`/`use-scaffold-method` to verify your template works\n\nExample workflow for boilerplate:\n```\n1. generate-boilerplate { templateName: \"react-vite\", boilerplateName: \"scaffold-vite-app\", ... }\n2. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"package.json\", content: \"...\" }\n3. generate-boilerplate-file { templateName: \"react-vite\", filePath: \"src/App.tsx\", content: \"...\" }\n4. list-boilerplates (verify it appears)\n5. use-boilerplate { boilerplateName: \"scaffold-vite-app\", variables: {...} }\n```\n\nExample workflow for feature:\n```\n1. generate-feature-scaffold { templateName: \"nextjs-15\", featureName: \"scaffold-nextjs-component\", generator: \"componentGenerator.ts\", ... }\n2. generate-boilerplate-file { templateName: \"nextjs-15\", filePath: \"src/components/Component.tsx\", content: \"...\" }\n3. list-scaffolding-methods (verify it appears)\n4. use-scaffold-method { scaffoldName: \"scaffold-nextjs-component\", variables: {...} }\n```\n{% endif %}\n";
-
 //#endregion
 //#region src/instructions/prompts/generate-boilerplate.md?raw
 var generate_boilerplate_default = "{% if promptAsSkill %}---\nname: generate-boilerplate\ndescription: Create a new boilerplate template configuration for scaffolding new projects. Use this skill when the user wants to define a reusable project template (e.g., React app, Express API, Next.js starter) that can be used to bootstrap future projects. This is an admin/developer tool for creating the template definitions themselves, not for using existing templates. It generates scaffold.yaml configuration and template files with Liquid syntax for variable substitution.\n---\n\n{% endif %}You are helping create a new boilerplate template configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   - Framework/technology (e.g., \"React Vite\", \"Express API\", \"Next.js 15\")\n   - Template name (kebab-case, e.g., \"react-vite\", \"nextjs-15\")\n   - Boilerplate name (prefixed with \"scaffold-\", e.g., \"scaffold-vite-app\")\n   {% if not isMonolith %}- Target folder (e.g., \"apps\", \"packages\"){% else %}- Target folder (defaults to \".\" for monolith mode){% endif %}\n   - Project type (app, library, service, etc.)\n   - Required variables (at minimum: appName or packageName)\n   - Files to include in the template\n\n2. **Use MCP Tools** in order:\n   - `generate-boilerplate` - Creates the boilerplate configuration\n   - `generate-boilerplate-file` - Creates each template file\n   {% if not isMonolith %}- `list-boilerplates` - Verify it appears{% endif %}\n   - `use-boilerplate` - Test the boilerplate\n\nImportant:\n- Template naming: Use kebab-case (e.g., \"react-vite\", \"express-api\")\n- Boilerplate naming: Prefix with \"scaffold-\" (e.g., \"scaffold-vite-app\")\n{% if not isMonolith %}- Target folder: \"apps\" for applications, \"packages\" for libraries{% else %}- Target folder: \".\" for monolith projects (creates files at workspace root){% endif %}\n- Include files explicitly - avoid wildcards\n- Template syntax: use {{ variableName }}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should be a comprehensive multi-paragraph overview (3-5 sentences):\n- Paragraph 1: Core technology stack and primary value proposition\n- Paragraph 2: Target use cases and ideal project types\n- Paragraph 3: Key integrations or special features (if applicable)\n\nExample:\n\"A modern React SPA template powered by Vite for lightning-fast HMR, featuring TanStack Router for type-safe routing and TanStack Query for server state management.\nPerfect for building data-driven dashboards, admin panels, and interactive web applications requiring client-side routing and real-time data synchronization.\n\nIncludes Agiflow Config Management System integration with systematic environment variable naming (VITE_{CATEGORY}_{SUBCATEGORY}_{PROPERTY}) and auto-generated configuration templates for cloud deployment.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should be a detailed multi-section guide that helps AI understand the codebase:\n\n1. **File purposes** section: List each major file/directory with its purpose\n   Format: \"- path/to/file: Description of what this file does\"\n\n2. **How to use the scaffolded code** section: Step-by-step workflows\n   Format: Numbered list with specific examples\n   - How to add routes/pages\n   - How to fetch data\n   - How to handle authentication\n   - How to configure environment variables\n\n3. **Design patterns to follow** section: Key architectural decisions\n   Format: \"- Pattern Name: Explanation and when to use it\"\n   - Routing patterns\n   - State management patterns\n   - Data fetching patterns\n   - Error handling patterns\n   - Performance optimization patterns\n\nExample structure:\n\"[Framework] application template with [key technologies].\n\nFile purposes:\n- package.json: NPM package configuration with [framework] and dependencies\n- src/main.tsx: Application entry point with [setup details]\n- src/routes/: Route definitions following [pattern]\n[... list all major files ...]\n\nHow to use the scaffolded code:\n1. Routes: Create new routes by [specific instructions with example]\n2. Data Fetching: Use [specific pattern] for [use case]\n3. Authentication: Use [specific components/modules] for user management\n[... numbered steps for common tasks ...]\n\nDesign patterns to follow:\n- File-based Routing: Use directory structure in src/routes/ to define URL paths\n- Type-safe Routes: Leverage [framework] type inference for params\n- State Management: Use [library] for server state, [library] for client state\n[... list key patterns with explanations ...]\"\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
-
 //#endregion
 //#region src/prompts/GenerateBoilerplatePrompt.ts
 /**
@@ -77,11 +73,9 @@ var GenerateBoilerplatePrompt = class GenerateBoilerplatePrompt {
 		}];
 	}
 };
-
 //#endregion
 //#region src/instructions/prompts/generate-feature-scaffold.md?raw
 var generate_feature_scaffold_default = "{% if promptAsSkill %}---\nname: generate-feature-scaffold\ndescription: Create a new feature scaffold configuration for adding features to existing projects. Use this skill when the user wants to define a reusable feature template (e.g., page, component, service, API route) that can be used to add functionality to projects of a specific type. This is an admin/developer tool for creating the feature scaffold definitions themselves, not for using existing scaffolds. It generates feature configurations in scaffold.yaml and template files with Liquid syntax and conditional includes.\n---\n\n{% endif %}You are helping create a new feature scaffold configuration using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task:\n\n1. **Gather Information**: Ask for any missing details:\n   {% if not isMonolith %}- Template name (e.g., \"nextjs-15\", \"react-vite\"){% else %}- Template name (will be auto-detected from `.toolkit/settings.yaml`){% endif %}\n   - Feature name (prefixed with \"scaffold-\", e.g., \"scaffold-nextjs-page\")\n   - Feature type (page, component, service, etc.)\n   - Variables needed\n   - Files to include\n\n2. **Use MCP Tools** in order:\n   - `generate-feature-scaffold` - Creates the feature configuration\n   - `generate-boilerplate-file` - Creates each template file\n   - `list-scaffolding-methods` - Verify it appears\n   - `use-scaffold-method` - Test the feature\n\nImportant:\n- Feature names: prefix with \"scaffold-\"\n- Conditional includes: use \"file.tsx?withLayout=true\"\n- Template syntax: use {{ variableName }}\n{% if isMonolith %}- Template name will be auto-detected from `.toolkit/settings.yaml`{% endif %}\n\n**Description Field Guidelines (CRITICAL)**:\nThe description should explain what the feature scaffold generates (2-3 sentences):\n- Sentence 1: What type of code it generates (component, page, service, etc.)\n- Sentence 2: Key features or capabilities included\n- Sentence 3: Primary use cases or when to use it\n\nExample:\n\"Generate a new service class for TypeScript libraries following best practices. Creates a service class with interface, implementation, and unit tests. Perfect for creating reusable service modules with dependency injection patterns.\"\n\n**Instruction Field Guidelines (CRITICAL)**:\nThe instruction should provide specific guidance for using the generated feature:\n\n1. **Pattern explanation**: Describe the architectural pattern used\n2. **File organization**: Where files should be placed\n3. **Naming conventions**: How to name things (PascalCase, camelCase, etc.)\n4. **Usage guidelines**: How to use the generated code\n5. **Testing approach**: How to test the feature\n\nExample structure:\n\"[Feature type] follow a [pattern name] pattern with [key characteristics].\n[Explanation of how it works and integrates with the project].\nPlace [files] in [directory].\nFor [features with X], define [Y] in [Z] for better separation of concerns.\n[Feature names] should be [case style] and [suffix/prefix rules].\nWrite comprehensive [tests/docs] for all [public methods/exports].\"\n\nKeep it concise but informative - focus on the patterns and conventions that AI needs to understand to work with the generated code effectively.\n\nTemplate File Content Guidelines:\n- Keep content MINIMAL and business-agnostic\n- Focus on structure and patterns, not business logic\n- Use placeholder/generic examples only\n- Include essential boilerplate code only\n- Let AI fill in specific logic later\n- Add clear headers with design patterns and coding standards\n";
-
 //#endregion
 //#region src/prompts/GenerateFeatureScaffoldPrompt.ts
 /**
@@ -137,11 +131,9 @@ var GenerateFeatureScaffoldPrompt = class GenerateFeatureScaffoldPrompt {
 		}];
 	}
 };
-
 //#endregion
 //#region src/instructions/prompts/scaffold-application.md?raw
 var scaffold_application_default = "{% if promptAsSkill %}---\nname: scaffold-application\ndescription: Create a new application or project from a boilerplate template. Use this skill when the user wants to start a new project, create a new app, or bootstrap a new codebase from scratch. This skill lists available boilerplate templates (React, Next.js, Express, etc.), gathers required configuration variables, generates the complete project structure, and provides guidance on next steps including adding features.\n---\n\n{% endif %}You are helping create a new {% if isMonolith %}monolith application{% else %}application{% endif %} using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}\nYour task is to scaffold a new application by following this workflow:\n\n## Step 1: {% if isMonolith %}Prepare to Create Application{% else %}List Available Boilerplates{% endif %}\n{% if isMonolith %}You will use the `use-boilerplate` tool to create your monolith application. The boilerplate name will be auto-detected from your `.toolkit/settings.yaml` file (or legacy `toolkit.yaml` if present).{% else %}Use the `list-boilerplates` tool to see all available project templates.\n\n**What to look for:**\n- Boilerplate name (e.g., \"scaffold-nextjs-app\", \"scaffold-vite-app\")\n- Description of what the boilerplate creates\n- Target folder where projects will be created (e.g., \"apps\", \"packages\")\n- Required and optional variables in the variables_schema{% endif %}\n\n## Step 2: Gather Required Information\nBased on the {% if isMonolith %}`.toolkit/settings.yaml` sourceTemplate{% else %}selected boilerplate's variables_schema{% endif %}, collect:\n{% if not isMonolith %}- **Project name**: Must be kebab-case (e.g., \"my-new-app\", not \"MyNewApp\")\n{% endif %}- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `appName` or `packageName`: The project name (kebab-case)\n- `description`: Brief description of what the project does\n- `author`: Author name\n\n## Step 3: Execute the Boilerplate\nUse the `use-boilerplate` tool with:\n{% if not isMonolith %}- `boilerplateName`: Exact name from list-boilerplates response\n{% endif %}- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"boilerplateName\": \"scaffold-nextjs-app\",\n{% endif %}  \"variables\": {\n    \"appName\": \"my-dashboard\",\n    \"description\": \"Admin dashboard for managing users\",\n    \"author\": \"John Doe\"\n  }\n}\n```\n\n## Important Guidelines:\n{% if not isMonolith %}- **Always call `list-boilerplates` first** to see available options and their schemas{% else %}- The boilerplate name is auto-detected from `.toolkit/settings.yaml` (or legacy `toolkit.yaml`){% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n{% if not isMonolith %}- **Use kebab-case for project names** (e.g., \"user-dashboard\", not \"UserDashboard\")\n- The tool will create the project in the appropriate directory automatically{% else %}- The tool will create files at the workspace root{% endif %}\n- After creation, inform the user {% if isMonolith %}what files were created{% else %}where the project was created{% endif %}\n\n## Step 4: Review and Add Features (If Needed)\nAfter the boilerplate is created, **consider if additional features are needed**:\n1. **READ** the generated {% if isMonolith %}application{% else %}project{% endif %} structure to understand what was created\n2. **REVIEW** the user's request to see if they asked for specific features (e.g., \"with tool for X\", \"with prompt for Y\")\n3. **If features are needed**:\n   - Use `list-scaffolding-methods`{% if not isMonolith %} with the new project path{% endif %}\n   - Use `use-scaffold-method` to add tools, services, prompts, etc.\n   - **IMPLEMENT** the actual logic in the scaffolded feature files\n   - **REMOVE the `// @scaffold-generated` marker** from each file after implementing it (see below)\n   - **REGISTER** the features in `src/server/index.ts`\n4. **Install dependencies**: Remind user to run `pnpm install`\n5. **Report** the complete setup including any features added\n\n## Scaffold Marker — Remove After Implementing\nGenerated `.ts`/`.tsx`/`.js`/`.jsx` files contain `// @scaffold-generated` at the top. This comment flags unimplemented boilerplate files.\n\n**You MUST delete this line once a file is fully implemented.** Leaving it in place marks the file as a \"phantom\" — a scaffolded file whose logic was never written. The marker is checked at session boundaries to catch files that were accidentally left as empty templates.\n\n## Example Workflow:\n{% if not isMonolith %}1. Call `list-boilerplates` → See available templates\n2. Ask user which template to use (or infer from request)\n3. Collect required variables based on schema\n4. Call `use-boilerplate` with boilerplateName and variables{% else %}1. Collect required variables based on the monolith template's variables_schema from `.toolkit/settings.yaml`\n2. Call `use-boilerplate` with variables (boilerplateName auto-detected){% endif %}\n5. **Review if user requested specific features (tools, prompts, etc.)**\n6. **If features needed**: Add them using `list-scaffolding-methods` and `use-scaffold-method`\n7. **READ and IMPLEMENT** the scaffolded feature files with actual logic\n8. **REMOVE `// @scaffold-generated`** from each file once implemented\n9. Report success and next steps to the user\n";
-
 //#endregion
 //#region src/prompts/ScaffoldApplicationPrompt.ts
 /**
@@ -197,11 +189,9 @@ var ScaffoldApplicationPrompt = class ScaffoldApplicationPrompt {
 		}];
 	}
 };
-
 //#endregion
 //#region src/instructions/prompts/scaffold-feature.md?raw
 var scaffold_feature_default = "{% if promptAsSkill %}---\nname: scaffold-feature\ndescription: Add a new feature to an existing project such as service, route, page, component, or API endpoint. Use this skill when the user wants to add functionality to an existing codebase using predefined scaffolding templates. This skill lists available scaffolding methods for the project's template type, gathers required variables, generates boilerplate files, and guides implementation of the actual business logic.\n---\n\n{% endif %}You are helping add a new feature to an existing project using the scaffold-mcp MCP tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}{% if projectPath %}Project path: {{ projectPath }}\n{% endif %}\nYour task is to scaffold a new feature by following this workflow:\n\n## Step 1: Identify the Project\nDetermine the project path where the feature will be added:\n- If projectPath is provided, use it\n- Otherwise, ask the user or infer from context (e.g., \"apps/my-app\", \"packages/my-lib\")\n{% if isMonolith %}- In monolith mode, you can use the current working directory (no projectPath needed){% else %}- The path should point to a directory containing a `project.json` file{% endif %}\n\n## Step 2: List Available Scaffolding Methods\nUse the `list-scaffolding-methods` tool{% if not isMonolith %} with the projectPath{% endif %}.\n\n**What to look for:**\n- Feature name (e.g., \"scaffold-nextjs-page\", \"scaffold-react-component\")\n- Description of what files/code it generates\n- Required and optional variables in the variables_schema\n- The template type (derived from project's sourceTemplate)\n\n**Example:**\n```json\n{% if isMonolith %}{}{% else %}{\n  \"projectPath\": \"apps/my-dashboard\"\n}{% endif %}\n```\n\n## Step 3: Gather Required Information\nBased on the selected scaffolding method's variables_schema, collect:\n- **Feature-specific variables**: Name, path, type, etc.\n- **Required variables**: All variables marked as required: true\n- **Optional variables**: Variables with required: false (ask user if needed)\n\nCommon variables:\n- `componentName` / `pageName` / `serviceName`: Name in PascalCase\n- `componentPath` / `pagePath`: Where to place the file (may use kebab-case)\n- Boolean flags: `withTests`, `withLayout`, `withStyles`, etc.\n\n## Step 4: Execute the Scaffolding Method\nUse the `use-scaffold-method` tool with:\n{% if not isMonolith %}- `projectPath`: Same path from step 1\n{% endif %}- `scaffold_feature_name`: Exact name from list-scaffolding-methods response\n- `variables`: Object matching the variables_schema exactly\n\n**Example:**\n```json\n{\n{% if not isMonolith %}  \"projectPath\": \"apps/my-dashboard\",\n{% endif %}  \"scaffold_feature_name\": \"scaffold-nextjs-page\",\n  \"variables\": {\n    \"pageName\": \"UserProfile\",\n    \"pagePath\": \"user/profile\",\n    \"withLayout\": true,\n    \"withTests\": false\n  }\n}\n```\n\n## Important Guidelines:\n- **Always call `list-scaffolding-methods` first**{% if not isMonolith %} with the projectPath{% endif %}\n- **Use exact variable names** from the schema (case-sensitive)\n- **Provide all required variables** - the tool will fail if any are missing\n- **Follow naming conventions**:\n  - Component/Page/Service names: PascalCase (e.g., \"UserProfile\")\n  - File paths: kebab-case or as specified in schema (e.g., \"user/profile\")\n- **Conditional files**: Files with `?condition=true` are only included when the variable is true\n- The tool will create files in the appropriate locations automatically\n- After creation, inform the user what files were created\n\n## Step 5: Review and Implement Generated Files\nAfter scaffolding completes, **you MUST**:\n1. **READ** all generated files to understand their structure\n2. **IMPLEMENT** the actual business logic:\n   - Replace TODO comments with real code\n   - Replace template placeholders with actual implementation\n   - Add the specific functionality described in the user's request\n3. **REMOVE the `// @scaffold-generated` marker** from each file after you finish implementing it:\n   - Generated `.ts`/`.tsx`/`.js`/`.jsx` files will have `// @scaffold-generated` at the top\n   - This marker flags files that still contain unimplemented boilerplate\n   - **Delete this comment line** once a file is fully implemented\n   - Leaving the marker in place signals that the file is a \"phantom\" — unimplemented boilerplate\n4. **REGISTER** the feature in appropriate files:\n   - Import and register tools in `src/server/index.ts`\n   - Export new modules from `index.ts` files\n   - Update any necessary configuration files\n5. **TEST** to ensure the implementation works correctly\n6. **DO NOT SKIP** this step - scaffolded files are templates that need actual code\n\n## Example Workflow:\n1. Identify project path (provided or ask user){% if not isMonolith %}\n2. Call `list-scaffolding-methods` → See available features for this project{% else %}\n2. Call `list-scaffolding-methods` → See available features for your template{% endif %}\n3. Ask user which feature to add (or infer from request)\n4. Collect required variables based on schema\n5. Call `use-scaffold-method` with {% if not isMonolith %}projectPath, {% endif %}scaffold_feature_name, and variables\n6. **READ the generated files and IMPLEMENT the actual logic**\n7. **REMOVE `// @scaffold-generated` from each file once implemented**\n8. **REGISTER the feature in server/index.ts and other config files**\n9. Report success and list created files with implementation details\n";
-
 //#endregion
 //#region src/prompts/ScaffoldFeaturePrompt.ts
 /**
@@ -263,11 +253,9 @@ var ScaffoldFeaturePrompt = class ScaffoldFeaturePrompt {
 		}];
 	}
 };
-
 //#endregion
 //#region src/instructions/prompts/sync-template-patterns.md?raw
 var sync_template_patterns_default = "{% if promptAsSkill %}---\nname: sync-template-patterns\ndescription: Update scaffold template files when design patterns have changed and there are discrepancies between templates and current coding standards. Use this skill when architect.yaml or RULES.yaml have been updated and existing .liquid template files need to be brought in line with the new patterns.\n---\n\n{% endif %}You are helping synchronize scaffold template files with the latest design patterns using architect-mcp and scaffold-mcp tools.\n\n{% if request %}User request: {{ request }}\n{% endif %}{% if templateName %}Template to sync: {{ templateName }}\n{% endif %}{% if filePath %}Focus on file type: {{ filePath }}\n{% endif %}\nYour task is to detect discrepancies between current design patterns and scaffold template files, then update the templates to match.\n\n## Step 1: Gather Context\n\nDetermine scope:\n- If `templateName` is provided, scope the work to that template\n- If `filePath` is provided, focus on templates that generate files matching that path pattern\n- Otherwise, ask the user which template or file type to update\n\n{% if not isMonolith %}Use `list-boilerplates` and `list-scaffolding-methods` to discover available templates and their file includes.{% else %}Use `list-scaffolding-methods` to discover available features and their file includes.{% endif %}\n\n## Step 2: Get Current Design Patterns\n\nFor each file type the template generates, use `get-file-design-pattern` from architect-mcp:\n\n```\nget-file-design-pattern({ file_path: \"<path matching the template's target file>\" })\n```\n\n**What to capture from the response:**\n- `must_do` rules — patterns that MUST appear in generated code\n- `must_not_do` rules — anti-patterns to eliminate from templates\n- `should_do` rules — best practices to incorporate\n- Code examples showing the expected structure\n- Naming conventions and architectural decisions\n\n**Important**: Use the TARGET file path (what the template generates), not the `.liquid` template file path.\nFor example, if a template generates `src/tools/MyTool.ts`, call `get-file-design-pattern` with `src/tools/ExistingTool.ts`.\n\n## Step 3: Read Existing Template Files\n\nFor each `.liquid` template file that corresponds to the file types you checked:\n- Read the current template content\n- Note what patterns, imports, class structures, and boilerplate it contains\n- Identify the Liquid variables in use (e.g., `{{ toolName }}`, `{{ serviceName }}`)\n\nTemplate files live in the templates directory under the template name folder with `.liquid` extension\n(e.g., `templates/nextjs-15/src/tools/Tool.ts.liquid`).\n\n## Step 4: Identify Discrepancies\n\nCompare template content against the design patterns. Look for:\n\n**Critical discrepancies (must fix):**\n- Missing required imports or base classes (`must_do` violations)\n- Presence of forbidden patterns (`must_not_do` violations)\n- Wrong class/function structure that contradicts current patterns\n- Outdated error handling, typing, or interface patterns\n\n**Important discrepancies (should fix):**\n- Missing `should_do` best practices\n- Outdated code examples in template headers\n- Stale design pattern documentation in the file header comment\n\n**Document each discrepancy before making changes:**\n- Which template file is affected\n- What the current template does\n- What the design pattern requires\n- What change is needed\n\n## Step 5: Update Template Files\n\nFor each discrepancy, use `generate-boilerplate-file` to update the template:\n\n```json\n{\n  {% if not isMonolith %}\"templateName\": \"<the template name>\",{% endif %}\n  \"filePath\": \"<relative path without .liquid extension>\",\n  \"content\": \"<updated template content with Liquid variables preserved>\",\n  \"header\": \"<updated design pattern summary reflecting the new patterns>\"\n}\n```\n\n**Critical rules when updating templates:**\n- **Preserve all Liquid variables** — `{{ variableName }}`, `{% if condition %}`, filter chains like `{{ name | pascalCase }}` must remain intact\n- **Keep templates minimal and business-agnostic** — structural/boilerplate code only, not specific logic\n- **Update the header comment** to reflect the new design patterns, coding standards, and things to avoid\n- **Do NOT hardcode business logic** — use placeholder examples only\n- **Do NOT overwrite variables with literals** — `{{ toolName }}` must never become a hardcoded string\n\n## Step 6: Update scaffold.yaml Instruction (If Needed)\n\nIf the design pattern changes affect the architectural guidance documented in the boilerplate/feature `instruction` field:\n\n1. Retrieve the current instruction via `list-boilerplates` or `list-scaffolding-methods`\n2. Update the entry using `generate-boilerplate` or `generate-feature-scaffold` with the revised `instruction`\n\n## Step 7: Verify\n\nAfter updating:\n1. Confirm all `must_do` patterns are present in the updated template\n2. Confirm all `must_not_do` patterns are removed\n3. Confirm Liquid syntax is valid (variables and tags intact)\n4. Optionally run `use-scaffold-method` or `use-boilerplate` to generate a sample and review output\n\n## Important Guidelines\n\n- **One file at a time** — work through discrepancies file by file\n- **Explain each change** — tell the user what was outdated and what you updated, and why\n- **Preserve variable placeholders** — never replace `{{ toolName }}` with a literal string\n- **Be conservative** — only change what the design patterns explicitly require\n- **Report skipped files** — if a template file has no discrepancies, say so explicitly\n\n## Example Workflow\n\n{% if not isMonolith %}1. Call `list-scaffolding-methods` with `{ \"templateName\": \"nextjs-15\" }` to see features and their includes\n{% else %}1. Call `list-scaffolding-methods` to see available features and their includes\n{% endif %}2. For each feature's included files, call `get-file-design-pattern` with a matching real file path\n3. Read the corresponding `.liquid` template files\n4. Document all discrepancies found\n5. Call `generate-boilerplate-file` for each file that needs updating\n6. Report a summary: which files were updated, what changed, and why\n";
-
 //#endregion
 //#region src/prompts/SyncTemplatePatterns.ts
 const syncTemplatePatternsPromptOptionsSchema = zod.z.object({
@@ -328,7 +316,6 @@ var SyncTemplatePatternsPrompt = class SyncTemplatePatternsPrompt {
 		}
 	}
 };
-
 //#endregion
 //#region src/server/index.ts
 const TOOL_CAPABILITIES_META_KEY = "agiflowai/capabilities";
@@ -343,7 +330,7 @@ function withCapabilities(definition, capabilities) {
 }
 function createServer(options = {}) {
 	const { adminEnabled = false, isMonolith = false, promptAsSkill = false, fallbackTool, fallbackToolConfig } = options;
-	const templatesPath = __agiflowai_aicode_utils.TemplatesManagerService.findTemplatesPathSync();
+	const templatesPath = _agiflowai_aicode_utils.TemplatesManagerService.findTemplatesPathSync();
 	if (!templatesPath) throw new Error("Templates folder not found. Please create a \"templates\" folder in your workspace root, or specify \"templatesPath\" in toolkit.yaml to point to your templates directory.");
 	const listBoilerplatesTool = !isMonolith ? new require_tools.ListBoilerplatesTool(templatesPath, isMonolith) : null;
 	const useBoilerplateTool = !isMonolith ? new require_tools.UseBoilerplateTool(templatesPath, isMonolith) : null;
@@ -379,7 +366,7 @@ function createServer(options = {}) {
 		fallbackTool,
 		fallbackToolConfig
 	});
-	const server = new __modelcontextprotocol_sdk_server_index_js.Server({
+	const server = new _modelcontextprotocol_sdk_server_index_js.Server({
 		name: "scaffold-mcp",
 		version
 	}, {
@@ -389,7 +376,7 @@ function createServer(options = {}) {
 			prompts: {}
 		}
 	});
-	server.setRequestHandler(__modelcontextprotocol_sdk_types_js.ListToolsRequestSchema, async () => {
+	server.setRequestHandler(_modelcontextprotocol_sdk_types_js.ListToolsRequestSchema, async () => {
 		try {
 			const tools = [
 				withCapabilities(listScaffoldingMethodsTool.getDefinition(), [
@@ -442,7 +429,7 @@ function createServer(options = {}) {
 			throw new Error(`Failed to list tools: ${error instanceof Error ? error.message : String(error)}`);
 		}
 	});
-	server.setRequestHandler(__modelcontextprotocol_sdk_types_js.CallToolRequestSchema, async (request) => {
+	server.setRequestHandler(_modelcontextprotocol_sdk_types_js.CallToolRequestSchema, async (request) => {
 		const { name, arguments: args } = request.params;
 		try {
 			if (name === require_tools.ListBoilerplatesTool.TOOL_NAME) {
@@ -473,7 +460,7 @@ function createServer(options = {}) {
 			throw new Error(`Tool '${name}' execution failed: ${error instanceof Error ? error.message : String(error)}`);
 		}
 	});
-	server.setRequestHandler(__modelcontextprotocol_sdk_types_js.ListPromptsRequestSchema, async () => {
+	server.setRequestHandler(_modelcontextprotocol_sdk_types_js.ListPromptsRequestSchema, async () => {
 		try {
 			const prompts = [scaffoldApplicationPrompt.getDefinition(), scaffoldFeaturePrompt.getDefinition()];
 			if (adminEnabled) {
@@ -486,7 +473,7 @@ function createServer(options = {}) {
 			throw new Error(`Failed to list prompts: ${error instanceof Error ? error.message : String(error)}`);
 		}
 	});
-	server.setRequestHandler(__modelcontextprotocol_sdk_types_js.GetPromptRequestSchema, async (request) => {
+	server.setRequestHandler(_modelcontextprotocol_sdk_types_js.GetPromptRequestSchema, async (request) => {
 		const { name, arguments: args } = request.params;
 		try {
 			if (name === ScaffoldApplicationPrompt.PROMPT_NAME) return { messages: scaffoldApplicationPrompt.getMessages(args) };
@@ -510,7 +497,6 @@ function createServer(options = {}) {
 	});
 	return server;
 }
-
 //#endregion
 //#region src/transports/stdio.ts
 /**
@@ -524,7 +510,7 @@ var StdioTransportHandler = class {
 		this.server = server;
 	}
 	async start() {
-		this.transport = new __modelcontextprotocol_sdk_server_stdio_js.StdioServerTransport();
+		this.transport = new _modelcontextprotocol_sdk_server_stdio_js.StdioServerTransport();
 		await this.server.connect(this.transport);
 		console.error("Scaffolding MCP server started on stdio");
 	}
@@ -535,7 +521,6 @@ var StdioTransportHandler = class {
 		}
 	}
 };
-
 //#endregion
 //#region src/transports/sse.ts
 /**
@@ -608,7 +593,7 @@ var SseTransportHandler = class {
 	async handleSseConnection(_req, res) {
 		try {
 			const mcpServer = this.serverFactory();
-			const transport = new __modelcontextprotocol_sdk_server_sse_js.SSEServerTransport("/messages", res);
+			const transport = new _modelcontextprotocol_sdk_server_sse_js.SSEServerTransport("/messages", res);
 			this.sessionManager.setSession(transport.sessionId, transport, mcpServer);
 			res.on("close", () => {
 				this.sessionManager.deleteSession(transport.sessionId);
@@ -677,7 +662,6 @@ var SseTransportHandler = class {
 		return this.config.host;
 	}
 };
-
 //#endregion
 //#region src/transports/http.ts
 /**
@@ -753,13 +737,13 @@ var HttpTransportHandler = class {
 		const sessionId = req.headers["mcp-session-id"];
 		let transport;
 		if (sessionId && this.sessionManager.hasSession(sessionId)) transport = this.sessionManager.getSession(sessionId).transport;
-		else if (!sessionId && (0, __modelcontextprotocol_sdk_types_js.isInitializeRequest)(req.body)) {
+		else if (!sessionId && (0, _modelcontextprotocol_sdk_types_js.isInitializeRequest)(req.body)) {
 			const mcpServer = this.serverFactory();
-			transport = new __modelcontextprotocol_sdk_server_streamableHttp_js.StreamableHTTPServerTransport({
+			transport = new _modelcontextprotocol_sdk_server_streamableHttp_js.StreamableHTTPServerTransport({
 				sessionIdGenerator: () => (0, node_crypto.randomUUID)(),
 				enableJsonResponse: true,
-				onsessioninitialized: (sessionId$1) => {
-					this.sessionManager.setSession(sessionId$1, transport, mcpServer);
+				onsessioninitialized: (sessionId) => {
+					this.sessionManager.setSession(sessionId, transport, mcpServer);
 				}
 			});
 			transport.onclose = () => {
@@ -833,54 +817,52 @@ var HttpTransportHandler = class {
 		return this.config.host;
 	}
 };
-
 //#endregion
 //#region src/transports/types.ts
 /**
 * Transport mode types
 */
-let TransportMode = /* @__PURE__ */ function(TransportMode$1) {
-	TransportMode$1["STDIO"] = "stdio";
-	TransportMode$1["HTTP"] = "http";
-	TransportMode$1["SSE"] = "sse";
-	TransportMode$1["CLI"] = "cli";
-	return TransportMode$1;
+let TransportMode = /* @__PURE__ */ function(TransportMode) {
+	TransportMode["STDIO"] = "stdio";
+	TransportMode["HTTP"] = "http";
+	TransportMode["SSE"] = "sse";
+	TransportMode["CLI"] = "cli";
+	return TransportMode;
 }({});
-
 //#endregion
-Object.defineProperty(exports, 'HttpTransportHandler', {
-  enumerable: true,
-  get: function () {
-    return HttpTransportHandler;
-  }
+Object.defineProperty(exports, "HttpTransportHandler", {
+	enumerable: true,
+	get: function() {
+		return HttpTransportHandler;
+	}
 });
-Object.defineProperty(exports, 'SseTransportHandler', {
-  enumerable: true,
-  get: function () {
-    return SseTransportHandler;
-  }
+Object.defineProperty(exports, "SseTransportHandler", {
+	enumerable: true,
+	get: function() {
+		return SseTransportHandler;
+	}
 });
-Object.defineProperty(exports, 'StdioTransportHandler', {
-  enumerable: true,
-  get: function () {
-    return StdioTransportHandler;
-  }
+Object.defineProperty(exports, "StdioTransportHandler", {
+	enumerable: true,
+	get: function() {
+		return StdioTransportHandler;
+	}
 });
-Object.defineProperty(exports, 'TransportMode', {
-  enumerable: true,
-  get: function () {
-    return TransportMode;
-  }
+Object.defineProperty(exports, "TransportMode", {
+	enumerable: true,
+	get: function() {
+		return TransportMode;
+	}
 });
-Object.defineProperty(exports, 'createServer', {
-  enumerable: true,
-  get: function () {
-    return createServer;
-  }
+Object.defineProperty(exports, "createServer", {
+	enumerable: true,
+	get: function() {
+		return createServer;
+	}
+});
+Object.defineProperty(exports, "version", {
+	enumerable: true,
+	get: function() {
+		return version;
+	}
 });
-Object.defineProperty(exports, 'version', {
-  enumerable: true,
-  get: function () {
-    return version;
-  }
-});