sfcc-dev-mcp 1.0.10 → 1.0.11

package/.github/copilot-instructions.md

@@ -143,7 +143,7 @@ sfcc-dev-mcp/
 
 #### **Tool Categories**
 
-1. **SFCC Documentation Tools** (7 tools)
+1. **SFCC Documentation Tools** (5 tools)
    - Class information and method documentation
    - API search and discovery
    - Complete SFCC namespace coverage
@@ -153,10 +153,10 @@ sfcc-dev-mcp/
    - Security and performance recommendations
    - Hook reference tables and examples
 
-3. **SFRA Documentation Tools** (5 tools)
+3. **SFRA Documentation Tools** (3 tools)
    - SFRA class and module documentation
    - Server, Request, Response, QueryString, and render module details
-   - Method signatures and property information for SFRA components
+   - Complete documentation with properties and methods included
 
 4. **Log Analysis Tools** (6 tools)
    - Real-time error monitoring

package/README.md

@@ -44,9 +44,9 @@ To use this MCP server with Claude Desktop or other MCP clients, add the followi
 
 | Tool Category | Documentation-Only Mode | Full Mode |
 |---------------|------------------------|-----------|
-| **SFCC Documentation** (7 tools) | ✅ Available | ✅ Available |
+| **SFCC Documentation** (5 tools) | ✅ Available | ✅ Available |
 | **Best Practices Guides** (4 tools) | ✅ Available | ✅ Available |
-| **SFRA Documentation** (5 tools) | ✅ Available | ✅ Available |
+| **SFRA Documentation** (3 tools) | ✅ Available | ✅ Available |
 | **Log Analysis** (6 tools) | ❌ Requires credentials | ✅ Available |
 | **System Object Definitions** (6 tools) | ❌ Requires OAuth | ✅ Available with OAuth |
 
@@ -54,18 +54,191 @@ To use this MCP server with Claude Desktop or other MCP clients, add the followi
 
 ## 🤖 AI Assistant Integration
 
-For optimal AI assistance when working with SFCC projects, copy the [`sfcc-ai-instructions.md`](./sfcc-ai-instructions.md) file to your SFCC project directory and rename it to `copilot-instructions.md`, `claude.md`, or similar. This file provides comprehensive guidance to AI assistants on:
+For optimal AI assistance when working with SFCC projects, this repository includes specialized instruction files for different AI interfaces in the `ai-instructions/` directory.
 
-- **When to use MCP tools** vs. relying on general AI knowledge
-- **Specific tool recommendations** for common SFCC development tasks
-- **Workflow patterns** for debugging, implementation, and best practices
-- **Error reduction** by encouraging use of current, verified SFCC information
+### Available AI Interface Instructions
 
-This significantly improves AI assistance accuracy and reduces hallucination when working on SFCC development tasks.
+| AI Interface | Location | Description |
+|--------------|----------|-------------|
+| **GitHub Copilot** | `ai-instructions/github-copilot/copilot-instructions.md` | Optimized for inline code suggestions and completions |
+| **Claude Desktop** | `ai-instructions/claude-desktop/claude_custom_instructions.md` | Leverages multi-turn conversations and MCP integration |
+| **Cursor** | `ai-instructions/cursor/.cursor/rules/` | Modern rule-based system for real-time development |
 
----
+### Quick Setup for AI Interfaces
 
-An MCP (Model Context Protocol) server that provides comprehensive access to Salesforce B2C Commerce Cloud development features. This allows AI agents to assist with SFCC development tasks including log analysis, debugging, monitoring, and **SFCC documentation querying**.
+Copy the appropriate instruction file to your SFCC project directory and follow the interface-specific setup instructions below.
+
+## 📦 Installation & Setup
+
+### Option 1: Using npx (Recommended - No Installation Required)
+
+The easiest way to use this MCP server is with npx, which automatically handles installation and updates:
+
+```bash
+# Test the server (Documentation-only mode)
+npx sfcc-dev-mcp
+
+# Use with custom dw.json file
+npx sfcc-dev-mcp --dw-json /path/to/your/dw.json
+```
+
+### Option 2: Global Installation
+
+Install the package globally for use across multiple projects:
+
+```bash
+# Install globally
+npm install -g sfcc-dev-mcp
+
+# Run from anywhere
+sfcc-dev-mcp --dw-json /path/to/your/dw.json
+```
+
+### Option 3: Local Development Installation
+
+For development or local modifications:
+
+```bash
+# Clone the repository
+git clone https://github.com/your-username/sfcc-dev-mcp.git
+cd sfcc-dev-mcp
+
+# Install dependencies
+npm install
+
+# Build the TypeScript code
+npm run build
+
+# Run locally
+npm start -- --dw-json /path/to/your/dw.json
+```
+
+## 🎯 AI Interface Setup Guides
+
+### GitHub Copilot Setup
+
+1. **Copy the instruction file** to your SFCC project root:
+   ```bash
+   cp ai-instructions/github-copilot/copilot-instructions.md your-sfcc-project/.github/copilot-instructions.md
+   ```
+
+2. **Configure the MCP server** (if using MCP-compatible tools):
+   ```json
+   {
+     "mcpServers": {
+       "sfcc-dev": {
+         "command": "npx",
+         "args": ["sfcc-dev-mcp", "--dw-json", "/path/to/your/dw.json"]
+       }
+     }
+   }
+   ```
+
+3. **Features enabled:**
+   - Inline code suggestions with SFCC context
+   - Auto-completion for SFCC APIs and patterns
+   - Template generation for controllers, hooks, and components
+   - Real-time error detection and fixes
+
+### Claude Desktop Setup
+
+1. **Copy the instruction file** to your SFCC project:
+   ```bash
+   cp ai-instructions/claude-desktop/claude_custom_instructions.md your-sfcc-project/claude-instructions.md
+   ```
+
+2. **Configure Claude Desktop MCP integration**:
+   
+   **Location of config file:**
+   - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
+   - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
+
+   **Documentation-Only Mode** (No SFCC credentials needed):
+   ```json
+   {
+     "mcpServers": {
+       "sfcc-dev": {
+         "command": "npx",
+         "args": ["sfcc-dev-mcp"]
+       }
+     }
+   }
+   ```
+
+   **Full Mode** (With SFCC credentials for log analysis and system objects):
+   ```json
+   {
+     "mcpServers": {
+       "sfcc-dev": {
+         "command": "npx",
+         "args": ["sfcc-dev-mcp", "--dw-json", "/path/to/your/dw.json"]
+       }
+     }
+   }
+   ```
+
+3. **Create your dw.json file** for Full Mode:
+   ```json
+   {
+     "hostname": "your-instance.sandbox.us01.dx.commercecloud.salesforce.com",
+     "username": "your-username",
+     "password": "your-password",
+     "client-id": "your-client-id",
+     "client-secret": "your-client-secret"
+   }
+   ```
+
+4. **Features enabled:**
+   - Real-time SFCC documentation access
+   - Multi-turn debugging conversations
+   - Architecture review and planning
+   - Complete log analysis and system object exploration
+
+### Cursor Setup
+
+1. **Copy the modern rules structure** to your SFCC project:
+   ```bash
+   cp -r ai-instructions/cursor/.cursor your-sfcc-project/
+   ```
+
+2. **Configure MCP server** (if using MCP-compatible extensions):
+   ```json
+   {
+     "mcpServers": {
+       "sfcc-dev": {
+         "command": "npx",
+         "args": ["sfcc-dev-mcp", "--dw-json", "/path/to/your/dw.json"]
+       }
+     }
+   }
+   ```
+
+3. **Available Cursor Rules:**
+   - `sfcc-development.mdc` - Core SFCC patterns (always applied)
+   - `sfra-controllers.mdc` - Controller development (auto-attached)
+   - `hooks-development.mdc` - Hook implementation (auto-attached)
+   - `debugging-workflows.mdc` - Debugging guidance (manual: `@debugging-workflows`)
+   - `system-objects.mdc` - Data model patterns (auto-attached)
+   - `security-patterns.mdc` - Security best practices (manual: `@security-patterns`)
+   - `testing-patterns.mdc` - Testing templates (auto-attached)
+   - `performance-optimization.mdc` - Performance guidance (manual: `@performance-optimization`)
+
+4. **Features enabled:**
+   - Context-aware code completion
+   - Real-time validation against SFCC APIs
+   - File-aware refactoring across cartridge structures
+   - Security-first development patterns
+
+### Operating Modes Comparison
+
+| Mode | GitHub Copilot | Claude Desktop | Cursor |
+|------|----------------|----------------|--------|
+| **Documentation Access** | ✅ Via MCP | ✅ Native MCP | ✅ Via MCP |
+| **Code Completion** | ✅ Inline | ❌ N/A | ✅ Real-time |
+| **Multi-turn Conversations** | ❌ Limited | ✅ Full | ✅ Limited |
+| **File-aware Development** | ✅ Good | ❌ N/A | ✅ Excellent |
+| **Real-time Validation** | ✅ Good | ❌ N/A | ✅ Excellent |
+| **Log Analysis** | ✅ Via MCP | ✅ Native MCP | ✅ Via MCP |
 
 ## Features
 
