Claude Code LSPs plugin
A Claude Code plugin marketplace that connects LSP language servers for TypeScript, Rust, Go, Python, 1C and other languages
- 522 ★ on the repository
- Last commit
Extended access
Why this level
- Each plugin starts a language-server process on your machine that reads the project files
- Server binaries come from npm, Homebrew, GitHub releases and other sources, and you have to vet each source yourself
- The authors recommend `npx tweakcc --apply`, which modifies the installed Claude Code
Install
- Works in
- Services
Manual install
/plugin marketplace add Piebald-AI/claude-code-lspsAfter adding the marketplace, open /plugins, pick the plugins for your languages, install them and restart Claude Code.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Each plugin starts a language-server process on your machine that reads the project files
- Server binaries come from npm, Homebrew, GitHub releases and other sources, and you have to vet each source yourself
- The authors recommend `npx tweakcc --apply`, which modifies the installed Claude Code
This is third-party code. Review the repository files before installing.
What it does
Claude Code LSPs is a plugin marketplace for Claude Code. Each plugin connects one language server to the built-in LSP tool, and for that language Claude gets IDE-style navigation. It jumps to the definition and implementation of a symbol, finds all references and builds a call hierarchy: who calls a function and what it calls itself. The plugins cover the mainstream languages: TypeScript and JavaScript, Python, Rust, Go, Java, C and C++, C#, PHP and Ruby. TypeScript has two servers to choose from, and so do Python and PHP. Kotlin, Scala, Perl, Julia, OCaml, Ada, Dart, Solidity and Elixir come next. For web and infrastructure there are Vue, Svelte, HTML and CSS, Bash, PowerShell, Terraform and OpenTofu, plus LaTeX. 1C:Enterprise gets a BSL server, and Markdown collections get mdbase. Each server's configuration sits in a .lsp.json file inside the plugin: the launch command, the mapping of file extensions to languages and the stdio transport.
Who it is for. For Claude Code developers who want IDE-level code navigation without reading whole files.
Good fit when
- In a large Go, Rust or Java repository you need an exact search for all references to a symbol, and a text grep returns extra matches
- Before a refactor you need to know which functions call a given one and what it calls itself
- A 1C project: the BSL plugin gives navigation across .bsl and .os files
- A monorepo has several languages, and each needs its own language server inside one Claude Code window
- You want to check a symbol's type and what the server knows about it, right from the agent chat
Not a fit when
- You work in another agent: the plugins are written for Claude Code, and Cursor or Codex need different solutions
- You need a language that is not on the list: the marketplace has no plugin for it
- You need symbol renaming and error diagnostics: they are not among the nine operations of the built-in LSP tool
- You only need text search over strings: grep is enough for that
Example request
Use LSP to find every place where parseConfig is called and show me the call hierarchyLimitations
A plugin only sets up the connection: you install the language server binary yourself and put it on PATH, otherwise the plugin does nothing. Some servers need a runtime: Java 17 or newer for Kotlin, Java 11 or 17 for Metals, Java 21 or newer for jdtls, Elixir 1.15 with Erlang/OTP 24 for ElixirLS, Node.js 20 for bash-language-server. Kotlin supports only JVM Gradle projects. For TypeScript install one of the two plugins, typescript-language-server or vtsls: they cover the same languages. The marketplace targets Claude Code 2.1.50 and newer. The author has not specified a license, so the rights to use and copy the code are undefined; check with the author.
How to disable. Remove the installed plugins in the `/plugins` menu and restart Claude Code; the marketplace is removed there too. If you patched Claude Code with tweakcc, see its documentation for undoing the patch.
FAQ
How do I connect the LSP plugins to Claude Code?
First add the marketplace with `/plugin marketplace add Piebald-AI/claude-code-lsps`. Then open `/plugins`, go to the Marketplaces tab, choose claude-code-lsps and Browse plugins, tick the plugins you want with the spacebar, press i to install and restart Claude Code.
How do I install the language server for Rust, Go or Python?
For Rust use `rustup component add rust-analyzer`, for Go `go install golang.org/x/tools/gopls@latest`, for Python `npm install -g pyright`. Commands for the other languages are in the collapsible blocks of the marketplace README.
What is tweakcc and do I need to run it?
It is a utility from the same authors. `npx tweakcc --apply` finds your Claude Code installation, npm or native, and patches it so that the built-in LSP tool becomes usable. It also changes the system prompt, themes and other parts of Claude Code. The LSP tool itself used to be switched on with the ENABLE_LSP_TOOL=1 environment variable. Since 2.0.74 it is in the official Claude Code changelog, so the patch is up to you.
Is there a plugin for 1C?
Yes, the bsl-lsp plugin connects bsl-language-server for .bsl and .os files. The executable for Windows, macOS or Linux is downloaded from the 1c-syntax project's GitHub releases and added to PATH.
Which operations does Claude get after installing?
Nine: go to definition and to implementation, hover, document symbols and workspace symbol search, find references, prepare call hierarchy, and incoming and outgoing calls.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsBSL 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 1C extension with a read-only HTTP service plus a Claude Code skill that pulls data from a live infobase into JSON using 1C query language
1C feature development plugin for Claude Code
1C:Enterprise AI Feature Development Plugin
A Claude Code plugin with a seven-phase workflow for extending 1C configurations: code research, architecture, implementation and review through separate agents
claude_rules_1c: Claude Code rules and agents for 1C
claude_rules_1c
A set of 12 subagents, profile-based rules and MCP configuration for 1C development in Claude Code, with a three-layer rule loading system
The 1c-dev Claude Code plugin: discussing a 1C task in dialogue, a technical spec, dependency-aware steps, and executing one verified step at a time
A Rust-based Language Server for BSL with code diagnostics, incremental analysis and a built-in MCP server for AI agents
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Claude Code LSPs (this entry) | no | 522 | ||
| cclsp | no | not required | 676 | an MCP server that connects LSP language servers to Claude Code: definitions, references, symbol renaming and diagnostics |
| MCP Language Server | no | not required | 1,611 | a bridge between an LSP language server and an agent: definitions, references, diagnostics, hover and symbol renaming |
README in short
The README opens with the authors' invitation to try the Piebald app, then covers the marketplace, the list of LSP operations, the Claude Code patch and plugin installation. Most of it is collapsible per-language blocks. It ends with a contributor section on .lsp.json files and checking them with `node scripts/validate-all.mjs`.