@ema.co/mcp-toolkit 0.3.0 → 1.4.0

package/dist/mcp/handlers-consolidated.js

@@ -562,6 +562,15 @@ export async function handleWorkflow(args, client) {
             if (!persona) {
                 return { error: `Persona not found: ${personaId}` };
             }
+            // Check persona status - deployment works on disabled personas but we should inform user
+            const personaStatus = persona.status?.toLowerCase();
+            const isDisabled = personaStatus === "inactive" || personaStatus === "disabled";
+            const statusWarnings = [];
+            if (isDisabled) {
+                statusWarnings.push(`⚠️ Persona "${persona.name}" is currently DISABLED (status: ${persona.status}). ` +
+                    `Workflow will be deployed but won't be active until enabled. ` +
+                    `Use persona(mode="update", id="${personaId}", enabled=true) to enable.`);
+            }
             let deployWorkflow = workflowDef || persona.workflow_def;
             // Validate if requested (default: true)
             if (args.validate !== false) {
@@ -572,6 +581,7 @@ export async function handleWorkflow(args, client) {
                         error: "Workflow has errors",
                         issues: errors,
                         hint: "Set auto_fix=true to attempt automatic fixes",
+                        ...(statusWarnings.length > 0 && { status_warnings: statusWarnings }),
                     };
                 }
                 // Auto-fix if enabled
@@ -588,7 +598,13 @@ export async function handleWorkflow(args, client) {
             return {
                 success: true,
                 persona_id: personaId,
+                persona_name: persona.name,
+                persona_status: persona.status,
                 deployed: true,
+                ...(isDisabled && {
+                    warning: `Persona is DISABLED - workflow deployed but inactive. Enable with: persona(mode="update", id="${personaId}", enabled=true)`,
+                }),
+                ...(statusWarnings.length > 0 && { status_warnings: statusWarnings }),
             };
         }
         case "compare": {

package/dist/mcp/prompts.js

@@ -74,9 +74,16 @@ Identify what the user is asking for:
 | **Data Sources** | ✓/✗ | Knowledge base, web search, APIs? |
 | **External Tools** | ✓/✗ | ServiceNow, Salesforce, email? |
 | **Routing Logic** | ✓/✗ | How to handle different intents? |
-| **HITL Requirements** | ✓/✗ | When is human approval needed? |
+| **HITL Requirements** | ✓/✗ | DEFAULT: No approval (auto-proceed). Only add if explicitly requested. |
 | **Fallback Handling** | ✓/✗ | What if no match? |
 
+#### HITL Policy (Default: Auto-Proceed)
+For external side-effect actions (send_email, create_ticket, update_record):
+- **Default**: Proceed WITHOUT approval gate unless explicitly requested
+- **Add HITL only when**: User says "confirm before", "approval required", "human review"
+- **Skip HITL when**: User says "auto", "directly", "no approval", or specifies direct flow
+- **If ambiguous**: ASK "Should [action] require approval, or auto-proceed?"
+
 #### For BROWNFIELD (extend existing):
 | Dimension | Status | Missing Info |
 |-----------|--------|--------------|
@@ -251,7 +258,7 @@ Verify you have answers for:
 - Intents: ${args.intents || "(to be determined)"}
 - Data Sources: (ask if not clear from use case)
 - Actions: (ask if not clear from use case)
-- Approvals/HITL: (ask if external actions involved)
+- Approvals/HITL: DEFAULT is no approval (auto-proceed). Only ask if user seems to want approval gates.
 
 ### Step 2: Select Pattern + Agents
 Call \`action(suggest="${args.use_case}")\` to get recommended agents and a suggested workflow pattern.
@@ -1073,6 +1080,8 @@ Where \`<requirements>\` includes:
 ${args.intents ? `- Intents: ${args.intents}` : ""}
 ${args.tools ? `- Tools: ${args.tools}` : ""}
 
+**HITL Policy**: DEFAULT is no approval gates. Only add HITL if user explicitly requests approval/confirmation before external actions.
+
 If the tool returns \`status="needs_input"\`, ask the missing questions, then call \`workflow(...)\` again with the additional details.
 
 ### Step 2: (Optional) Validate the generated workflow