MCP Hub
Back to servers

LSP-MCP Bridge

A universal bridge that connects MCP-compatible clients to any Language Server Protocol (LSP) provider, enabling features like hover docs, definitions, and diagnostics across multiple programming languages through a single binary.

Tools
6
Updated
Jan 3, 2026
Validated
Jan 9, 2026

lsp-mcp-rs

MCP server that bridges to any LSP. One binary, multiple language servers.

Build

cargo build --release

Binary: target/release/lsp-mcp-rs.exe

Configure

Create config.toml next to the binary:

[servers.lua]
command = "C:/path/to/lua-language-server.exe"
args = ["--stdio"]
extensions = [".lua"]

[servers.rust]
command = "rust-analyzer"
args = []
extensions = [".rs"]

[servers.python]
command = "pyright-langserver"
args = ["--stdio"]
extensions = [".py"]

Add to Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "lsp": {
      "command": "X:\\path\\to\\lsp-mcp-rs.exe",
      "args": []
    }
  }
}

Tools

ToolDescription
lsp_hoverGet docs/type at position
lsp_definitionGo to definition
lsp_referencesFind all references
lsp_symbolsList symbols in file
lsp_diagnosticsGet errors/warnings
lsp_serversList configured servers

All position arguments are 0-indexed.

How it works

  1. MCP request comes in with a file path
  2. File extension maps to configured LSP server
  3. LSP spawns on first use, stays running
  4. Request forwarded to LSP, response returned via MCP

License

MIT

Authors

DC, KALIC, Stryk9190

Reviews

No reviews yet

Sign in to write a review