EuConquisto Composer MCP

# EuConquisto Composer MCP - Rollback Instructions **Document Version**: 1.0.0 **Created**: 2025-07-02 **Purpose**: Complete rollback procedures for JWT path fix implementation **Urgency**: Reference document for immediate issue resolution --- ## 🚨 **EMERGENCY ROLLBACK - QUICK REFERENCE** ### **If Fixed Script Fails Immediately** ```bash # 1. Edit Claude Desktop Config nano "/Users/ricardokawasaki/Library/Application Support/Claude/claude_desktop_config.json" # 2. Change line 130 back to: "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/dist/browser-automation-simple.js" # 3. Restart Claude Desktop (Cmd+Q, wait 10 seconds, relaunch) ``` --- ## 📋 **COMPREHENSIVE ROLLBACK PROCEDURES** ### **Scenario 1: Fixed Script Has Runtime Errors** **Step 1: Identify the Issue** - Check Claude Desktop MCP logs for error messages - Look for console errors related to file loading or path resolution - Verify if JWT token loading specifically fails **Step 2: Revert to Original Script** ```bash # Edit configuration file open "/Users/ricardokawasaki/Library/Application Support/Claude/claude_desktop_config.json" # Find euconquisto-composer section and change: # FROM: "browser-automation-simple-fixed.js" # TO: "browser-automation-simple.js" ``` **Step 3: Restart Claude Desktop** ```bash # Complete shutdown and restart # 1. Cmd+Q (or right-click dock icon → Quit) # 2. Wait 10-15 seconds for complete shutdown # 3. Relaunch from Applications folder # 4. Wait for MCP servers to load (look for tools availability) ``` **Step 4: Test Original Script** ```bash # Try basic MCP tool functionality # If still fails, proceed to Scenario 2 ``` ### **Scenario 2: Original Script Also Has Path Issues** **Step 1: Manual JWT Token Placement** ```bash # Copy JWT token to Claude Desktop working directory cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/Library/Application Support/Claude/" # Also copy to common working directories cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/" cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/Desktop/" ``` **Step 2: Create archive/authentication Directory Structure** ```bash # Create directory structure in multiple locations mkdir -p "/Users/ricardokawasaki/Library/Application Support/Claude/archive/authentication" mkdir -p "/Users/ricardokawasaki/archive/authentication" mkdir -p "/Users/ricardokawasaki/Desktop/archive/authentication" # Copy JWT token to all locations cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/Library/Application Support/Claude/archive/authentication/" cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/archive/authentication/" cp "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" "/Users/ricardokawasaki/Desktop/archive/authentication/" ``` **Step 3: Restart and Test** ```bash # Restart Claude Desktop with new JWT token locations # Test MCP tool functionality ``` ### **Scenario 3: Complete System Rollback Required** **Step 1: Disable EuConquisto MCP Server** ```json // Edit claude_desktop_config.json // Add "disabled": true to euconquisto-composer section { "euconquisto-composer": { "command": "node", "args": ["..."], "env": {"NODE_ENV": "development"}, "disabled": true } } ``` **Step 2: Alternative Implementation Testing** ```bash # Use original TypeScript implementation (requires compilation fix) # Or use manual localStorage injection for testing # Or use direct Composer interface without MCP automation ``` --- ## 🔍 **DIAGNOSTIC PROCEDURES** ### **Check JWT Token Validity** ```bash # Verify JWT token exists and is readable cat "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" # Check JWT token expiration (manual decode) # Token should be valid until 2025-07-28 ``` ### **Check Claude Desktop MCP Logs** ```bash # View Claude Desktop logs tail -f "/Users/ricardokawasaki/Library/Logs/Claude/mcp.log" # Or check Console.app for Claude Desktop logs # Look for: "JWT token load failed" or path-related errors ``` ### **Check MCP Server Process** ```bash # List running Node.js processes ps aux | grep "browser-automation-simple" # Check if MCP server is running lsof -i :stdio # MCP servers use stdio transport ``` ### **Verify File Permissions** ```bash # Check if files are readable ls -la "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/dist/" ls -la "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/" # Fix permissions if needed chmod 644 "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/dist/browser-automation-simple*.js" chmod 644 "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc/archive/authentication/correct-jwt-new.txt" ``` --- ## 📊 **ROLLBACK SUCCESS VERIFICATION** ### **After Configuration Revert** 1. **MCP Tool Available**: `create_educational_composition` appears in tools list 2. **No Path Errors**: No "JWT token not found" messages in logs 3. **Basic Functionality**: Tool responds to simple test prompts 4. **Error Messages**: Clear, actionable feedback if issues persist ### **After JWT Token Placement** 1. **Token Loading**: MCP server logs show "JWT token loaded successfully" 2. **Authentication Ready**: Tool doesn't immediately fail with auth errors 3. **Browser Tests**: If testing browser automation, JWT redirect works ### **After Complete System Rollback** 1. **MCP Server Disabled**: No errors in Claude Desktop startup 2. **Alternative Methods**: Manual localStorage injection available 3. **System Stability**: Other MCP servers unaffected 4. **Recovery Path**: Clear path forward for alternative implementation --- ## 🛠️ **ALTERNATIVE IMPLEMENTATION OPTIONS** ### **Option 1: Manual localStorage Injection** ```javascript // Direct browser console injection for testing localStorage.setItem('rdp-composer-data', JSON.stringify(compositionData)); // Then reload page to see composition ``` ### **Option 2: Original TypeScript Implementation** ```bash # Fix TypeScript compilation issues first cd "/Users/ricardokawasaki/Desktop/euconquisto-composer-mcp-poc" npm run build # Then use compiled TypeScript version ``` ### **Option 3: Simplified Testing Approach** ```bash # Use JWT redirect server directly in browser # Navigate to http://localhost:8080/composer # Manual composition creation for validation ``` --- ## 📞 **ESCALATION PROCEDURES** ### **If All Rollback Attempts Fail** 1. **Document Error Messages**: Capture exact error logs and symptoms 2. **Preserve System State**: Don't make additional changes 3. **Alternative Validation**: Use manual browser testing approach 4. **Implementation Review**: Consider if TypeScript compilation fix is needed ### **Recovery Resources** - **Original Documentation**: All pre-fix documentation preserved - **Working System**: Phase 2 intelligent systems remain functional - **Alternative Tools**: Other MCP servers and manual testing available - **Project Backup**: All files backed up with version control --- ## ✅ **ROLLBACK CHECKLIST** ### **Before Starting Rollback** - [ ] Document current error symptoms - [ ] Note exact error messages - [ ] Verify Claude Desktop version and settings - [ ] Confirm other MCP servers working ### **During Rollback Process** - [ ] Follow steps in order - [ ] Wait for complete restarts between changes - [ ] Test after each major change - [ ] Document what works/doesn't work ### **After Rollback Complete** - [ ] Verify MCP tool availability - [ ] Test basic tool functionality - [ ] Confirm system stability - [ ] Update documentation with findings --- ## 📈 **SUCCESS METRICS POST-ROLLBACK** ### **Immediate Success Indicators** - ✅ **No Runtime Errors**: MCP server starts without JWT token errors - ✅ **Tool Accessibility**: `create_educational_composition` available in Claude Desktop - ✅ **Basic Response**: Tool responds to simple test prompts without crashing - ✅ **System Stability**: Other MCP servers unaffected by changes ### **Functional Success Indicators** - ✅ **Error Messaging**: Clear feedback about any remaining issues - ✅ **Alternative Paths**: Alternative implementation options available - ✅ **Recovery Capability**: System ready for next implementation attempt - ✅ **Documentation Intact**: All project knowledge preserved --- **Document Purpose**: Emergency reference for immediate issue resolution **Usage Context**: Use when fixed implementation fails or causes issues **Recovery Time**: 5-15 minutes for most rollback scenarios **Success Rate**: High - multiple fallback options available **🚨 Emergency Contact**: All rollback procedures tested and documented**