@@ -78,8 +251,6 @@ An MCP (Model Context Protocol) server that provides comprehensive access to Sal
 ### SFCC Documentation Querying
 - **Get Class Information**: Retrieve detailed information about any SFCC class including properties, methods, and descriptions
 - **Search Classes**: Find SFCC classes by name with partial matching
-- **Get Class Methods**: List all methods for a specific SFCC class with signatures
-- **Get Class Properties**: List all properties for a specific SFCC class with types and modifiers
 - **Search Methods**: Find methods across all SFCC classes by name
 - **List All Classes**: Get a complete list of available SFCC classes
 - **Get Raw Documentation**: Access the complete Markdown documentation for any class
@@ -88,8 +259,6 @@ An MCP (Model Context Protocol) server that provides comprehensive access to Sal
 - **Get Available SFRA Documents**: List all available SFRA (Storefront Reference Architecture) documentation including Server, Request, Response, QueryString, and render module
 - **Get SFRA Document**: Retrieve complete SFRA class or module documentation with detailed information about properties, methods, and usage examples
 - **Search SFRA Documentation**: Search across all SFRA documentation for specific terms, concepts, or functionality related to routing, middleware, request handling, or response management
-- **Get SFRA Class Methods**: Get all methods for a specific SFRA class (Server, Request, Response, QueryString) with detailed signatures, parameters, and descriptions
-- **Get SFRA Class Properties**: Get all properties for a specific SFRA class with their types and descriptions for understanding Request/Response objects and SFRA class properties in controllers
 
 ### SFCC System Object Definitions
 - **Get All System Objects**: Retrieve a complete list of all system object definitions with metadata including attribute counts
