I am on the latest version of Claude Code and nothing comes up when I follow this and search for "mcp". Looks like this feature is quite undercooked at the moment. I'm hoping for a more straightforward way to enable this and ensure the LSP is being used by Claude in the future.
Perhaps because you are searching for "mcp" and not "lsp"?
LOL yeah that would be a solid guess but I just sanity checked and I messed it up only in the comment, in Claude Code when I search for "lsp" I still get no matches.
But in all seriousness, LLMs have their strengths but we’re all wasting tokens and burning the planet unnecessarily getting LLMs to work so inefficiently. Use the best tool for the job; make the tools easier to use by LLMs. This mantra is applicable generally. Not just for coding.
What boggles my mind is. I've been using OpenCode [1] which had this future for at least 6 months. I sometimes baffled by the slow progress of closed source software. Also highly recommend OpenCode you can also use it with your Claude subscription or Copilot one. [1]: https://opencode.ai/
I do like OpenCode, but I get small bugs here and there like flickering, freezing and sometimes just crash all together.
But their configuration setup is the easiest and best out of all the other CLI tools
I literally said this three days ago: https://hachyderm.io/@ed_blackburn/115747527216812176 But in all seriousness, LLMs have their strengths but we’re all wasting tokens and burning the planet unnecessarily getting LLMs to work so inefficiently. Use the best tool for the job; make the tools easier to use by LLMs. This mantra is applicable generally. Not just for coding.
I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding. Imagine how much smaller the context would be for a tool that renames a function than editing hundreds of files. This LSP support is a good start but without the mutation functions it is still pretty lackluster. Plus LSPs aren't as good as…
I completely agree. Likewise I'm amazed Microsoft hasn't done it themselves for Roslyn and Copilot. Roslyn analyzers are so incredibly powerful, and it's being ignored. An explainer for others: Not only can analyzers act as basic linters, but transformations are built right in to them. Every time claude does search-and-replace to add a parameter I want to cry a little, this has been a solved science. Agents + Roslyn…
In a similar vein, I really struggle to understand why copilot is so crap when writing SQL and I'm connected to the database. The database has so much context (schema names, column names, constraints etc.) yet copilot regularly hallucinates the most basic stuff like table and column names, which standard auto complete has managed fine for the last 20+ years.
> This is why we're seeing the bulk of gains from things like MCP and, now, "agents". This is objectively not true. The models have improved a ton (with data from "tools" and "agentic loops", but it's still the models that become more capable). Check out [1] a 100 LoC "LLM in a loop with just terminal access", it is now above last year's heavily harnessed SotA. > Gemini 3 Pro reaches 74% on SWE-bench verified with mi…
I don't understand. You're highlighting a project that implements an "agent" as a counterargument to my claim that the bulk of improvements are from "agents"? Sure, the models themselves have improved, but not by the same margins from a couple of years ago. E.g. the jump from GPT-3 to GPT-4 was far greater than the jump from GPT-4 to GPT-5. Currently we're seeing moderate improvements between each release, with "agen…
I think the point here is that it’s not adding agents on top but the improvements in the models allow the agentic flow.
LSPs should expose their api through shell commands - then integrating it with any LLM would be trivial. And it would also be very useful for humans.
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?
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.
Perhaps because you are searching for "mcp" and not "lsp"?
LOL yeah that would be a solid guess but I just sanity checked and I messed it up only in the comment, in Claude Code when I search for "lsp" I still get no matches.
Interesting. I'd guess you don't have the Claude Plugins marketplace enabled, but I very much agree that the whole plugins/marketplace system seems half-baked in Claude Code.
I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding. Imagine how much smaller the context would be for a tool that renames a function than editing hundreds of files. This LSP support is a good start but without the mutation functions it is still pretty lackluster. Plus LSPs aren't as good as…
Jetbrains seems a bit lost these days. Look at that very recent screw up [0].
I thought about moving after 10+ years when they abandoned the commit modal, and jacked up the plan prices, but I barely understand how to commit things in Vscode anyway. Let's see in 2026.