[all-commits] [llvm/llvm-project] 5ddad7: [lldb-mcp] Replace byte forwarding with a protocol...

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 5ddad72b154e4c4ddc2547b6cd17abd7b9a6ae53
      https://github.com/llvm/llvm-project/commit/5ddad72b154e4c4ddc2547b6cd17abd7b9a6ae53
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-07-10 (Fri, 10 Jul 2026)

  Changed paths:
    M lldb/include/lldb/Protocol/MCP/Protocol.h
    M lldb/source/Plugins/Protocol/MCP/ProtocolServerMCP.cpp
    M lldb/source/Protocol/MCP/Protocol.cpp
    M lldb/tools/lldb-mcp/CMakeLists.txt
    A lldb/tools/lldb-mcp/Multiplexer.cpp
    A lldb/tools/lldb-mcp/Multiplexer.h
    M lldb/tools/lldb-mcp/lldb-mcp.cpp

  Log Message:
  -----------
  [lldb-mcp] Replace byte forwarding with a protocol-aware multiplexer (#208506)

To serve several LLDB instances behind one endpoint it has to act as a
multiplexer. This PR adds a Multiplexer that presents a unified MCP
server to the client. It answers initialize and tools/list locally, and
forwards tools/call and the resource requests to the different instances
through an mcp::Client (added in #208371), relaying the answer back.

For now, this still drives a single backend. Discovering and routing
across several instances is coming next.

Assisted-by: Claude



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications