MCP Directory

How to add LLDB-MCP to Cursor

Integrate the LLDB debugger with Claude via MCP for AI-assisted debugging sessions. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 105 · stdio · no auth

Cursor config for LLDB-MCP

git clone https://github.com/stass/lldb-mcp.git && cd lldb-mcp && pip install mcp
{
  "mcpServers": {
    "lldb-mcp": {
      "command": "python3",
      "args": [
        "/path/to/lldb-mcp/lldb_mcp.py"
      ]
    }
  }
}

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the LLDB-MCP config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of LLDB-MCP's tools to confirm it's connected.

Before you start

  • Python 3.7+
  • LLDB installed on the system
  • Claude desktop app with MCP support
  • The mcp Python package (pip install mcp)

What LLDB-MCP can do in Cursor

lldb_start

Start a new LLDB session.

lldb_terminate

Terminate an LLDB session.

lldb_list_sessions

List all active LLDB sessions.

lldb_load

Load a program into LLDB.

lldb_attach

Attach to a running process.

lldb_load_core

Load a core dump file.

lldb_run

Run the loaded program.

lldb_continue

Continue program execution.

Security

The server can attach to running processes and execute arbitrary LLDB commands on the host. Check for permission issues when attaching to processes. Enable debug mode with the --debug flag for detailed logging.

LLDB-MCP + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the LLDB-MCP config there under the "mcpServers" key and restart the client.

Is LLDB-MCP safe to use with Cursor?

The server can attach to running processes and execute arbitrary LLDB commands on the host. Check for permission issues when attaching to processes. Enable debug mode with the --debug flag for detailed logging.

How do I run LLDB commands that don't have a dedicated function?

Use the lldb_command tool to execute arbitrary LLDB commands directly.

How do I enable detailed logging?

Start the server with the --debug flag to enable debug mode for detailed logging.

What should I do if LLDB commands are timing out?

Check that LLDB is installed correctly and verify the path to LLDB when starting a new session.

View repo Full LLDB-MCP page