mcpbeat

Typescript Lsp

clickhouse/typescript-lsp

> Use the TypeScript language server (`typescript-language-server`) for precise references, hover (type signatures and JSDoc, including `@deprecated` info), workspace-wide symbol search, completions, and per-file type diagnostics. Prefer this over grep when you need to resolve a symbol's actual definition, find all usages of an exported API, or inspect inferred types across the `packages/*` workspaces. The server is preinstalled as a root devDependency — run the repository `setup` skill (`npm install`) first so `node_modules` is populated. Do NOT use this skill for downstream projects that merely depend on `@clickhouse/client`; it is specific to working inside this repo.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
326
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/ClickHouse/clickhouse-js --skill typescript-lsp

The instruction itself

5 sections, as written by the author

TypeScript Language Server in clickhouse-js

typescript-language-server is declared as a root devDependency, so after

npm install (see the setup skill) it is available via npx and uses the

workspace-local typescript (6.x) compiler, matching CI exactly.

Starting the server

From the repo root:

npx typescript-language-server --stdio

It speaks LSP (JSON-RPC, Content-Length-framed) over stdio. There is no

extra configuration: each packages/* workspace, tests/clickhouse-test-runner,

examples/node, and examples/web has its own tsconfig.json, and the

server picks the nearest one per opened file automatically.

Protocol essentials

  • Send initialize with rootUri/workspaceFolders pointing at the repo

root, then the initialized notification.

  • Send textDocument/didOpen with the full file text for every file you

want to query (the server reads dependencies from disk on its own; only

files you query positions in need to be opened).

  • Positions are 0-based (line and character).

Verified capabilities (typescript-language-server 5.x, TS 6.x)

| Request | Notes |

| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| textDocument/hover | Returns the full inferred signature + JSDoc markdown |

| textDocument/definition | Resolves across workspace packages via source, not dist/ |

| textDocument/references | Within the opened file's project |

| workspace/symbol | e.g. query ClickHouseClient finds class + re-exports |

| textDocument/completion | Context-aware member completions |

| Diagnostics | Push only (textDocument/publishDiagnostics notifications, sent ~1–3s after didOpen). The pull textDocument/diagnostic request is _not_ supported (-32601) — wait for the push notification instead. |

Tips

  • If your environment provides built-in LSP/code-intelligence tooling, point

it at npx typescript-language-server --stdio with the repo root as the

workspace folder.

  • For one-off scripted queries, spawn the server from Node, frame messages

with Content-Length: <bytes>\r\n\r\n<json>, and match responses by id.

  • A full workspace typecheck is still npm run build && npm run typecheck

(build first — some workspaces import compiled dist/ outputs); the LSP is

for targeted, interactive queries, not for CI-equivalent validation.

How to use it

Copy the folder

Take clickhouse/typescript-lsp from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm, npx. Without those the skill loads but fails at the first command.