Chromia LSP MCP
OfficialRelated Servers
Alternatives to Chromia LSP MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP clients to pull real-time language-server data from a running editor instance, including diagnostics, hover/definition/signature and type information, and symbol references with usage context. It also supports workspace-wide symbol renaming, opening files, and command execution, letting agents validate changes without waiting on slow tsc/eslint runs.-

karellen-lsp-mcpofficial
AlicenseNot gradedqualityCmaintenanceProvides LLM clients with structured code intelligence through LSP servers, enabling queries for definitions, references, call hierarchies, and more.3Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and compatible clients to query real-time editor language-server diagnostics, type/symbol information, and code navigation without waiting for slow tsc/eslint checks, plus workspace-aware operations such as finding references, renaming symbols, opening files, and executing editor commands.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to obtain real-time language-server diagnostics, type information, symbol definitions, references, and workspace-wide renames directly from open editor instances, avoiding slow external type and lint checks.-
- AlicenseNot gradedqualityFmaintenanceProvides AI agents with language-aware code analysis through the Language Server Protocol, enabling tasks like getting code insights and diagnostics.5 npm192MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP clients to query real-time LSP diagnostics, type information, definitions, references, and workspace-wide symbol renaming through the editor's language servers, avoiding slow tsc/eslint checks.-
TDQS
Scored across 10 tools
Each tool addresses a distinct LSP operation, but save_document and open_document have identical descriptions, creating potential confusion about their respective roles. Hover, completions, code actions, diagnostics, and lifecycle tools are otherwise clearly separated.
Most tools follow a verb_noun pattern with get_ for queries and open/save/close for document management. Minor inconsistencies exist: start_lsp lacks 'server' while restart_lsp_server includes it, and get_info_on_location is more verbose than sibling get_ tools.
10 tools appropriately cover server lifecycle, document lifecycle, and core LSP queries without redundancy or bloat. This is well within the ideal 3-15 range for a focused MCP server.
The tool set covers the essential LSP workflow: start server, open documents, retrieve diagnostics, hover info, completions, and code actions. However, common LSP features like go-to-definition, find references, formatting, and rename are absent, leaving notable gaps for a full language server experience.