About kindly-software/kdb
kindly-software/kdb is an MCP server published by Kindly-Software in the Data category: kindly Debugger - Time-Travel Debugging for AI Workflows.
Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/Kindly-Software/kdbThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about kindly-software/kdb
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
3 checks have not been run yet.
README
🚀 Quick Start (30 seconds)
Option 1: One-Line Setup
npx -p @kindly-software-inc/kdb kdb-configure --auto
Follow the prompts to sign in with Google and auto-configure your MCP client.
Option 2: With License Key
npx -p @kindly-software-inc/kdb kdb-configure --auto --license "YOUR-LICENSE-KEY"
Option 3: Manual Config
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"
⏱️ What It Does
Time-travel debugging for AI workflows. Step forward. Step backward. Debug as if the bug never existed.
| Feature | Description |
|---|---|
| ⏪ Step Backward | Rewind execution to find root causes |
| ⏩ Step Forward | Resume from any checkpoint |
| 🎯 Breakpoints | Hardware-level with hit counting |
| 📚 Stack Traces | SIMD-accelerated unwinding |
| 🔐 Audit Trail | Hash-chain integrity for compliance |
💜 How It Works
┌─────────────────┐ 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.
🏷️ Pricing
| Tier | Price | Sessions |
|---|---|---|
| 🆓 Hobby | Free | 5/month (unlimited during 7-day trial!) |
| 💎 Pro | $19/mo | 100/month + unlimited time-travel |
| 🔧 Engineer | $49/mo | 500/month + memory replay + LSH bug search |
| 👥 Teams | $129/mo | 2,000/month + team audit logs |
| 🏢 Enterprise | Custom | Unlimited + SOX/SOC2/GDPR/HIPAA compliance |
🛠️ MCP Tools
Your AI gets these debugging superpowers:
debugger_attach- Connect to a processdebugger_set_breakpoint- Set breakpointsdebugger_continue- Resume executiondebugger_step_forward- Step forwarddebugger_step_backward- ⏪ Step backward in timedebugger_get_stack_trace- Get stack tracedebugger_get_variables- Read memorydebugger_export_trace- Export execution trace
💬 Example
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]
📞 Support
- 🌐 kindly.software
- 📖 Documentation
- 💬 Discord (coming soon)
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.