TypeScript LSP MCP
Related Servers
Alternatives to TypeScript LSP MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to interact with TypeScript projects through compiler-level code intelligence, providing tools for navigation, type information, diagnostics, refactoring, and semantic search.29722 npm4Apache 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 retrieve real-time LSP diagnostics, symbol and type information, and code references, and to perform workspace-aware file operations such as symbol renaming. This avoids waiting for slow tsc/eslint checks while improving code navigation and editing accuracy.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to access real-time VSCode LSP diagnostics, type information, and code navigation without slow tsc/eslint checks, plus symbol renaming and file operations.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and AI IDEs to pull real-time LSP diagnostics, type/hover/signature information, and code navigation from a running editor, replacing slow tsc and eslint runs. Also supports workspace-wide symbol renaming, reference lookup with usage context, opening files, and listing open editor windows.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.-
TDQS
Scored across 9 tools
Each tool targets a distinct LSP feature (type-checking, completions, definitions, diagnostics, hover, references, type queries, type tests, type tracing). There is no overlap or ambiguity between tools.
Most tools follow a 'get' + noun pattern (getCompletions, getDefinition, etc.), with two exceptions: 'checkInlineCode' uses 'check' and 'runTypeTests' uses 'run'. This minor inconsistency prevents a perfect score.
9 tools is an appropriate size for a TypeScript LSP server. It covers essential features without being bloated or too sparse.
The tools cover core LSP operations (diagnostics, hover, definition, references, completions, type queries) and even include niche features (type tracing, type tests). Missing common operations like code actions, rename, or formatting, but the set is largely complete for its apparent purpose.