Graph-based debugging knowledge management system. Helps track debugging process systematically and retrieve past solutions.

Use this tool when:

• User reports an error or bug that needs systematic investigation

• You need to document your debugging approach for complex issues

• You want to check if similar problems were solved before

• Building a knowledge base of debugging patterns

Actions:

1. CREATE - Add nodes to the debugging graph

   • nodeType: problem|hypothesis|experiment|observation|learning|solution

   • content: Description of the node

   • parentId: Optional parent node for automatic edge creation

   • metadata: Optional tags, confidence scores, etc.

2. CONNECT - Link nodes with relationships

   • from/to: Node IDs to connect

   • type: decomposes|hypothesizes|tests|produces|learns|contradicts|supports|solves

   • strength: 0-1 relationship strength

3. QUERY - Search and analyze the graph

   • queryType: similar-problems|recent-activity

   • parameters: pattern (search text), limit, minSimilarity

Example workflow:

• CREATE problem "TypeError: Cannot read property 'x' of undefined"

• CREATE hypothesis "Missing null check in async operation"

• CREATE experiment "Add optional chaining operator"

• CREATE observation "Error resolved"

• QUERY similar-problems with pattern "TypeError undefined"

Data persists in ~/.debug-thinking-mcp/