mcp-language-server and mcpls
These are complementary tools that operate in opposite directions: mcp-language-server exposes MCP semantic capabilities to LSP clients, while mcpls exposes LSP capabilities as MCP tools, allowing bidirectional bridging between the two protocol ecosystems.
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 mcpls
bug-ops/mcpls
Universal MCP to LSP bridge - expose Language Server Protocol capabilities as MCP tools for AI agents
Bridges MCP and LSP by spawning language servers (rust-analyzer, pyright, gopls, etc.) and exposing their capabilities—type inference, cross-references, diagnostics, call hierarchies—as MCP tools. Uses project marker heuristics to automatically detect and start only relevant servers, with graceful degradation if servers fail. Integrates with AI coding assistants like Claude through MCP's stdio transport, enabling semantic code understanding beyond text-based reasoning.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work