LLDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lldb_run_commandA | Execute an arbitrary LLDB command and return the output. |
| lldb_analyze_crashA | Analyze a crashed program or core dump to determine the cause. |
| lldb_set_breakpointA | Set a breakpoint in a program. |
| lldb_examine_variablesA | Examine local variables and arguments at a breakpoint. |
| lldb_disassembleA | Disassemble machine code to view assembly instructions. |
| lldb_read_memoryA | Read and display memory contents at a specified address. |
| lldb_evaluateA | Evaluate a C/C++ expression in the debugger context. |
| lldb_backtraceA | Get a stack backtrace showing the call chain. |
| lldb_sourceA | List source code for a file, function, or current location. |
| lldb_symbolsA | Look up symbols (functions, variables, types) in an executable. |
| lldb_registersA | View CPU register values at a breakpoint. |
| lldb_watchpointA | Set a watchpoint to break when a variable is accessed. |
| lldb_runA | Run a program under the debugger with optional breakpoints. |
| lldb_threadsA | List all threads and their current state. |
| lldb_imagesA | List loaded executable images and shared libraries. |
| lldb_helpA | Get help on LLDB commands and usage. |
| lldb_versionA | Get LLDB version information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool has a clearly distinct purpose targeting specific debugger operations, such as analyzing crashes, viewing backtraces, disassembling code, evaluating expressions, examining variables, listing images, reading memory, viewing registers, running programs, executing commands, setting breakpoints, showing source, looking up symbols, listing threads, checking version, and setting watchpoints. No tools appear to overlap in functionality, making it easy for an agent to select the correct one.
All tool names follow a consistent 'lldb_' prefix with a descriptive verb_noun pattern, such as lldb_analyze_crash, lldb_backtrace, lldb_disassemble, etc. This uniformity enhances readability and predictability, allowing agents to easily understand and navigate the toolset without confusion from mixed naming conventions.
With 17 tools, the server is well-scoped for a comprehensive debugger interface, covering essential operations like execution control, inspection, and analysis. Each tool serves a specific and necessary function in the debugging workflow, avoiding redundancy while ensuring complete coverage of typical debugging tasks.
The toolset provides complete coverage of the LLDB debugging domain, including core operations like running programs, setting breakpoints and watchpoints, examining state (variables, registers, memory), analyzing crashes, and accessing symbols and source code. No significant gaps are evident; agents can perform full debugging workflows without dead ends.