mcp-language-server and lsp-mcp-server
These are complementary tools operating in opposite directions: mcp-language-server exposes LSP capabilities to MCP clients, while lsp-mcp-server bridges MCP clients (like Claude Code) to existing LSP servers, together enabling bidirectional semantic code intelligence integration.
About mcp-language-server
isaacphi/mcp-language-server
mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, and diagnostics.
Built on the Model Context Protocol, it wraps any stdio-based language server (gopls, rust-analyzer, pyright, clangd, etc.) to expose LSP capabilities as MCP tools for LLM clients. Beyond standard definition and references, it includes file editing via line-based text operations and hover documentation retrieval. Supports multi-language codebases through pluggable language server backends with configurable workspace paths and environment variables.
About lsp-mcp-server
ProfessioneIT/lsp-mcp-server
An MCP (Model Context Protocol) server that bridges Claude Code to Language Server Protocol (LSP) servers, enabling semantic code intelligence capabilities.
Exposes 24 MCP tools providing semantic code intelligence (go-to-definition, find references, rename, diagnostics, call/type hierarchy) across 10 languages via stdio-based JSON-RPC communication with language servers. Features automatic server lifecycle management, multi-root workspace support with per-workspace server instances, and push-based diagnostics caching for real-time error tracking. Integrates with any LSP-compatible server (TypeScript, Python, Rust, Go, C/C++, Ruby, PHP, Elixir, Kotlin, Java) and configures directly into Claude Code via `.mcp.json`.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work