mcp-lsp-bridge

MCP LSP Bridge exposes Language Server Protocol capabilities to MCP-compatible agents, enabling code intelligence features such as symbol search, navigation, diagnostics, and safe refactoring across 20+ languages. It acts as a bridge between your MCP client (for example Claude Code) and various language servers configured via lsp_config.json. Once running, you can access LSP tools through your MCP client to perform tasks like finding definitions, viewing hover information, listing references, renaming symbols, formatting code, and applying quick fixes with optional previews. The project emphasizes multi-language support, project analysis, and improved tooling integration so you can analyze and refactor large codebases across languages like Go, Python, JavaScript/TypeScript, Rust, Java, and more.

To use it within an MCP client, configure the lsp MCP server in your client’s MCP configuration (or add a --config path to the bridge). Create or provide an lsp_config.json that defines the language servers you want the bridge to manage, then run the bridge so the MCP client can query and execute LSP-powered tools through the standard MCP interface. You’ll find a set of documentation references in the repository for constructing your lsp_config.json and understanding the available tools and commands. Once set up, you can invoke the tools via your MCP client’s tool palette or command surface to perform code intelligence and editing tasks across supported languages.

Prerequisites:

• Go installed if building from source (go1.x+)
• Access to an MCP client (e.g., Claude Code) that supports MCP integrations
• Optional: Docker if you prefer running from an image

Option A: Build from source

1. Clone the repository: git clone https://github.com/rockerboo/mcp-lsp-bridge.git cd mcp-lsp-bridge
2. Build the binary: go build -o mcp-lsp-bridge ./...
3. Move the binary to a directory in your PATH, for example: mv mcp-lsp-bridge /usr/local/bin/

Option B: Use a prebuilt release

1. Download the appropriate release for your platform from the project's releases page.
2. Ensure the binary is executable and in your PATH.

Configuration steps (required after installation):

1. Create an lsp_config.json defining the language servers you want to run under the bridge.
2. In your MCP client configuration, add the lsp server as shown in the Quick Start:

{
  "mcpServers": {
    "lsp": {
      "type": "stdio",
      "command": "mcp-lsp-bridge",
      "args": ["--config", "lsp_config.json"],
      "env": {}
    }
  }
}

3. Start or reload your MCP client so it picks up the new server configuration.

Tips and notes:

• The bridge relies on an lsp_config.json file to define and configure language servers. Place this file in a location accessible to the bridge and reference it via the --config flag when starting the bridge.
• If you run into environment-related issues, ensure the bridge binary has the necessary permissions and that any external language servers referenced in lsp_config.json are installable on your system.
• The base Docker image is available for extending with your own LSP servers; use it if you want to encapsulate the bridge with specific servers.
• Since the project is under active development, expect interface changes and frequent updates. Pin versions where possible and review the docs folder for the latest guidance.
• Ensure your MCP client supports standard LSP tool usage: you may need to grant appropriate access in the client to the bridge process.