TypeScript LSP MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getTypeAtPositionC | Get the TypeScript type at a specific position in a file |
| getDefinitionA | Get the definition location(s) for a symbol at a position (go-to-definition) |
| getReferencesB | Find all references to a symbol at a position |
| getHoverB | Get hover information (documentation, type signature) at a position |
| getCompletionsC | Get autocomplete suggestions at a position |
| getDiagnosticsB | Get TypeScript diagnostics (errors, warnings) for a file or project |
| traceTypeC | Trace where a type comes from and how it is composed |
| runTypeTestsB | Run type test assertions from files with @ts-lsp-mcp expect-type/expect-error comments |
| checkInlineCodeA | Type-check inline TypeScript code without creating a file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.