TypeScript LSP MCP
# ts-lsp-mcp
[](https://www.npmjs.com/package/ts-lsp-mcp)
[](https://www.npmjs.com/package/ts-lsp-mcp)
[](https://github.com/jaenster/ts-lsp-mcp/blob/main/LICENSE)
MCP server exposing TypeScript LSP-like functionality to AI agents.
Gives AI agents the same "what's the type at this position?" powers that IDE users have.
## Quick Start
### Install into Claude Code
```bash
# Install to current project (recommended)
npx ts-lsp-mcp install cc
# Or install globally for all projects
npx ts-lsp-mcp install cc --global
```
That's it! The MCP server is now available to Claude Code.
### Uninstall
```bash
npx ts-lsp-mcp uninstall cc
```
## Manual Installation
### Global npm install
```bash
npm install -g ts-lsp-mcp
ts-lsp-mcp install cc
```
### Manual config
Add to your Claude Code MCP config (`.mcp.json` in project or `~/.claude/settings.json` globally):
```json
{
"mcpServers": {
"ts-lsp-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "ts-lsp-mcp", "serve", "--stdio"]
}
}
}
```
### HTTP/SSE Mode
For remote clients or debugging:
```bash
ts-lsp-mcp --http --port 3000
```
Endpoints:
- `GET /sse` - SSE connection
- `POST /message` - Send messages
- `GET /health` - Health check
## Available Tools
| Tool | Description |
|------|-------------|
| `getTypeAtPosition` | Get the TypeScript type at a specific file:line:col |
| `getDefinition` | Go to definition |
| `getReferences` | Find all references |
| `getHover` | Get hover documentation |
| `getCompletions` | Get autocomplete suggestions |
| `getDiagnostics` | Get type errors and warnings |
| `traceType` | Trace where a type comes from and how it's composed |
| `runTypeTests` | Run type assertions from `@ts-lsp-mcp` comments |
| `checkInlineCode` | Type-check inline TypeScript without creating files |
## Type Test Assertions
Add type assertions to your code:
```typescript
// @ts-lsp-mcp expect-type: string
const name = user.name;
// @ts-lsp-mcp expect-type: User
const user = createUser({ name: 'Alice' });
// @ts-lsp-mcp expect-error: 2322
const bad: number = "oops"; // Should have error 2322
```
Run tests:
```
runTypeTests({ file: "src/types.ts" })
runTypeTests({ pattern: "**/*.type-test.ts" })
```
## Example Usage
### Get type at position
Supports unified `file:line:col` format:
```json
{
"tool": "getTypeAtPosition",
"arguments": {
"file": "src/user.ts:10:5"
}
}
```
Or separate parameters:
```json
{
"tool": "getTypeAtPosition",
"arguments": {
"file": "src/user.ts",
"line": 10,
"col": 5
}
}
```
Response:
```json
{
"type": "User",
"expanded": "{ id: number; name: string; email: string }",
"symbol": "user",
"kind": "variable"
}
```
### Check for type errors
```json
{
"tool": "getDiagnostics",
"arguments": {
"file": "src/user.ts"
}
}
```
### Type-check inline code
```json
{
"tool": "checkInlineCode",
"arguments": {
"code": "const x: number = 'bad';"
}
}
```
Response:
```json
{
"valid": false,
"diagnostics": [{
"line": 1,
"col": 7,
"code": 2322,
"message": "Type 'string' is not assignable to type 'number'."
}]
}
```
## Features
- **Multi-project support**: Works with monorepos with multiple tsconfigs
- **Auto-discovery**: Finds tsconfig.json automatically
- **Smart file resolution**: Accepts absolute, relative, or unique filenames
- **Virtual files**: Type-check unsaved code with the `content` parameter
- **Efficient**: Long-lived daemon caches TypeScript projects
## CLI Options
```
ts-lsp-mcp [command] [options]
Commands:
serve Start the MCP server (default)
install <target> Install into an AI assistant (cc, claude-code, claude)
uninstall <target> Uninstall from an AI assistant
Serve options:
--stdio Use stdio transport (default)
--http Use HTTP/SSE transport
--port <port> HTTP server port (default: 3000)
--host <host> HTTP server host (default: 127.0.0.1)
--debug Enable debug logging
Install options:
--global Install globally (user scope) instead of project
--name <name> Custom name for the MCP server (default: ts-lsp-mcp)
General:
-V, --version Output version number
-h, --help Display help
```
## License
MIT
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.