Give your AI the superpower of traveling back in time to find what went wrong and fix the timeline.

🌐 Website • 🎉 Start Free • 📖 Docs

npx -p @kindly-software-inc/kdb kdb-configure --auto

Follow the prompts to sign in with Google and auto-configure your MCP client.

npx -p @kindly-software-inc/kdb kdb-configure --auto --license "YOUR-LICENSE-KEY"

Add to your MCP client config (Claude Code, Cursor, etc.):

{
  "mcpServers": {
    "kdb": {
      "command": "npx",
      "args": ["@kindly-software-inc/kdb"]
    }
  }
}

That's it! 🎊 Ask your AI: "Debug my crashing program"

Time-travel debugging for AI workflows. Step forward. Step backward. Debug as if the bug never existed.

┌─────────────────┐     MCP      ┌─────────────────┐
│  Your Machine   │◄────────────►│  Kindly Server  │
│  (any OS)       │              │  (Linux x86_64) │
│                 │              │                 │
│  Claude Code    │              │  🔮 Time-Travel │
│  Cursor         │              │  🎯 Breakpoints │
│  Any AI         │              │  📊 Analysis    │
└─────────────────┘              └─────────────────┘

No local installation. Works on macOS, Windows, Linux via MCP.

Start Free →

Your AI gets these debugging superpowers:

• debugger_attach - Connect to a process
• debugger_set_breakpoint - Set breakpoints
• debugger_continue - Resume execution
• debugger_step_forward - Step forward
• debugger_step_backward - ⏪ Step backward in time
• debugger_get_stack_trace - Get stack trace
• debugger_get_variables - Read memory
• debugger_export_trace - Export execution trace

You: "My Rust program crashes at runtime. PID is 12345"

AI:

I'll attach and debug that for you.

📎 Attached to process 12345
📸 Captured snapshot
🔍 Stack trace shows crash at unwrap() on None in process_data()

The issue is at line 47 in src/main.rs. Here's the fix:
[code suggestion]

• 🌐 kindly.software
• 📖 Documentation
• 💬 Discord (coming soon)

Built with 💜 by Kindly Software