How I’m Using (New) Claude Code LSP to Code & Fix Bugs Faster (Language Server Protocol)
Claude Code LSP
Claude Code now supports Language Server Protocol (LSP), and I’m using it to make a huge difference in my coding workflow.
If you have no idea what LSP is, you’ve likely used it without knowing — every single day inside your code editor.
What is LSP?
When you’re coding in VS Code, and you hover over a function, that tooltip showing you the parameters and documentation?
Press enter or click to view image in full size
That’s LSP.
When you right-click a variable and hit “Go to Definition” and it jumps straight to the exact file and line? That’s LSP.
When you see those red squiggly lines under your code telling you something is wrong before you even run it? That’s LSP.
When you start typing a function name and VS Code autocompletes it with the correct parameters? You guessed it — LSP.
Press enter or click to view image in full size
Microsoft created the Language Server Protocol so that code intelligence could be built once and work everywhere.
Your TypeScript language server works in VS Code, in Cursor, in JetBrains, and now — it works in Claude Code too.
Claude Code Without LSP
Before this update, Claude Code was doing something clever but limited.
When Claude needed to find where a function was defined, it was essentially doing a fancy grep — searching through text patterns.
When it needed to understand your code structure, it was parsing raw text.
This works surprisingly well. LLMs are good at understanding code as text because they’ve seen so much of it.
But it’s fundamentally limited.
You’re asking AI to reconstruct, from raw text, the kind of semantic understanding that your IDE already has built in.
If you’ve ever asked Claude Code to “find all references to this function” and watched it read through dozens of files one by one, you know what I mean.
Native LSP Support
Claude Code version 2.0.74 shipped with native LSP support.
This means Claude Code now has access to the same code intelligence your IDE uses:
- Go-to-definition — Jump to symbol definitions instantly
- Find references — Locate every usage of a function or variable across your entire codebase
- Hover documentation — See type hints, parameters, and descriptions
- Real-time diagnostics — Catch errors and warnings immediately after edits
Instead of reading 100 files naively, Claude Code can now query the language server directly — just like you do when you Ctrl+Click on a function in VS Code.
This is how professional developers navigate code. And now Claude Code can do it too.
Setting Up LSP in Claude Code
The setup is straightforward. I’ll walk you through it step by step.
Step 1: Enable LSP Tools
First, you need to enable the LSP tool in Claude Code. Add this to your shell profile (.bashrc, .zshrc, or equivalent):
export ENABLE_LSP_TOOLS=1
Restart your terminal or run source ~/.zshrc to apply the change.
Press enter or click to view image in full size
Step 2: Install the Language Server Plugin
Claude Code uses plugins to connect with language servers. The easiest way to install one is through the /plugin command.
In Claude Code, type:
/plugin
This opens the plugin interface. Navigate to the available plugins and find the one for your language.
Press enter or click to view image in full size
For Python, select pyright-lsp (Microsoft’s static analyzer).
Press enter or click to view image in full size
For TypeScript/JavaScript, select vtsls or typescript-lsp.
Press enter or click to view image in full size
Select “Install for me only” (user scope) and let it install.
Step 3: Install the Language Server Binary
The plugin requires the actual language server binary to be installed on your system.
For Python (Pyright):
pip install pyright
For TypeScript/JavaScript:
npm install -g @vtsls/language-server typescript
For Go:
go install The Go Programming Language
For Rust:
rustup component add rust-analyzer
Press enter or click to view image in full size
Step 4: Restart Claude Code
After installing the plugin and language server binary, restart Claude Code for the changes to take effect.
claude
Step 5: Verify It’s Working
Run /plugin again and check the “Installed” tab. You should see your LSP plugin listed.
Press enter or click to view image in full size
You can also verify by asking Claude Code to use LSP on a file:
Find references to this function using LSP
If it works, you’ll see Claude Code use the find_references tool instead of grep.
Supported Languages
Claude Code LSP supports 10+ languages out of the box:
Press enter or click to view image in full size
If your language isn’t listed, you can create your own LSP plugin. Check the Claude Code documentation for custom plugin setup.
5 LSP Operations You Need to Know
Once LSP is configured, Claude Code gains access to five powerful operations. These map directly to what you’re used to in VS Code.
1. goToDefinition — Jump to Where Code is Defined
This is the equivalent of Ctrl+Click (or Cmd+Click on Mac) in your IDE.
Ask Claude Code something like:
Where is the processRequest function defined use LSP?
Press enter or click to view image in full size
With LSP enabled, Claude Code doesn’t search through files randomly. It queries the language server and jumps straight to the exact file and line number.
2. findReferences — Find All Usages Across Your Codebase
This is the killer feature for debugging and refactoring.
Instead of Claude reading through dozens of files, it queries the language server to find every place a function, variable, or class is used.
Press enter or click to view image in full size
Find all references to the displayError function use LSP
Press enter or click to view image in full size
This is incredibly useful when you’re:
- Refactoring code and need to know what will break
- Tracking down a bug introduced by a recent change
- Understanding how a function is used across the project
3. hover — Get Documentation and Type Info
When you hover over a function in VS Code, you see its signature, parameters, and documentation.
Claude Code can now do the same thing.
What parameters does the displayBooks function accept use LSP?
With LSP, Claude Code queries the language server and returns:
- Required parameters
- Optional parameters
- Parameter types
- Descriptions and documentation
Press enter or click to view image in full size
This is especially powerful for dynamically typed languages like Python, where Claude might otherwise guess incorrectly.
From my example above, you see that it missed it since it does not have the LSP for HTML
4. documentSymbol — List All Symbols in a File
Want a quick overview of everything in a file? Classes, functions, variables — all of it.
Show me all the symbols in backend/index.js use LSP
Claude Code returns a structured list of every symbol defined in that file.
5. workspaceSymbol — Search Symbols Across the Project
This is like a project-wide search, but smarter.
Instead of searching text, it searches for actual code symbols — function names, class names, and constants.
Find all methods that contain innerHTML
Bonus: Real-Time Diagnostics
LSP doesn’t just help you navigate code — it catches errors too.
After every edit, the language server reports diagnostics (errors, warnings, hints) back to Claude Code.
This means Claude can:
- See type errors immediately after writing code
- Catch missing imports before you run anything
- Identify issues that would otherwise only show up at runtime
Practical Examples — LSP in Action
Let me show you how I’m actually using this in my projects.
Example 1: Tracking Down Where a Function is Used
I was working on this project called AseBook Finder — a simple app that uses the Gemini API to recommend books based on user preferences.
The frontend has several utility functions, and I needed to find every place where my displayBooks function was being called.
Without LSP, Claude Code would grep through files looking for the text “displayBooks”. It works, but it can miss context or return false positives.
With LSP, I asked:
Find all references to the displayBooks function using LSP
Claude Code queried the language server and returned the exact locations:
- The function definition
- The call inside the fetch success handler
- Any other places it’s referenced
No scanning through files manually. Just precise, instant results.
Example 2: Understanding Function Parameters
In the same project, I have a displayError function that handles error messages.
Simple enough, but what if I wanted Claude to understand exactly how it works before generating new code that uses it?
I asked:
What parameters does displayError accept?
With LSP, Claude Code queried the language server and returned the function signature — showing that it takes a message parameter.
This matters more in larger projects where functions have multiple parameters, default values, or complex types. Claude can now read the actual signature instead of guessing from context.
Example 3: Finding Where API Calls Are Made
I wanted to trace where the Gemini API recommendations endpoint was being called in the app.
Find all references to /api/recommendations in the codebase
Claude Code found the fetch call in the click handler — line 27 where it posts to http://localhost:3000/api/recommendations .
This is useful when you’re debugging API issues or need to understand the data flow in your app.
Example 4: Catching Errors Before Running
I was refactoring the escapeHtml function and accidentally introduced an error — I misspelled a variable name.
Normally, I wouldn’t catch this until the browser threw an error.
But with LSP enabled, Claude Code flagged it immediately through diagnostics.
The language server reported the issue, and Claude caught it before I even ran the code.
Think about how you work in VS Code:
- You Ctrl+Click to jump to definitions
- You right-click to find all references
- You hover to see function signatures
- You rely on red squiggles to catch errors
You don’t just search through files naively. You use these shortcuts because they’re faster and more reliable. Claude Code can now do the same thing.
It’s not pattern matching on text anymore. It’s querying the language server — the same tool that powers your IDE’s intelligence.
This makes Claude Code operate more like a professional developer and less like a text search engine.
Limitations and Tips
LSP in Claude Code is powerful, but it’s still new.
Here’s what you should know.
Current Limitations
- It’s still raw. Version 2.0.74 introduced LSP support, but there are some bugs. Some users report issues with plugin loading or servers not starting correctly. If you run into problems, check the Claude Code GitHub issues — fixes are coming quickly.
- No UI indication. Unlike VS Code, there’s no visual indicator showing that your LSP server is running. You won’t see a status bar icon or anything like that. The only way to confirm is to test it with an actual query.
- The language server must be installed separately. The plugin alone isn’t enough. You need the actual language server binary (pyright, gopls, rust-analyzer, etc.) installed on your system and available in your PATH.
- Some operations require specific syntax. LSP was designed for cursor positions (file, line, column). While Claude Code handles this well, occasionally you may need to be more explicit in your prompts — like specifying “use LSP” directly.
My Tips for Getting the Most Out of LSP
Tip 1: Always verify your setup.
After installing a plugin, run /plugin and check the Installed tab. Then test with a simple query like “find references to X using LSP” to confirm it’s working.
Tip 2: Use LSP for navigation, not everything.
LSP is great for:
- Finding references across large codebases
- Understanding function signatures and parameters
- Jumping to definitions quickly
- Catching type errors early
For simple text searches or grep-style queries, Claude Code’s regular tools work fine.
Tip 3: Restart Claude Code after plugin changes.
If you install a new LSP plugin or update your language server, restart Claude Code. The servers are loaded at startup.
Tip 4: Check your PATH.
If Claude Code says “No LSP server available,” the binary probably isn’t in your PATH. Run which pyright (or your language server) In a terminal to verify.
Tip 5: Be explicit when needed.
If Claude Code isn’t using LSP when you expect it to, add “use LSP” to your prompt:
Find all references to authenticateUser using LSP
This nudges Claude to use the language server instead of falling back to grep.