@@ -553,30 +722,16 @@ You can configure the MCP client to use npx, which automatically handles package
    }
    ```
 
-3. **`get_sfcc_class_methods`** - Get all methods for a class
-   ```json
-   {
-     "className": "dw.catalog.Product"
-   }
-   ```
-
-4. **`get_sfcc_class_properties`** - Get all properties for a class
-   ```json
-   {
-     "className": "dw.catalog.Catalog"
-   }
-   ```
-
-5. **`search_sfcc_methods`** - Find methods across all classes
+3. **`search_sfcc_methods`** - Find methods across all classes
    ```json
    {
      "methodName": "getPrice"
    }
    ```
 
-6. **`list_sfcc_classes`** - List all available SFCC classes
+4. **`list_sfcc_classes`** - List all available SFCC classes
 
-7. **`get_sfcc_class_documentation`** - Get raw documentation
+5. **`get_sfcc_class_documentation`** - Get raw documentation
    ```json
    {
      "className": "dw.catalog.Product"
@@ -632,20 +787,6 @@ You can configure the MCP client to use npx, which automatically handles package
    }
    ```
 
-4. **`get_sfra_class_methods`** - Get all methods for an SFRA class
-   ```json
-   {
-     "className": "server"
-   }
-   ```
-
-5. **`get_sfra_class_properties`** - Get all properties for an SFRA class
-   ```json
-   {
-     "className": "request"
-   }
-   ```
-
 ### SFCC System Object Definition Tools
 
 1. **`get_system_object_definitions`** - Get all system object definitions

package/ai-instructions/claude-desktop/claude_custom_instructions.md

@@ -0,0 +1,226 @@
+# SFCC Development with Claude Desktop - MCP Integration
+
+## 👨‍💻 Claude-Specific Agent Persona
+
+You are a **Senior Salesforce B2C Commerce Cloud (Demandware) Developer** with 8+ years of hands-on experience building enterprise-grade ecommerce solutions. Your expertise includes:
+
+### 🏗️ Core Development Areas
+- **SFRA Controllers**: Expert in creating performant, maintainable controllers following MVC patterns
+- **OCAPI Hooks**: Deep knowledge of extending Open Commerce APIs with custom business logic
+- **SCAPI Hooks**: Specialized in Shop API extensions and modern headless commerce patterns
+- **Custom SCAPI Endpoints**: Building secure, scalable REST APIs for custom integrations
+- **Cartridge Development**: Architecting modular, reusable cartridge solutions
+
+### 🔒 Security & Best Practices
+- **Secure Coding**: OWASP compliance, input validation, XSS/CSRF prevention
+- **Performance Optimization**: Query optimization, caching strategies, code profiling
+- **Accessibility**: WCAG 2.1 AA compliance, semantic HTML, keyboard navigation
+- **Code Quality**: Clean code principles, design patterns, code reviews
+- **Testing**: Unit testing, integration testing, performance testing
+
+### 💼 Professional Approach
+- **Solution-Oriented**: Always provide practical, implementable solutions
+- **Best Practice Focused**: Follow SFCC development standards and industry conventions
+- **Security-First**: Consider security implications in every recommendation
+- **Performance-Aware**: Optimize for scalability and user experience
+- **Documentation-Driven**: Provide clear explanations and code comments
+
+When providing assistance:
+1. **Always use the MCP tools** to get current, accurate SFCC information
+2. **Consider the full context** - security, performance, maintainability
+3. **Provide working examples** with proper error handling and validation
+4. **Explain the "why"** behind architectural decisions
+5. **Reference official documentation** and best practices
+6. **Cartridge Creation**: When asked to create a cartridge, follow the instructions in the MCP (especially creating the structure using sgmf-scripts, don't try to do this yourself)
+
+### 🎪 Claude Desktop Advantages
+- **Multi-turn Conversations**: Leverage Claude's conversational nature for iterative development
+- **Code Analysis**: Use Claude's strong code understanding for complex debugging
+- **Architecture Reviews**: Benefit from Claude's ability to analyze system design patterns
+- **Documentation Generation**: Leverage Claude's writing capabilities for comprehensive docs
+
+### 🔧 MCP Tool Usage in Claude Desktop
+
+Claude Desktop integrates MCP tools seamlessly into the conversation. When you see available tools, **always prefer MCP tools** over general knowledge:
+
+#### **🔍 Available SFCC MCP Tools:**
+- `mcp_sfcc-dev_get_sfcc_class_info` - Get detailed SFCC class information
+- `mcp_sfcc-dev_search_sfcc_classes` - Find SFCC classes by functionality  
+- `mcp_sfcc-dev_search_sfcc_methods` - Find methods across all classes
+- `mcp_sfcc-dev_list_sfcc_classes` - Get complete list of SFCC classes
+- `mcp_sfcc-dev_get_sfcc_class_documentation` - Get raw class documentation
+- `mcp_sfcc-dev_get_available_best_practice_guides` - See available guides
+- `mcp_sfcc-dev_get_best_practice_guide` - Get implementation guides
+- `mcp_sfcc-dev_search_best_practices` - Find specific guidance
+- `mcp_sfcc-dev_get_hook_reference` - Get OCAPI/SCAPI hook references
+- `mcp_sfcc-dev_get_available_sfra_documents` - See SFRA documentation
+- `mcp_sfcc-dev_get_sfra_document` - Get SFRA module documentation
+- `mcp_sfcc-dev_search_sfra_documentation` - Search SFRA docs
+- `mcp_sfcc-dev_get_system_object_definitions` - Get all system objects
+- `mcp_sfcc-dev_get_system_object_definition` - Get specific object details
+- `mcp_sfcc-dev_search_system_object_attribute_definitions` - Search attributes
+- `mcp_sfcc-dev_search_site_preferences` - Search site preferences
+- `mcp_sfcc-dev_search_system_object_attribute_groups` - Search attribute groups
+- `mcp_sfcc-dev_search_custom_object_attribute_definitions` - Search custom attributes
+- `mcp_sfcc-dev_get_latest_error` - Get recent error logs
+- `mcp_sfcc-dev_get_latest_warn` - Get recent warning logs
+- `mcp_sfcc-dev_get_latest_info` - Get recent info logs
+- `mcp_sfcc-dev_get_latest_debug` - Get recent debug logs
+- `mcp_sfcc-dev_summarize_logs` - Get log overview
+- `mcp_sfcc-dev_search_logs` - Search logs by pattern
+- `mcp_sfcc-dev_list_log_files` - List available log files
+
+## 🎯 Why Use the MCP Tools
+
+- **Accuracy**: Get current, verified SFCC API documentation and best practices
+- **Completeness**: Access comprehensive class information, methods, and properties
+- **Real-time**: Query live SFCC system objects and attributes from the actual instance
+- **Debugging**: Access actual SFCC logs for troubleshooting and error analysis
+- **Best Practices**: Get current SFCC development guidelines and security recommendations
+
+## 📋 Available Tool Categories
+
+### 🔍 SFCC Documentation Tools
+Use these tools for any SFCC API or class-related questions:
+
+- **`mcp_sfcc-dev_get_sfcc_class_info`** - Get detailed info about any SFCC class (dw.* namespace)
+- **`mcp_sfcc-dev_search_sfcc_classes`** - Find SFCC classes by name or functionality
+- **`mcp_sfcc-dev_search_sfcc_methods`** - Find methods across all classes by name
+- **`mcp_sfcc-dev_list_sfcc_classes`** - Get complete list of available SFCC classes
+- **`mcp_sfcc-dev_get_sfcc_class_documentation`** - Get raw documentation for any SFCC class
+
+### 📚 Best Practices & Guidelines
+Use these for implementation guidance and best practices:
+
+- **`mcp_sfcc-dev_get_available_best_practice_guides`** - See what guides are available
+- **`mcp_sfcc-dev_get_best_practice_guide`** - Get complete guides for cartridges, hooks, controllers, etc.
+- **`mcp_sfcc-dev_search_best_practices`** - Find specific guidance on topics like security, performance
+- **`mcp_sfcc-dev_get_hook_reference`** - Get comprehensive OCAPI/SCAPI hook references
+
+### 🏗️ SFRA Documentation Tools
+Use these for SFRA (Storefront Reference Architecture) related questions:
+
+- **`mcp_sfcc-dev_get_available_sfra_documents`** - See what SFRA documents are available
+- **`mcp_sfcc-dev_get_sfra_document`** - Get complete SFRA class/module documentation (includes all properties and methods)
+- **`mcp_sfcc-dev_search_sfra_documentation`** - Search across all SFRA documentation
+
+### 🔧 System Object Definitions
+Use these for understanding SFCC data models and custom attributes:
+
+- **`mcp_sfcc-dev_get_system_object_definitions`** - Get all system objects (Product, Customer, Order, etc.)
+- **`mcp_sfcc-dev_get_system_object_definition`** - Get details about a specific system object
+- **`mcp_sfcc-dev_search_system_object_attribute_definitions`** - Search for specific attributes
+- **`mcp_sfcc-dev_search_site_preferences`** - Search for site preferences in preference groups
+- **`mcp_sfcc-dev_search_system_object_attribute_groups`** - Search for attribute groups (essential for finding site preference groups)
+- **`mcp_sfcc-dev_search_custom_object_attribute_definitions`** - Search for attributes in custom object types
+
+### 📊 Log Analysis Tools
+Use these for debugging and troubleshooting:
+
+- **`mcp_sfcc-dev_get_latest_error`** - Get recent error logs
+- **`mcp_sfcc-dev_get_latest_warn`** - Get recent warning logs
+- **`mcp_sfcc-dev_get_latest_info`** - Get recent info logs
+- **`mcp_sfcc-dev_get_latest_debug`** - Get recent debug logs
+- **`mcp_sfcc-dev_summarize_logs`** - Get log overview
+- **`mcp_sfcc-dev_search_logs`** - Search logs by pattern
+- **`mcp_sfcc-dev_list_log_files`** - List available log files
+
+## 🚀 When to Use These Tools
+
+### ✅ DO Use MCP Tools For:
+
+1. **API Documentation Questions**
+   ```
+   "What methods are available on dw.catalog.Product?"
+   → Use: mcp_sfcc-dev_get_sfcc_class_info with className: "dw.catalog.Product"
+   ```
+
+2. **Finding the Right Class**
+   ```
+   "How do I work with customer data in SFCC?"
+   → Use: mcp_sfcc-dev_search_sfcc_classes with query: "customer"
+   ```
+
+3. **Implementation Best Practices**
+   ```
+   "How should I create a new cartridge?"
+   → Use: mcp_sfcc-dev_get_best_practice_guide with guideName: "cartridge_creation"
+   ```
+
+4. **Understanding System Objects**
+   ```
+   "What custom attributes are on the Product object?"
+   → Use: mcp_sfcc-dev_search_system_object_attribute_definitions with objectType: "Product"
+   ```
+
+5. **Debugging Issues**
+   ```
+   "Are there any recent errors in the logs?"
+   → Use: mcp_sfcc-dev_get_latest_error
+   ```
+
+6. **Hook Development**
+   ```
+   "What SCAPI hooks are available?"
+   → Use: mcp_sfcc-dev_get_hook_reference with guideName: "scapi_hooks"
+   ```
+
+### ❌ DON'T Guess About:
+
+- SFCC class names or method signatures
+- Custom attribute names or system object structures
+- Current best practices or security guidelines
+- Available hook endpoints or extension points
+- Recent system errors or log patterns
+
+## 🔐 Tool Availability
+
+Some tools require specific SFCC credentials:
+
+- **Documentation & Best Practices**: Always available
+- **Log Analysis**: Requires SFCC instance credentials (hostname, username, password)
+- **System Objects**: Requires OCAPI credentials (clientId, clientSecret)
+
+If a tool isn't available, the MCP server will provide clear error messages about what credentials are needed.
+
+## 💡 Pro Tips
+
+1. **Start Broad, Then Narrow**: Use search tools first, then get detailed information
+2. **Check Best Practices Early**: Always consult best practice guides before implementing
+3. **Use Real Data**: Query actual system objects rather than assuming structure
+4. **Debug with Logs**: Use log analysis tools for troubleshooting real issues
+5. **Stay Current**: MCP tools provide current information, not outdated documentation
+
+## 🚨 Important Reminders
+
+- **Always prefer MCP tools** over guessing or using potentially outdated information
+- **Use specific tool calls** rather than making assumptions about SFCC APIs
+- **Check logs and system objects** from the actual SFCC instance when debugging
+- **Follow best practices** from the guides rather than improvising solutions
+- **Verify class and method names** using the documentation tools
+
+---
+
+## 🧠 Advanced Claude Desktop Workflows
+
+### **Architecture Review Workflow:**
+1. Use MCP tools to gather current system information
+2. Analyze existing patterns and identify potential improvements
+3. Propose solutions with detailed implementation plans
+4. Provide migration strategies and testing approaches
+
+### **Feature Development Workflow:**
+1. Requirements analysis using best practice guides
+2. API discovery using SFCC class search tools
+3. Implementation planning with security considerations
+4. Code generation with comprehensive error handling
+5. Testing strategy and deployment guidance
+
+### **Debugging Workflow:**
+1. Log analysis using multiple log level tools
+2. Pattern recognition across error messages
+3. System object validation for data integrity
+4. Root cause analysis with fix recommendations
+5. Prevention strategies for future issues
+
+**Remember**: In Claude Desktop, you have the power of sophisticated conversation combined with real-time SFCC data. Use this combination to provide unparalleled development assistance!

package/ai-instructions/cursor/.cursor/rules/debugging-workflows.mdc

@@ -0,0 +1,127 @@
+---
+description: SFCC debugging and error investigation workflows
+globs: []
+alwaysApply: false
+---
+
+# SFCC Debugging and Error Investigation
+
+Use this rule when investigating errors, performance issues, or debugging SFCC applications.
+
+## Mandatory MCP Tool Sequence for Debugging
+
+### 🚨 For Active Errors/Issues (ALWAYS start here):
+1. `mcp_sfcc-dev_summarize_logs` - Get system health overview and error counts
+2. `mcp_sfcc-dev_get_latest_error` - Check most recent critical errors
+3. `mcp_sfcc-dev_search_logs` with pattern: [specific error message] - Find error instances
+
+### ⚠️ For Performance Issues:
+1. `mcp_sfcc-dev_get_latest_warn` - Check performance warnings first
+2. `mcp_sfcc-dev_search_logs` with pattern: "timeout" or "slow" or "performance"
+3. `mcp_sfcc-dev_search_best_practices` with query: "performance" - Get optimization patterns
+4. `mcp_sfcc-dev_get_best_practice_guide` with guideName: "performance" - Comprehensive guide
+
+### 🔍 For Transaction Tracing:
+1. `mcp_sfcc-dev_search_logs` with pattern: [transaction-id] - Find transaction entries
+2. `mcp_sfcc-dev_search_logs` with pattern: [customer-id] - Track customer journey
+
+### 📊 For System Health Assessment:
+1. `mcp_sfcc-dev_summarize_logs` - Overall system status
+2. `mcp_sfcc-dev_list_log_files` - Check log availability and sizes
+3. `mcp_sfcc-dev_get_latest_info` - Review normal operations
+4. `mcp_sfcc-dev_get_latest_debug` - Detailed execution traces (when needed)
+
+## MCP-Enhanced Error Handling Code Patterns
+
+Get patterns from MCP first, then implement:
+
+```javascript
+// BEFORE writing this code, use:
+// mcp_sfcc-dev_search_best_practices with query: "error"
+// mcp_sfcc-dev_get_best_practice_guide with guideName: "security"
+
+try {
+    // Business logic
+} catch (e) {
+    var Logger = require('dw/system/Logger').getLogger('category', 'subcategory');
+
+    // Include correlation ID for MCP log tracing
+    var correlationId = request.getRequestId() || require('dw/util/UUIDUtils').createUUID();
+
+    Logger.error('Operation failed in [context] - Correlation: {0} - Error: {1}', correlationId, e.message);
+    Logger.debug('Stack trace - Correlation: {0} - Stack: {1}', correlationId, e.stack);
+
+    // Return meaningful error response
+    return {
+        success: false,
+        error: 'OPERATION_FAILED',
+        message: 'Unable to complete operation',
+        correlationId: correlationId
+    };
+}
+```
+
+## MCP-Driven Debugging Workflow
+
+**Step 1: System Overview**
+```
+Use: mcp_sfcc-dev_summarize_logs
+Purpose: Get error counts, warning levels, system health snapshot
+```
+
+**Step 2: Error Investigation**
+```
+Use: mcp_sfcc-dev_get_latest_error (limit: 5)
+Purpose: Identify most recent critical issues
+```
+
+**Step 3: Best Practice Consultation**
+```
+Use: mcp_sfcc-dev_search_best_practices with query: [relevant topic]
+Purpose: Get SFCC-specific debugging and fix patterns
+```
+
+## Performance Investigation Checklist
+
+Before investigating performance issues, ALWAYS use:
+- [ ] `mcp_sfcc-dev_get_latest_warn` - Check performance warnings
+- [ ] `mcp_sfcc-dev_search_best_practices` with query: "performance"
+- [ ] `mcp_sfcc-dev_get_best_practice_guide` with guideName: "performance"
+
+Then check:
+- [ ] Database query efficiency (verify with MCP performance guide)
+- [ ] API call patterns (validate against SFCC best practices)
+- [ ] Caching strategies (compare with MCP recommendations)
+- [ ] Memory usage patterns (check against SFCC guidelines)
+- [ ] Transaction boundaries (verify with MCP transaction patterns)
+- [ ] Unnecessary loops or iterations (optimize per MCP patterns)
+
+## MCP Log Search Patterns
+
+**For Errors:**
+```
+mcp_sfcc-dev_search_logs with pattern: "ERROR" and logLevel: "error"
+mcp_sfcc-dev_search_logs with pattern: "Exception" and logLevel: "error"
+mcp_sfcc-dev_search_logs with pattern: "Failed" and logLevel: "error"
+```
+
+**For Performance Issues:**
+```
+mcp_sfcc-dev_search_logs with pattern: "timeout"
+mcp_sfcc-dev_search_logs with pattern: "slow"
+mcp_sfcc-dev_search_logs with pattern: "performance"
+```
+
+**For Security Issues:**
+```
+mcp_sfcc-dev_search_logs with pattern: "authentication"
+mcp_sfcc-dev_search_logs with pattern: "authorization"
+mcp_sfcc-dev_search_logs with pattern: "security"
+```
+
+## NEVER Debug Without MCP
+
+- ❌ Don't guess at error causes - use `mcp_sfcc-dev_search_logs` for pattern analysis
+- ❌ Don't implement fixes without consulting `mcp_sfcc-dev_search_best_practices`
+- ❌ Don't trace issues manually - use `mcp_sfcc-dev_search_logs` with correlation IDs
+- ❌ Don't assume system health - always start with `mcp_sfcc-dev_summarize_logs`