The C# LSP plugin brings capabilities that go far beyond what text search tools like Grep can offer.
Operations such as hover (showing type info or documentation inline), go to implementation (jumping straight to the concrete code behind an interface), and incoming/outgoing calls (mapping call hierarchies) rely on the Language Server Protocol’s deep understanding of the code. Grep, by contrast, only matches raw text and has no awareness of symbols or relationships.
That’s why LSP isn’t just a faster search — it’s a smarter, language-aware tool that fills in the gaps where Grep stops. For developers navigating large projects, these features save time and reduce friction, making it easier to move seamlessly between definitions, implementations, and call flows. In short, LSP delivers structured insights that text search alone can’t replicate.
How to install it ?
Requirements: .NET 10 .SDK
Do a /plugins and on the Discover tab search for csharp-lsp.
Once installed run /reload-plugins you should see at least one plugin on LSP servers (I have two in my case)
Double checking it
Now go to a C# project, in the root of it, try the simple double check message like so:
Is the csharp lsp plugin up and running ?
All set and good to go
Now Claude is going to call the LSP methods automatically when needed.
How does it work?
LSP is a background service that runs inside Claude, it indexes the project so it can help Claude during its activity.
When am I going to save tokens?
Over the time, LSP server will index your changes, and you are going to save tokens during the same.
With the LSP plugin, you simply use go to implementation and jump directly to the exact class that defines the method. From there, you can use incoming calls to see every place in the codebase where that method is invoked. And this is something grep can’t do.
Conclusion
In short, the C# LSP plugin doesn’t just add convenience — it helps save tokens by handling operations that Grep can’t do at all. Features like hover, go to implementation, and incoming/outgoing calls rely on the Language Server Protocol’s semantic understanding of code, giving developers precise navigation and insights without wasting effort on blind text searches. Where Grep stops at raw matching, LSP leverages compiler knowledge to streamline workflows, reduce errors, and make exploring complex projects far more efficient.