@maka/maka-cli 5.2.10 → 5.3.0

package/bundle/typescript/src/commands/ai/mcp.sub.cmd.js

@@ -1,960 +0,0 @@
-import AICommand from './ai.command.js';
-import Maka from '../maka.cmd.js';
-import { Command } from '../../command.js';
-import { Log } from '../../tools/log/log.class.js';
-import { FSI } from '../../tools/fsi/fsi.class.js';
-import express from 'express';
-import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
-import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js';
-import { z } from 'zod';
-import cors from 'cors';
-import path from 'path';
-import fs from 'fs';
-import { fileURLToPath } from 'url';
-import { execSync } from 'child_process';
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path.dirname(__filename);
-/**
- * Get all commands from the Maka CLI
- */
-const getAllCommands = (cmd, prefix = '') => {
-    const commands = [];
-    if (cmd._commands && cmd._commands.length > 0) {
-        for (const subCmd of cmd._commands) {
-            const fullName = prefix ? `${prefix}:${subCmd.name}` : subCmd.name;
-            // Skip internal/hidden commands
-            if (subCmd.name === 'murder' || subCmd.name === 'play') {
-                continue;
-            }
-            commands.push({
-                name: fullName,
-                aliases: subCmd.aliases ? subCmd.aliases() : 'None',
-                shortDesc: subCmd.shortDesc ? subCmd.shortDesc() : '',
-                description: subCmd.description ? subCmd.description() : '',
-                usage: subCmd.options?.usage || `maka ${fullName}`,
-                examples: subCmd.options?.examples || [],
-                validOpts: subCmd.options?.validOpts || [],
-                requiredOpts: subCmd.options?.requiredOpts || [],
-                experimental: subCmd.experimental ? subCmd.experimental() : false
-            });
-            // Recursively get subcommands
-            const subCommands = getAllCommands(subCmd, fullName);
-            commands.push(...subCommands);
-        }
-    }
-    return commands;
-};
-/**
- * Get project configuration if in a Maka project
- */
-const getProjectInfo = (projectPath) => {
-    try {
-        const configPath = path.join(projectPath, '.maka', 'config.json');
-        if (fs.existsSync(configPath)) {
-            const config = JSON.parse(fs.readFileSync(configPath, 'utf-8'));
-            return {
-                isMakaProject: true,
-                config,
-                projectPath
-            };
-        }
-    }
-    catch (e) {
-        // Not a Maka project or config error
-    }
-    return {
-        isMakaProject: false,
-        projectPath
-    };
-};
-/**
- * Validate that the agent's working directory matches the MCP server's project
- * This prevents accidentally modifying files in the wrong project
- */
-const validateWorkingDirectory = (serverProjectPath) => {
-    const fsi = FSI.getInstance();
-    const agentProjectPath = fsi.findProjectDirectory();
-    // If agent is not in a Maka project at all
-    if (!agentProjectPath) {
-        return {
-            isValid: false,
-            message: `⚠️  SAFETY CHECK FAILED: Agent is not in a Maka project.\n\nAgent's current directory: ${process.cwd()}\nMCP Server project: ${serverProjectPath}\n\nPlease ensure you are working in the correct project directory before executing commands.`
-        };
-    }
-    // Normalize paths for comparison
-    const normalizedAgentPath = path.resolve(agentProjectPath);
-    const normalizedServerPath = path.resolve(serverProjectPath);
-    // If they don't match, it's a potential safety issue
-    if (normalizedAgentPath !== normalizedServerPath) {
-        return {
-            isValid: false,
-            message: `⚠️  SAFETY CHECK FAILED: Project mismatch detected!\n\nAgent's project: ${normalizedAgentPath}\nMCP Server project: ${normalizedServerPath}\n\nThe agent is attempting to work in a different project than where the MCP server is running. This could lead to modifying the wrong codebase.\n\nTo fix this:\n1. Navigate to the correct project: cd ${normalizedServerPath}\n2. Or restart the MCP server in the agent's project directory`,
-            actualProjectPath: normalizedAgentPath
-        };
-    }
-    return {
-        isValid: true,
-        actualProjectPath: normalizedAgentPath
-    };
-};
-/**
- * Creates and configures the MCP server with tools and resources
- */
-const createMcpServer = (projectPath, tool) => {
-    const server = new McpServer({
-        name: 'maka-cli-mcp-server',
-        version: '1.0.0'
-    }, {
-        capabilities: {
-            logging: {},
-            tools: {},
-            resources: {},
-            prompts: {}
-        }
-    });
-    const commands = getAllCommands(Maka);
-    const projectInfo = getProjectInfo(projectPath);
-    // Resource: Agent Instructions - How to work with Maka CLI
-    server.resource('agent-instructions', 'maka://instructions/agent-workflow', {
-        mimeType: 'text/markdown',
-        description: '⭐ CRITICAL: Read this first! Instructions for AI agents on how to properly work with Maka CLI'
-    }, async () => {
-        return {
-            contents: [
-                {
-                    uri: 'maka://instructions/agent-workflow',
-                    mimeType: 'text/markdown',
-                    text: `# Maka CLI Agent Workflow Instructions
-
-## ⚠️ CRITICAL: Read This Before Using Any Maka Commands
-
-### What is Maka CLI?
-
-Maka-CLI is a command line scaffolding tool for building modern web applications. It organizes file structure and automates package installation for React, GraphQL, REST APIs, Material-UI, and testing frameworks. Maka-CLI integrates with Meteor.js to develop high-performing, scalable Node.js applications deployable to on-prem and cloud infrastructures.
-
-### Key Maka Project Principles
-
-**Use MeteorJS Documentation to create high quality Meteor applications**
-https://docs.meteor.com/about/what-is.html
-https://docs.meteor.com/api/
-
-**IMPORTANT Directory Information:**
-- Maka commands can be run from **anywhere in the project** - you do NOT need to navigate to the 'app' directory
-- The CLI automatically detects the project root (where .maka directory exists) and operates relative to it
-- When making changes or generating files, stay in your current directory and let Maka handle the paths
-
-**AVOID Creating new files outside of using maka.**
-- To keep directory structure organized, new resources should be created using a maka generator, and then modified to suite the task.
-- If there is no generator for a a needed file, then it should be created as close to the implementation as possible.
-
-**Package Installation:**
-- Use \`maka npm install <package>\` for npm packages (NOT \`npm install\` directly)
-- Use \`maka add <meteor:package>\` for Meteor packages (NOT \`meteor add\` directly)
-- Maka CLI proxies these commands to the appropriate tools with correct configuration
-
-**Verifying Changes with Logs:**
-- After making changes, use the \`get-run-logs\` tool to inspect recent log output
-- Logs are located in \`.maka/logs/run-[env]-[timestamp].log\`
-- Check log timestamps to ensure the Meteor app is running and logs are current
-- ⚠️ **If logs are not recent (older than a few minutes), the app may not be running!**
-- False positives: Old success messages don't mean current changes worked
-- False negatives: Recent errors might be from old code if app wasn't restarted
-- **Best practice:** Ensure \`maka run\` is active, then check logs after changes appear
-
-
-### Required Workflow for ALL Maka Commands
-
-**NEVER execute a Maka command without following this workflow:**
-
-#### 1. INVESTIGATE OPTIONS FIRST
-- Use \`get-command-info\` tool to discover all available options for the command
-- Review required options, optional flags, allowed values, and examples
-- Understand what the command does and what it needs
-
-#### 2. BE INTERACTIVE WITH THE USER
-- **You must prompt the user for any required information**
-- Ask clear, specific questions about:
-  - Required parameters (e.g., "What should we name this component?")
-  - Technology choices (e.g., "Would you like to use TypeScript or JavaScript?")
-  - Optional features (e.g., "Should this page be private/authenticated?")
-- Present options as clear choices when applicable
-- Gather ALL necessary information before proceeding
-
-#### 3. CONSTRUCT COMPLETE COMMAND
-- Build the full command with ALL options as flags
-- Use the format: \`maka <command> <name> --option1=value --flag2 --option3=value\`
-- Boolean flags don't need values (use \`--private\`, not \`--private=true\`)
-- **Never rely on Maka's built-in interactive prompts - they don't work via MCP**
-
-#### 4. EXECUTE WITH ALL FLAGS
-- Only execute when you have all required information
-- Always include the "maka" prefix
-- Run from anywhere in the project - no need to change directories
-
-
-#### 5. AFTER MAKING CHANGES CHECK THE LOGS
-- Using the get-run-logs tool to ensure changes that are made do not break the application
-`
-                }
-            ]
-        };
-    });
-    // Tool: Get agent workflow instructions
-    server.tool('get-agent-instructions', '⭐ CRITICAL: Read this FIRST before using any Maka commands! Essential workflow instructions for AI agents working with Maka CLI.', {}, async () => {
-        return {
-            content: [
-                {
-                    type: 'text',
-                    text: `# Maka CLI Agent Workflow Instructions
-
-## ⚠️ CRITICAL: Read This Before Using Any Maka Commands
-
-### What is Maka CLI?
-
-Maka-CLI is a command line scaffolding tool for building modern web applications. It organizes file structure and automates package installation for React, GraphQL, REST APIs, Material-UI, and testing frameworks. Maka-CLI integrates with Meteor.js to develop high-performing, scalable Node.js applications deployable to on-prem and cloud infrastructures.
-
-### Key Maka Project Principles
-
-**Use MeteorJS Documentation to create high quality Meteor applications**
-https://docs.meteor.com/about/what-is.html
-https://docs.meteor.com/api/
-
-**IMPORTANT Directory Information:**
-- Maka commands can be run from **anywhere in the project** - you do NOT need to navigate to the 'app' directory
-- The CLI automatically detects the project root (where .maka directory exists) and operates relative to it
-- When making changes or generating files, stay in your current directory and let Maka handle the paths
-
-**AVOID Creating new files outside of using maka.**
-- To keep directory structure organized, new resources should be created using a maka generator, and then modified to suite the task.
-- If there is no generator for a a needed file, then it should be created as close to the implementation as possible.
-
-**Package Installation:**
-- Use \`maka npm install <package>\` for npm packages (NOT \`npm install\` directly)
-- Use \`maka add <meteor:package>\` for Meteor packages (NOT \`meteor add\` directly)
-- Maka CLI proxies these commands to the appropriate tools with correct configuration
-
-**Verifying Changes with Logs:**
-- After making changes, use the \`get-run-logs\` tool to inspect recent log output
-- Logs are located in \`.maka/logs/run-[env]-[timestamp].log\`
-- Check log timestamps to ensure the Meteor app is running and logs are current
-- ⚠️ **If logs are not recent (older than a few minutes), the app may not be running!**
-- False positives: Old success messages don't mean current changes worked
-- False negatives: Recent errors might be from old code if app wasn't restarted
-- **Best practice:** Ensure \`maka run\` is active, then check logs after changes appear
-
-
-### Required Workflow for ALL Maka Commands
-
-**NEVER execute a Maka command without following this workflow:**
-
-#### 1. INVESTIGATE OPTIONS FIRST
-- Use \`get-command-info\` tool to discover all available options for the command
-- Review required options, optional flags, allowed values, and examples
-- Understand what the command does and what it needs
-
-#### 2. BE INTERACTIVE WITH THE USER
-- **You must prompt the user for any required information**
-- Ask clear, specific questions about:
-  - Required parameters (e.g., "What should we name this component?")
-  - Technology choices (e.g., "Would you like to use TypeScript or JavaScript?")
-  - Optional features (e.g., "Should this page be private/authenticated?")
-- Present options as clear choices when applicable
-- Gather ALL necessary information before proceeding
-
-#### 3. CONSTRUCT COMPLETE COMMAND
-- Build the full command with ALL options as flags
-- Use the format: \`maka <command> <name> --option1=value --flag2 --option3=value\`
-- Boolean flags don't need values (use \`--private\`, not \`--private=true\`)
-- **Never rely on Maka's built-in interactive prompts - they don't work via MCP**
-
-#### 4. EXECUTE WITH ALL FLAGS
-- Only execute when you have all required information
-- Always include the "maka" prefix
-- Run from anywhere in the project - no need to change directories
-
-
-#### 5. AFTER MAKING CHANGES CHECK THE LOGS
-- Using the get-run-logs tool to ensure changes that are made do not break the application`
-                }
-            ]
-        };
-    });
-    // Tool: List all available Maka CLI commands
-    server.tool('list-maka-commands', 'List all available Maka CLI commands with descriptions. ⭐ IMPORTANT: First time using Maka? Call get-agent-instructions to learn the required workflow!', {
-        filter: z.string().optional().describe('Filter commands by name or category (e.g., "aws", "generate", "deploy")')
-    }, async ({ filter }) => {
-        let filteredCommands = commands;
-        if (filter) {
-            filteredCommands = commands.filter(cmd => cmd.name.toLowerCase().includes(filter.toLowerCase()) ||
-                cmd.shortDesc.toLowerCase().includes(filter.toLowerCase()));
-        }
-        const commandList = filteredCommands.map(cmd => {
-            const experimental = cmd.experimental ? ' (experimental)' : '';
-            return `• maka ${cmd.name}${experimental}\n  ${cmd.shortDesc}\n  Usage: ${cmd.usage}`;
-        }).join('\n\n');
-        return {
-            content: [
-                {
-                    type: 'text',
-                    text: `Available Maka CLI Commands:\n\n${commandList}\n\nTotal: ${filteredCommands.length} commands\n\n⚠️  IMPORTANT NOTES:\n• All commands must be prefixed with "maka" when executing\n• Always provide all options as command-line flags (e.g., --option=value)\n• Never rely on interactive prompts - use get-command-info to see available options\n• Example: maka generate:page myPage --private --url=/custom-path`
-                }
-            ]
-        };
-    });
-    // Tool: Get detailed command information
-    server.tool('get-command-info', 'Get detailed information about a specific Maka CLI command. ⭐ TIP: Use get-agent-instructions to learn the proper workflow before executing commands!', {
-        command: z.string().describe('Command name (e.g., "create", "generate:component", "aws:create-instance")')
-    }, async ({ command }) => {
-        const cmd = commands.find(c => c.name === command ||
-            c.name.replace(/:/g, '-') === command ||
-            c.aliases === command);
-        if (!cmd) {
-            return {
-                content: [
-                    {
-                        type: 'text',
-                        text: `Command "${command}" not found. Use list-maka-commands to see available commands.`
-                    }
-                ]
-            };
-        }
-        // Format valid options with details if available
-        const formatValidOpts = (opts) => {
-            if (!opts || opts.length === 0)
-                return null;
-            return opts.map((opt) => {
-                if (typeof opt === 'string') {
-                    return `  --${opt}`;
-                }
-                else if (opt.name) {
-                    const parts = [`  --${opt.name}`];
-                    if (opt.boolFlag)
-                        parts.push(' (boolean flag)');
-                    if (opt.description)
-                        parts.push(`\n    ${opt.description}`);
-                    if (opt.values)
-                        parts.push(`\n    Allowed values: ${opt.values.join(', ')}`);
-                    return parts.join('');
-                }
-                return `  --${opt}`;
-            }).join('\n');
-        };
-        const validOptsFormatted = formatValidOpts(cmd.validOpts);
-        const requiredOptsFormatted = cmd.requiredOpts?.length > 0
-            ? cmd.requiredOpts.map((o) => `  --${o.name || o}`).join('\n')
-            : null;
-        const details = [
-            `Command: maka ${cmd.name}`,
-            cmd.aliases !== 'None' ? `Aliases: maka ${cmd.aliases}` : null,
-            `\nDescription:\n${cmd.description || cmd.shortDesc}`,
-            `\nUsage:\n${cmd.usage}`,
-            requiredOptsFormatted ? `\n⚠️  Required Options (must be provided):\n${requiredOptsFormatted}` : null,
-            validOptsFormatted ? `\nAvailable Options:\n${validOptsFormatted}` : null,
-            cmd.examples?.length > 0 ? `\nExamples:\n${cmd.examples.map((e) => `  ${e}`).join('\n')}` : null,
-            cmd.experimental ? '\n⚠️  This is an experimental command' : null,
-            `\n💡 IMPORTANT: When executing via MCP/API:`,
-            `   • Always provide options as flags: --option=value or --flag`,
-            `   • Do not rely on interactive prompts`,
-            `   • Use: maka ${cmd.name} <args> [--option=value ...]`
-        ].filter(Boolean).join('\n');
-        return {
-            content: [
-                {
-                    type: 'text',
-                    text: details
-                }
-            ]
-        };
-    });
-    // Tool: Execute Maka CLI command (read-only operations)
-    server.tool('execute-maka-command', 'Execute a Maka CLI command (use with caution - some commands may modify files). ⭐ CRITICAL: Call get-agent-instructions FIRST to learn the required workflow! Then: (1) Use get-command-info to see all options, (2) Ask user for required info, (3) Provide ALL options as flags.', {
-        command: z.string().describe('Full command with all options as flags (e.g., "maka create myApp --js=jsx --css=scss", "maka generate:page homePage --private --url=/home"). NEVER rely on interactive prompts - always specify options explicitly.'),
-    }, async ({ command }) => {
-        let fullCommand = command.trim();
-        try {
-            // SAFETY CHECK: Validate working directory
-            const validation = validateWorkingDirectory(projectPath);
-            if (!validation.isValid) {
-                return {
-                    content: [
-                        {
-                            type: 'text',
-                            text: validation.message
-                        }
-                    ]
-                };
-            }
-            // Ensure command starts with "maka"
-            if (!fullCommand.startsWith('maka ') && !fullCommand.startsWith('maka\t')) {
-                fullCommand = `maka ${fullCommand}`;
-            }
-            // Safety check: prevent destructive operations
-            // Use word boundaries to avoid false positives (e.g., "rm" in "confirm")
-            const dangerousCommands = ['murder', 'uninstall', 'delete'];
-            const dangerousPattern = new RegExp(`\\b(${dangerousCommands.join('|')})\\b`, 'i');
-            // Check for standalone 'rm' command (not as part of other words)
-            const rmPattern = /\brm\s+/i;
-            if (dangerousPattern.test(fullCommand) || rmPattern.test(fullCommand)) {
-                return {
-                    content: [
-                        {
-                            type: 'text',
-                            text: '⚠️  This command may be destructive and cannot be executed via MCP for safety reasons.'
-                        }
-                    ]
-                };
-            }
-            const output = execSync(fullCommand, {
-                encoding: 'utf-8',
-                timeout: 120000, // 2 minutes for create commands
-                maxBuffer: 10 * 1024 * 1024, // 10MB
-                stdio: 'pipe' // Ensure we capture all output
-            });
-            return {
-                content: [
-                    {
-                        type: 'text',
-                        text: `✅ Command executed successfully:\n${fullCommand}\n\nOutput:\n${output}`
-                    }
-                ]
-            };
-        }
-        catch (error) {
-            // Capture all available error information
-            const errorDetails = [
-                `❌ Error executing command: ${fullCommand}`,
-                `\nError Message: ${error.message}`,
-                error.stdout ? `\nStdout:\n${error.stdout}` : '',
-                error.stderr ? `\nStderr:\n${error.stderr}` : '',
-                error.status !== undefined ? `\nExit Code: ${error.status}` : '',
-                error.signal ? `\nSignal: ${error.signal}` : ''
-            ].filter(Boolean).join('\n');
-            return {
-                content: [
-                    {
-                        type: 'text',
-                        text: errorDetails
-                    }
-                ]
-            };
-        }
-    });
-    // Tool: Get run logs
-    server.tool('get-run-logs', 'Read recent Meteor run logs to verify changes and check application status. IMPORTANT: Check log timestamps - if logs are old, the app may not be running!', {
-        env: z.string().optional().describe('Environment name (e.g., "local", "development"). Defaults to "local"'),
-        lines: z.number().optional().describe('Number of lines to read from the end of the most recent log file (default: 100)')
-    }, async ({ env, lines }) => {
-        try {
-            const environment = env || 'local';
-            const lineCount = lines || 100;
-            // SAFETY CHECK: Validate working directory
-            const validation = validateWorkingDirectory(projectPath);
-            if (!validation.isValid) {
-                return {
-                    content: [
-                        {
-                            type: 'text',
-                            text: validation.message
-                        }
-                    ]
-                };
-            }
-            // Use the validated project path
-            const actualProjectPath = validation.actualProjectPath;
-            const logsDir = path.join(actualProjectPath, '.maka', 'logs');
-            if (!fs.existsSync(logsDir)) {
-                return {
-                    content: [
-                        {
-                            type: 'text',
-                            text: `No logs directory found at .maka/logs/\n\nProject root: ${actualProjectPath}\n\nThis usually means:\n1. The app has never been run with \`maka run\`, OR\n2. Logging was disabled with \`--no-log\` flag\n\nTo generate logs, run: maka run`
-                        }
-                    ]
-                };
-            }
-            // Try to use the "latest" log file first (symlink or copy)
-            const latestLogPath = path.join(logsDir, `run-${environment}-latest.log`);
-            let mostRecentLog = null;
-            if (fs.existsSync(latestLogPath)) {
-                // Use the latest log file
-                const stats = fs.statSync(latestLogPath);
-                mostRecentLog = {
-                    name: `run-${environment}-latest.log`,
-                    path: latestLogPath,
-                    mtime: stats.mtime
-                };
-            }
-            else {
-                // Fallback: Find all log files for this environment and use most recent
-                const logFiles = fs.readdirSync(logsDir)
-                    .filter(file => file.startsWith(`run-${environment}-`) && file.endsWith('.log') && !file.includes('latest'))
-                    .map(file => ({
-                    name: file,
-                    path: path.join(logsDir, file),
-                    mtime: fs.statSync(path.join(logsDir, file)).mtime
-                }))
-                    .sort((a, b) => b.mtime.getTime() - a.mtime.getTime());
-                if (logFiles.length === 0) {
-                    return {
-                        content: [
-                            {
-                                type: 'text',
-                                text: `No log files found for environment: ${environment}\n\nAvailable log files:\n${fs.readdirSync(logsDir).join('\n')}\n\nTo generate logs for this environment, run: maka run --env=${environment}`
-                            }
-                        ]
-                    };
-                }
-                mostRecentLog = logFiles[0];
-            }
-            const logContent = fs.readFileSync(mostRecentLog.path, 'utf-8');
-            const logLines = logContent.split('\n');
-            const recentLines = logLines.slice(-lineCount).join('\n');
-            // Calculate how old the log is
-            const now = new Date();
-            const logAge = Math.floor((now.getTime() - mostRecentLog.mtime.getTime()) / 1000);
-            const logAgeMinutes = Math.floor(logAge / 60);
-            const logAgeSeconds = logAge % 60;
-            let ageWarning = '';
-            if (logAge > 300) { // 5 minutes
-                ageWarning = `\n⚠️  WARNING: This log is ${logAgeMinutes} minutes old! The Meteor app may not be running.\n`;
-            }
-            else if (logAge > 60) {
-                ageWarning = `\n⚠️  Note: Log is ${logAgeMinutes} minutes ${logAgeSeconds} seconds old.\n`;
-            }
-            else {
-                ageWarning = `\n✅ Log is recent (${logAgeSeconds} seconds old) - app appears to be running.\n`;
-            }
-            // Count total log files for this environment
-            const allLogFiles = fs.readdirSync(logsDir)
-                .filter(file => file.startsWith(`run-${environment}-`) && file.endsWith('.log') && !file.includes('latest'));
-            const response = [
-                `Most Recent Log: ${mostRecentLog.name}`,
-                `Last Modified: ${mostRecentLog.mtime.toISOString()}`,
-                ageWarning,
-                `Showing last ${lineCount} lines:\n`,
-                `${'='.repeat(80)}`,
-                recentLines,
-                `${'='.repeat(80)}`,
-                `\nTotal log files for ${environment}: ${allLogFiles.length}`,
-                `Log file path: ${path.relative(actualProjectPath, mostRecentLog.path)}`
-            ].join('\n');
-            return {
-                content: [
-                    {
-                        type: 'text',
-                        text: response
-                    }
-                ]
-            };
-        }
-        catch (error) {
-            return {
-                content: [
-                    {
-                        type: 'text',
-                        text: `Error reading logs: ${error.message}`
-                    }
-                ]
-            };
-        }
-    });
-    // Resource: Maka CLI Commands Reference
-    server.resource('maka-commands-reference', 'maka://commands/all', {
-        mimeType: 'application/json',
-        description: 'Complete reference of all Maka CLI commands in JSON format'
-    }, async () => {
-        return {
-            contents: [
-                {
-                    uri: 'maka://commands/all',
-                    mimeType: 'application/json',
-                    text: JSON.stringify(commands, null, 2)
-                }
-            ]
-        };
-    });
-    // Resource: Project Configuration
-    server.resource('project-config', 'maka://project/config', {
-        mimeType: 'application/json',
-        description: 'Current project configuration'
-    }, async () => {
-        return {
-            contents: [
-                {
-                    uri: 'maka://project/config',
-                    mimeType: 'application/json',
-                    text: JSON.stringify(projectInfo, null, 2)
-                }
-            ]
-        };
-    });
-    // Resource: Maka CLI Version and Info
-    server.resource('maka-info', 'maka://info', {
-        mimeType: 'application/json',
-        description: 'Maka CLI version and system information'
-    }, async () => {
-        try {
-            const versionOutput = execSync('maka --version', {
-                encoding: 'utf-8',
-                cwd: projectPath
-            }).trim();
-            return {
-                contents: [
-                    {
-                        uri: 'maka://info',
-                        mimeType: 'application/json',
-                        text: JSON.stringify({
-                            version: versionOutput,
-                            platform: process.platform,
-                            nodeVersion: process.version,
-                            cwd: projectPath
-                        }, null, 2)
-                    }
-                ]
-            };
-        }
-        catch (error) {
-            return {
-                contents: [
-                    {
-                        uri: 'maka://info',
-                        mimeType: 'application/json',
-                        text: JSON.stringify({
-                            error: 'Failed to get Maka CLI version',
-                            message: error.message
-                        }, null, 2)
-                    }
-                ]
-            };
-        }
-    });
-    // Prompt: Create new component
-    server.prompt('create-component', 'Generate a prompt for creating a new component with Maka CLI', {
-        componentName: z.string().describe('Name of the component to create'),
-        componentType: z.enum(['component', 'page', 'layout', 'template']).optional().describe('Type of component (default: component)')
-    }, async ({ componentName, componentType }) => {
-        const type = componentType || 'component';
-        return {
-            messages: [
-                {
-                    role: 'user',
-                    content: {
-                        type: 'text',
-                        text: `I want to create a new ${type} named "${componentName}" in my Maka project. Can you help me with the correct command and explain what it will generate?`
-                    }
-                },
-                {
-                    role: 'assistant',
-                    content: {
-                        type: 'text',
-                        text: `I'll help you create a ${type} named "${componentName}".\n\nCommand:\nmaka generate:${type} ${componentName}\n\nThis will create:\n- Component file with boilerplate code\n- Associated test file\n- Styles/CSS file\n- Proper imports and exports\n\nWould you like me to show you more options or execute this command?`
-                    }
-                }
-            ]
-        };
-    });
-    // Prompt: Deployment helper
-    server.prompt('deploy-help', 'Get help with deploying a Maka application', {
-        environment: z.enum(['dev', 'staging', 'production']).optional().describe('Target environment'),
-        platform: z.enum(['aws', 'docker', 'custom']).optional().describe('Deployment platform')
-    }, async ({ environment, platform }) => {
-        const env = environment || 'production';
-        const plat = platform || 'aws';
-        return {
-            messages: [
-                {
-                    role: 'user',
-                    content: {
-                        type: 'text',
-                        text: `I need help deploying my Maka application to ${env} environment using ${plat}. What are the steps?`
-                    }
-                },
-                {
-                    role: 'assistant',
-                    content: {
-                        type: 'text',
-                        text: `Here's a guide for deploying to ${env} using ${plat}:\n\n` +
-                            (plat === 'aws' ?
-                                `AWS Deployment Steps:\n1. Configure AWS credentials\n2. Use: maka aws:create-instance --env ${env}\n3. Use: maka deploy --env ${env}\n\nAvailable AWS commands:\n- maka aws:create-instance\n- maka aws:set-host\n- maka aws:terminate-instance\n\nWould you like details on any specific step?` :
-                                plat === 'docker' ?
-                                    `Docker Deployment Steps:\n1. Build: maka build:docker\n2. Configure your docker-compose.yml\n3. Deploy: docker-compose up -d\n\nWould you like help with Docker configuration?` :
-                                    `Custom Deployment:\n1. Build your app: maka run --production\n2. Configure your deployment settings\n3. Use maka deploy command with custom settings\n\nWould you like help with custom deployment configuration?`)
-                    }
-                }
-            ]
-        };
-    });
-    // Prompt: How to use Maka commands via MCP
-    server.prompt('mcp-command-usage', 'Guide on how to properly execute Maka commands via MCP (avoiding interactive prompts)', {}, async () => {
-        return {
-            messages: [
-                {
-                    role: 'user',
-                    content: {
-                        type: 'text',
-                        text: 'How do I properly execute Maka CLI commands through the MCP server?'
-                    }
-                },
-                {
-                    role: 'assistant',
-                    content: {
-                        type: 'text',
-                        text: `📘 Guide: Executing Maka Commands via MCP
-
-🔑 KEY RULES:
-1. Always prefix commands with "maka"
-2. Never rely on interactive prompts
-3. Always provide ALL options as command-line flags
-4. Use get-command-info tool first to see available options
-
-✅ CORRECT USAGE:
-• maka create myApp --js=jsx --css=scss --client=react
-• maka generate:page homePage --private --url=/home
-• maka generate:component Button --baseDir=components
-• maka generate:api Users --withMethods --withRest
-
-❌ INCORRECT USAGE:
-• generate:page homePage (missing "maka" prefix)
-• maka create myApp (missing required options, will prompt)
-• maka generate:page (missing page name)
-
-📋 WORKFLOW:
-1. Use list-maka-commands to find the command
-2. Use get-command-info to see all available options
-3. Execute with execute-maka-command, providing all options
-4. Check the output for success/errors
-
-💡 TIP: Boolean flags don't need values:
-   --private (not --private=true)
-
-Would you like to see specific examples for any command?`
-                    }
-                }
-            ]
-        };
-    });
-    // Prompt: Project setup wizard
-    server.prompt('project-setup', 'Interactive guide for setting up a new Maka project', {
-        projectType: z.enum(['basic', 'full-stack', 'api']).optional().describe('Type of project to create')
-    }, async ({ projectType }) => {
-        const type = projectType || 'basic';
-        return {
-            messages: [
-                {
-                    role: 'user',
-                    content: {
-                        type: 'text',
-                        text: `I want to create a new ${type} Maka project. Can you guide me through the setup?`
-                    }
-                },
-                {
-                    role: 'assistant',
-                    content: {
-                        type: 'text',
-                        text: `I'll guide you through creating a ${type} Maka project!\n\n` +
-                            `Step 1: Create the project\n` +
-                            `Command: maka create <your-app-name>\n\n` +
-                            `Step 2: Navigate to your project\n` +
-                            `Command: cd <your-app-name>\n\n` +
-                            `Step 3: Install dependencies\n` +
-                            `Command: maka install meteor\n\n` +
-                            `Step 4: Run your app\n` +
-                            `Command: maka run\n\n` +
-                            `Additional setup options:\n` +
-                            `- Generate components: maka generate:component <name>\n` +
-                            `- Add API routes: maka generate:api <name>\n` +
-                            `- Configure deployment: Use maka deploy commands\n\n` +
-                            `Would you like help with any specific step?`
-                    }
-                }
-            ]
-        };
-    });
-    return server;
-};
-Command.create({
-    name: 'mcp',
-    usage: 'maka ai:mcp [--port=3000] [--host=localhost]',
-    validOpts: ['port', 'host'],
-    shortDesc: 'Start an MCP server with HTTP transport',
-    mustBeInMakaProject: true,
-    description: `
-  Start a Model Context Protocol (MCP) server with HTTP transport.
-
-  The server exposes Maka CLI capabilities, commands, and project information
-  to MCP clients like Claude Desktop or other AI assistants.
-
-  Features:
-    • List all available commands
-    • Get detailed command documentation
-    • Execute Maka CLI commands (with safety restrictions)
-    • Access project information and configuration
-    • Interactive prompts for common workflows
-
-  Options:
-    --port    Port to listen on (default: 3000)
-    --host    Host to bind to (default: localhost)
-  `,
-    examples: [
-        'maka ai:mcp',
-        'maka ai:mcp --port=8080',
-        'maka ai:mcp --host=0.0.0.0 --port=3001'
-    ]
-}, async function (args, opts) {
-    try {
-        const port = opts.port || 5050;
-        const host = opts.host || 'localhost';
-        const projectPath = process.cwd();
-        // Check if we're in a Maka project and create MCP configurations
-        const isMakaProject = this.validateMakaProject();
-        if (isMakaProject) {
-            Log.notice('Detected Maka project - setting up MCP configurations...');
-            // Create .claude directory if it doesn't exist
-            const claudeDir = path.join(projectPath, '.claude');
-            if (!fs.existsSync(claudeDir)) {
-                fs.mkdirSync(claudeDir, { recursive: true });
-            }
-            // Create Claude Code MCP configuration
-            const claudeMcpPath = path.join(claudeDir, 'mcp.json');
-            const claudeMcpConfig = {
-                mcpServers: {
-                    'maka-cli': {
-                        command: 'maka',
-                        args: ['ai:mcp', `--port=${port}`],
-                        autoApprove: ['list-maka-commands', 'get-command-info', 'get-project-info', 'get-run-logs']
-                    }
-                }
-            };
-            if (!fs.existsSync(claudeMcpPath)) {
-                fs.writeFileSync(claudeMcpPath, JSON.stringify(claudeMcpConfig, null, 2));
-                Log.success(`Created Claude Code MCP config: ${path.relative(projectPath, claudeMcpPath)}`);
-            }
-            else {
-                Log.info(`Claude Code MCP config already exists: ${path.relative(projectPath, claudeMcpPath)}`);
-            }
-            // Create .vscode directory if it doesn't exist
-            const vscodeDir = path.join(projectPath, '.vscode');
-            if (!fs.existsSync(vscodeDir)) {
-                fs.mkdirSync(vscodeDir, { recursive: true });
-            }
-            // Create GitHub Copilot / VS Code MCP configuration
-            const vscodeMcpPath = path.join(vscodeDir, 'mcp.json');
-            const vscodeMcpConfig = {
-                servers: {
-                    'maka-cli': {
-                        type: 'http',
-                        url: `http://${host}:${port}/mcp`
-                    }
-                }
-            };
-            if (!fs.existsSync(vscodeMcpPath)) {
-                fs.writeFileSync(vscodeMcpPath, JSON.stringify(vscodeMcpConfig, null, 2));
-                Log.success(`Created VS Code/Copilot MCP config: ${path.relative(projectPath, vscodeMcpPath)}`);
-            }
-            else {
-                Log.info(`VS Code/Copilot MCP config already exists: ${path.relative(projectPath, vscodeMcpPath)}`);
-            }
-        }
-        Log.notice(`Starting Maka CLI MCP Server`);
-        Log.bright(`Project: ${projectPath}`);
-        const app = express();
-        app.use(express.json());
-        // Configure CORS to expose Mcp-Session-Id header for browser-based clients
-        app.use(cors({
-            origin: '*', // Allow all origins - adjust as needed for production
-            exposedHeaders: ['Mcp-Session-Id']
-        }));
-        // Health check endpoint
-        app.get('/health', (req, res) => {
-            res.json({
-                status: 'ok',
-                name: 'maka-cli-mcp-server',
-                version: '1.0.0',
-                projectPath
-            });
-        });
-        // Main MCP endpoint
-        app.post('/mcp', async (req, res) => {
-            const server = createMcpServer(projectPath, this);
-            try {
-                const transport = new StreamableHTTPServerTransport({
-                    sessionIdGenerator: undefined // Stateless mode
-                });
-                await server.connect(transport);
-                await transport.handleRequest(req, res, req.body);
-                res.on('close', () => {
-                    transport.close().catch(console.error);
-                    server.close().catch(console.error);
-                });
-            }
-            catch (error) {
-                console.error('Error handling MCP request:', error);
-                if (!res.headersSent) {
-                    res.status(500).json({
-                        jsonrpc: '2.0',
-                        error: {
-                            code: -32603,
-                            message: 'Internal server error'
-                        },
-                        id: null
-                    });
-                }
-            }
-        });
-        // Handle unsupported methods on /mcp endpoint
-        app.get('/mcp', (req, res) => {
-            res.status(405).json({
-                jsonrpc: '2.0',
-                error: {
-                    code: -32000,
-                    message: 'Method not allowed. Use POST for MCP requests.'
-                },
-                id: null
-            });
-        });
-        app.delete('/mcp', (req, res) => {
-            res.status(405).json({
-                jsonrpc: '2.0',
-                error: {
-                    code: -32000,
-                    message: 'Method not allowed.'
-                },
-                id: null
-            });
-        });
-        // Start the server
-        const server = app.listen(port, host, () => {
-            Log.success(`MCP Server listening on http://${host}:${port}`);
-            Log.notice('\n📋 Register with Claude Code:');
-            Log.bright(`  claude mcp add --transport http maka-cli http://${host}:${port}/mcp`);
-            Log.notice('\n📋 GitHub Copilot / VS Code (.vscode/mcp.json):');
-            Log.bright(`  {`);
-            Log.bright(`    "servers": {`);
-            Log.bright(`      "maka-cli": {`);
-            Log.bright(`        "type": "http",`);
-            Log.bright(`        "url": "http://${host}:${port}/mcp"`);
-            Log.bright(`      }`);
-            Log.bright(`    }`);
-            Log.bright(`  }`);
-            Log.warn(`This MCP Server is interacting with ${process.cwd()}`);
-            Log.warn(`Ensure this is the correct directory of your app!`);
-            Log.header('\n Press Ctrl+C to stop the server');
-        });
-        // Handle graceful shutdown
-        const shutdown = async () => {
-            Log.notice('\nShutting down MCP server...');
-            server.close(() => {
-                Log.success('Server stopped');
-                process.exit(0);
-            });
-        };
-        process.on('SIGINT', shutdown);
-        process.on('SIGTERM', shutdown);
-    }
-    catch (e) {
-        Log.error('Failed to start MCP server');
-        console.error(e);
-        process.exit(1);
-    }
-}, AICommand);
-//# sourceMappingURL=mcp.sub.cmd.js.map