Enables debugging of Linux x86_64 processes through time-travel debugging features including process attachment, breakpoint management, execution control, stack trace analysis, and memory inspection.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@KDBdebug my crashing Rust program with PID 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
š Quick Start (30 seconds)
Option 1: One-Line Setup
npx -p @kindly-software-inc/kdb kdb-configure --autoFollow 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)