Claude Code LSP: Code Intelligence Plugins Explained
Claude Code LSP plugins connect Claude to a language server, so it sees type errors after edits and finds definitions by symbol. Install, languages, fixes.
Josh Pocock7 min read
AI Coding
Claude Code LSP
Stride AI Academy
Claude Code LSP support comes through code intelligence plugins. Each one connects Claude Code to a language server for one language, using the Language Server Protocol. Claude then sees the type errors and missing imports its own edits cause, right after each edit, and finds definitions and references by symbol instead of by text search. You install the plugin from Anthropic's official marketplace and the language server binary on your machine.
This guide covers what Claude gains, the official plugins by language, how to install one, how to tell it's working, fixes for common problems, and how to add a language that has no plugin. Everything here was checked against Claude Code's code intelligence plugins docs, the tools reference, plugin components and plugin troubleshooting pages on November 22, 2026.
What a Claude Code language server gives Claude
Without a language server, Claude finds code by searching text and only learns about type errors when you run a build. With one, it gets two things.
Diagnostics after edits. Each time Claude edits or writes a file the server handles, it gets the errors and warnings the server reports. It sees a type error, a missing import or a syntax error it just introduced, without running a compiler.
Code navigation. Claude gets an LSP tool that looks up symbols through the server. The tools reference lists what it can do:
- Jump to a symbol's definition
- Find all references to a symbol
- Get type information at a position
- List symbols in a file
- Search for a symbol by name across the workspace
- Find implementations of an interface
- Trace call hierarchies
The tool is read-only. The tools reference lists it as needing no permission, and Read permission rules apply to it, so a Read(~/secrets/**) deny rule covers LSP calls too. Our Claude Code permissions guide explains those rules.
Why it matters: Anthropic's guidance page notes that in a typed language, a code intelligence plugin lets Claude jump straight to a definition instead of reading through many files to find it. Fewer files read means less context used. Our context management guide covers why that adds up over a session.
Which languages have code intelligence plugins
On November 22, 2026, the docs list these plugins:
| Language | Plugin | Language server binary |
|---|---|---|
| C/C++ | clangd-lsp |
clangd |
| C# | csharp-lsp |
csharp-ls |
| Go | gopls-lsp |
gopls |
| Java | jdtls-lsp |
jdtls |
| Kotlin | kotlin-lsp |
kotlin-lsp |
| Liquid | liquid-lsp |
shopify, from the Shopify CLI |
| Lua | lua-lsp |
lua-language-server |
| PHP | php-lsp |
intelephense |
| Python | pyright-lsp |
pyright-langserver |
| Ruby | ruby-lsp |
ruby-lsp |
| Rust | rust-analyzer-lsp |
rust-analyzer |
| Swift | swift-lsp |
sourcekit-lsp |
| TypeScript and JavaScript | typescript-lsp |
typescript-language-server |
Anthropic maintains all of them except liquid-lsp, which Shopify maintains and the official marketplace lists. The plugins live in the claude-plugins-official repo.
How to install a Claude Code LSP plugin
The plugin tells Claude Code which command starts the server and which file extensions it handles. It doesn't include the server itself, so there are three steps.
1. Install the language server binary
Each plugin's README in the repo gives the install command. For TypeScript, the docs give this one:
npm install -g typescript-language-server typescriptThen check the binary is on the PATH of the shell you start claude from:
which typescript-language-serverGet-Command typescript-language-server2. Install the plugin
Start claude in a terminal and run this at the prompt, swapping in your language's plugin from the table:
/plugin install typescript-lsp@claude-plugins-officialA message says whether the plugin is active now or needs /reload-plugins. In the VS Code extension or the desktop app, use their plugin install screens instead. Our Claude Code plugins guide covers install scopes, updates and removal.
3. Confirm the server starts
The server starts the first time Claude edits a file with one of the plugin's extensions. The docs suggest asking Claude to introduce a type error and then fix it. Under the edit, you should see:
Found N new diagnostic issues in M files (ctrl+o to expand)That line means it's working. Press Ctrl+O to read the issues themselves.
If no line appears, run /plugin and open the Errors tab. A row reading Executable not found in $PATH: "<binary>" names the binary you still need.
The LSP plugin recommendation dialog
If a language server binary is already on your PATH but its plugin isn't installed, Claude Code may offer it in a dialog titled LSP plugin recommendation after Claude edits a matching file. It appears at most once a session. The choices:
| Choice | Effect |
|---|---|
| Yes, install | Installs for your user account. Start a new session to load the server |
| Not now | Closes. A later session can offer it again |
| Never for this plugin | Stops offers for that plugin only |
| Disable all LSP recommendations | Stops offers for every language |
If you ignore the dialog, it closes after 30 seconds and counts as ignored. After five ignored dialogs, recommendations stop. To turn them back on, remove the lspRecommendationDisabled and lspRecommendationIgnoredCount keys from ~/.claude.json.
Fix a language server that won't start or uses too much memory
The troubleshooting page covers three problems:
| Symptom | Cause | Fix |
|---|---|---|
No diagnostics, or Executable not found in $PATH |
Binary missing from PATH |
Install it, confirm it's on the launching terminal's PATH, start a new session |
| High memory use | Servers such as rust-analyzer and pyright index the whole project |
Run /plugin disable <plugin> and let Claude use its built-in search |
| Unresolved-import errors in a monorepo | Server isn't configured for the workspace | Nothing to fix in Claude Code. The diagnostics don't stop Claude editing |
For more detail, claude --debug logs a failed start as LSP server <name> failed to start: <reason>.
Where code intelligence doesn't work
Code intelligence plugins work in terminal sessions. In cloud sessions, Claude Code doesn't start plugin language servers, so Claude gets no diagnostics or navigation there. That includes Claude Code on the web.
Language servers also run outside the Bash sandbox, which the sandboxing docs list alongside MCP servers and hooks. Our Claude Code sandboxing guide covers what that means.
Add a language without an official plugin
You can connect any language server by writing a small plugin with an .lsp.json file at its root. This example from the docs connects the Go server:
{
"gopls": {
"command": "gopls",
"args": ["serve"],
"extensionToLanguage": {
".go": "go"
}
}
}The rules from the plugin components page:
commandis the binary's name, started from the user'sPATH, with arguments inargs.extensionToLanguageneeds at least one extension, each starting with..- If any entry is invalid, the whole file is skipped and
Invalid LSP server config for ".lsp.json"appears in the Errors tab.claude plugin validatedoesn't check this file. - Each extension gets one server. If two enabled servers claim the same one, the first registered wins.
- The server must log to stderr, not stdout.
Load it for one session with --plugin-dir, or publish it to a marketplace. If you're new to building plugins, our guide to creating Claude Code skills is a gentler start.
Learn to build with Claude Code
The Stride AI Coding course teaches Claude Code and Codex for building client tools, written for non-programmers, with weekly live calls to review your builds. Many of the free guides cover Claude Code setups, and the Claude Code community is where members compare theirs.
FAQ
Does Claude Code support LSP?
Yes, through code intelligence plugins. Each plugin connects Claude Code to a language server for one language. Claude then gets diagnostics after its edits and an LSP tool for finding definitions, references and symbols.
How do I install an LSP plugin in Claude Code?
Install the language server binary first, such as typescript-language-server. Then run /plugin install typescript-lsp@claude-plugins-official inside Claude Code, swapping in the plugin for your language.
Which languages have Claude Code code intelligence?
On November 22, 2026: C/C++, C#, Go, Java, Kotlin, Liquid, Lua, PHP, Python, Ruby, Rust, Swift, and TypeScript and JavaScript. For other languages you can write your own plugin with an .lsp.json file.
How do I know the language server is working?
Ask Claude to introduce a type error and fix it. If you see Found N new diagnostic issues under the edit, the server started. If not, check the Errors tab in /plugin.
Why is my Claude Code language server using so much memory?
Servers like rust-analyzer and pyright index the whole project. If that's too heavy, run /plugin disable <plugin> and Claude falls back to its built-in search tools.
Does code intelligence work in Claude Code on the web?
No. Cloud sessions don't start plugin language servers, so the LSP tool stays inactive there. Code intelligence plugins work in terminal sessions.