LSPs should expose their api through shell commands - then integrating it with a...

anamexis · 2025-12-22T21:34:26 1766439266

You could use a CLI frontend for LSP, e.g. https://github.com/valentjn/lsp-cli

But why would that be better than LLMs using the LSP with a dedicated tool rather than a shell command tool?

wild_egg · 2025-12-22T21:56:46 1766440606

CLIs don't use context space when unused. I find them almost universally preferable just because of that.

Models get stupid after the first 80-100k tokens are used so keeping bloated tools out of the window unless completely necessary is a pretty hard requirement for effective AI use IMO.

anamexis · 2025-12-22T22:01:15 1766440875

Well you need to use context space somehow, to tell Claude that the LSP CLI exists and how to use it.

wild_egg · 2025-12-22T23:19:44 1766445584

It takes a dozen tokens to put "when you need to do X, run `foo --help` and use it" in your CLAUDE.md.

Plenty of MCPs and plugins and whatnot out there idly consuming 5-25k tokens 24/7. How is that the same?

anamexis · 2025-12-22T23:23:05 1766445785

Because you can enable/disable MCPs and plugins just like you can choose not to include that context in CLAUDE.md .

I do it all the time. I have several MCPs configured but only enable them on demand.