Claude Code LSPs plugin
A marketplace of LSP plugins for Claude Code: go to definition, find references and diagnostics for over 20 languages and setups.
- 193 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Plugin hooks try to install LSP servers through package managers and run them on your machine.
Install
- Works in
Manual install
/plugin marketplace add boostvolt/claude-code-lspsThen `/plugin install gopls@claude-code-lsps` or another plugin from the list.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Plugin hooks try to install LSP servers through package managers and run them on your machine.
This is third-party code. Review the repository files before installing.
What it does
Claude Code starts LSP servers from installed plugins itself and exposes them to the agent in two ways. A builtin LSP tool gets nine operations: `goToDefinition`, `findReferences`, `hover`, `documentSymbol`, `workspaceSymbol`, `goToImplementation`, `prepareCallHierarchy`, `incomingCalls` and `outgoingCalls`. Error and warning diagnostics arrive automatically, like the VS Code integration but independent of it. The marketplace consists of per-language plugins: Bash, C and C++, Clojure, Dart, Elixir, Gleam, Go, PHP (Intelephense and a WordPress variant), Java (`jdtls`), Kotlin, Lua, Nix, OCaml, C#, Python (`pyright`), Rust, Ruby, Swift, Terraform, TypeScript and JavaScript (`vtsls`), YAML and Zig. Each plugin installs its own server on first use.
Who it is for. Developers who work in Claude Code on less common languages and want symbol navigation and diagnostics from the agent instead of text search.
Good fit when
- In a Go project the agent finds all references to a function and its implementations by symbol.
- For a Rust project `rust-analyzer` is installed so the agent sees compiler errors right after an edit.
- A Terraform or YAML codebase gets schema checks and hints with no editor running.
- The call hierarchy must be walked: who calls a function and what it calls.
Not a fit when
- The project language is not in the plugin list.
- Claude Code is between 2.0.69 and 2.0.x, where the integration is broken by a race condition.
- You want to chat with code through the shared VS Code integration rather than a separate server.
Example request
Find all references to the ParseConfig function and show who calls it through LSP, then list the diagnostic errors in this package.Limitations
Claude Code 2.1.0 or newer is needed: from 2.0.69 to 2.0.x the LSP integration was broken by a race condition. A plugin tries to install its own server on first use, but on failure the server is installed by hand through Homebrew, npm, rustup and other managers as the README describes per language. Each plugin installs separately, so pick the one for your project language. Servers run locally and read project files.
How to disable. Disable a plugin with `/plugin uninstall <name>@claude-code-lsps`. Installed LSP servers are removed with the usual package manager (Homebrew, npm, rustup).
FAQ
How do I add the marketplace?
In Claude Code run `/plugin marketplace add boostvolt/claude-code-lsps`, then `/plugin install gopls@claude-code-lsps` or another plugin. Pick plugins interactively with `/plugin`.
Which languages are supported?
Bash, C and C++, Clojure, Dart, Elixir, Gleam, Go, PHP, Java, Kotlin, Lua, Nix, OCaml, C#, Python, Rust, Ruby, Swift, Terraform, TypeScript and JavaScript, YAML, Zig and Astro.
What if the server does not install itself?
Install it by hand following the README instructions for the language, for example `brew install bash-language-server` or `npm install -g bash-language-server`.
Which LSP operations does the agent get?
Nine: definition, references, hover, document and workspace symbols, implementations, call hierarchy, and incoming and outgoing calls.
Which Claude Code version is needed?
2.1.0 or newer. From 2.0.69 to 2.0.x the LSP integration was broken by a race condition, fixed in 2.1.0.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin marketplace that connects LSP language servers for TypeScript, Rust, Go, Python, 1C and other languages
cclsp connects LSP language servers to Claude Code over MCP: go to definition, find references, rename symbols and diagnostics with no editor needed
BSL Language Server for Claude Code
BSL Language Server Claude Code Plugin
A Claude Code plugin that attaches BSL Language Server to 1C and OneScript files: diagnostics, go to definition, references, formatting
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.
Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Claude Code LSPs (this card) | no | 193 | ||
| Claude Code LSPs | no | 520 | an LSP plugin set by another author; here are per-language plugins including Astro, Gleam, Nix and WordPress | |
| cclsp | no | not required | 675 | an LSP bridge over MCP; here Claude Code plugins with ready server setup and a check hook |
README in short
The collection consists of separate plugins with `.lsp.json` files and a server check hook. Detailed manual install instructions exist for every language, and an example is shown in the integration screenshot.