lsp-mcp
Provides an MCP server that exposes language-aware code intelligence by wrapping one or more LSP (Language Server Protocol) servers (e.g., typescript-language-server) so LLM/agent clients can request LSP features over MCP.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No explicit TLS/auth/scope model is described; the likely stdio/local execution pattern reduces network exposure but increases risk if run with broad filesystem access. The README suggests mounting local directories into a container, which can expose sensitive code/assets; sandboxing and least-privilege mounting are important. Security hygiene beyond dependency selection is not documented in the provided materials.
⚡ Reliability
Best When
You can run the MCP server locally/in your infrastructure (often alongside Docker) and want LLMs to query LSP features for the files you provide to the runtime.
Avoid When
You need centralized managed hosting with documented SLAs, strong auth controls, or you cannot safely mount/share code into the server/container environment.
Use Cases
- • Enable LLM/agents to use code-aware LSP capabilities (symbols, go-to-definition, references, diagnostics, etc.) for one or more languages in a repo
- • Editor/agent context enrichment for programming assistants (e.g., Claude Desktop, Cursor, MCP CLI clients)
- • Rapidly adding LSP-backed tooling to agent workflows via Docker or npx
- • Dynamic LSP method exposure driven by an LSP JSON Schema/config
Not For
- • Production-grade, security-sensitive deployments without reviewing the runtime permissions and sandboxing
- • Environments requiring a strongly specified REST/SDK integration contract
- • Use cases needing fine-grained, per-user authorization and auditability built into the service
- • High-reliability, long-lived sessions without additional operational hardening
Interface
Authentication
No authentication/authorization is described in the provided README. MCP clients generally connect over stdio (e.g., Claude Desktop) or local execution, so auth may be delegated to deployment environment rather than built into the service.
Pricing
No pricing information provided (appears to be open-source).
Agent Metadata
Known Gotchas
- ⚠ README notes this is a POC state, implying rough edges and incomplete spec coverage.
- ⚠ Claude Desktop via npx is described as finicky (tools may still work even when it reports failure).
- ⚠ Multiple LSPs at the same time are mentioned but later qualified as not yet supported in some npx workflow, so config expectations may vary by integration path.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for lsp-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.