LLDB MCP server

This is a small helper that connects your AI to LLDB, a debugger. A debugger is a tool programmers use to look inside a running program: to pause it, peek at variables, and see why it crashed. If you ever have to figure out why a program misbehaves, this lets you do it by just asking your AI in plain words.

What this MCP server does

You ask your AI something like "why does my program crash when I pass hello?" The AI starts an LLDB session through this helper, loads your program, and sets a breakpoint (a pause point) where it wants to look. It runs the program, inspects memory, registers and variables, then walks back up the call stack to find what went wrong. Finally it tells you what it found, in plain words, in the chat.

Click to zoom

What you can do with it

• Start and manage LLDB debugging sessions
• Load a program, attach to a running process, or open a core dump file
• Set breakpoints and watchpoints, then run or step through code
• Print variables, examine memory, and show register values
• Show the call stack and details of each stack frame
• Disassemble code and list threads
• Run any LLDB command directly when needed

Try asking your AI

• “Start a new LLDB session and load my program at /path/to/a.out”
• “Set a breakpoint at main and run the program”
• “Show me the backtrace and print the value of the variable count”
• “Examine memory at address 0x1000 and show the register values”

What it gives back to you

You get answers in the chat: backtraces, variable values, memory contents, register dumps, disassembly, and short summaries of what the AI found. It can also tell you what it changed, like which breakpoints it set or which thread it selected. Everything is text you can read and copy.

Before you start

Who it's for

Developers and anyone who debugs programs, especially people who want to investigate crashes without memorising LLDB commands.