TypeScript LSP MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jaenster/ts-lsp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server