lspz 0.10.5

AI-friendly LSP compression proxy
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99

# Claude Desktop Integration

This guide explains how to configure Claude Desktop to use lspz's MCP tools for LSP-powered code analysis.

## Prerequisites

- [lspz](https://github.com/straydragon/lspz) installed (`cargo install lspz` or `cargo install --path .` from the repo root)
- LSP servers installed for your languages (e.g., `rust-analyzer`, `gopls`, `basedpyright`, `typescript-language-server`)
- [Claude Desktop](https://claude.ai/download) installed

## Configuration

Add the following to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "lspz": {
      "command": "lspz",
      "args": ["mcp"]
    }
  }
}
```

**File location:**

| Platform | Path |
|----------|------|
| macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json` |
| Linux | `~/.config/Claude/claude_desktop_config.json` |

## Tools Available

After restarting Claude Desktop, the following tools will appear in the MCP tool list:

| Tool | Description | Parameters |
|------|-------------|------------|
| `get_diagnostics` | Returns LSP diagnostics for a file (optionally compressed) | `uri`, `backend`, `language` |
| `get_completions` | Returns completions at a cursor position | `uri`, `backend`, `language`, `line`, `character` |
| `get_symbols` | Returns document symbols for a file | `uri`, `backend`, `language` |

## Usage Examples

Once configured, you can ask Claude to analyze your code:

> "Check diagnostics for file:///home/user/project/src/main.go using gopls in Go"

> "Get completions at line 42, character 10 for file:///home/user/project/app.ts using typescript-language-server in typescript"

> "List symbols in file:///home/user/project/src/lib.rs using rust-analyzer in rust"

### URI Format

All tools require `file://` URIs. Note that the path must be absolute:

- Correct: `file:///home/user/project/main.go`
- Incorrect: `/home/user/project/main.go`
- Incorrect: `file://relative/path.rs`

## Log Levels

To increase logging verbosity, pass a log level flag:

```json
{
  "mcpServers": {
    "lspz": {
      "command": "lspz",
      "args": ["mcp", "--log-level", "debug"]
    }
  }
}
```

Available levels: `trace`, `debug`, `info` (default), `warn`, `error`.

## Troubleshooting

### "backend not found"
Ensure the LSP server is installed and available in your `PATH`. Test with `which rust-analyzer` (or your server's command).

### "file not accessible"
The file path must exist and be readable by the lspz process. Claude Desktop's sandboxed process may have restricted filesystem access. Use absolute paths.

### "URI must start with file://"
Ensure you prefix the file path with `file://` as shown in the examples above.

### No tools appearing
- Verify the MCP server is running: run `lspz mcp` directly in a terminal to check for startup errors.
- Check Claude Desktop's MCP logs for connection issues.
- Restart Claude Desktop after modifying the configuration.

## References

- [lspz README](https://github.com/straydragon/lspz#readme)
- [ROADMAP.md](https://github.com/straydragon/lspz/blob/main/ROADMAP.md)
- [LSP Compatibility Spec](../specs/lsp-compatibility.md)