Back to Blog
Claude Code LSP Plugins: TypeScript Setup Guide (2026)
Share:
LSP plugins are how Claude Code stops guessing about your code and starts knowing it. If you have looked for the LSP plugins Claude Code supports, there are eleven official ones, one per language. A Language Server Protocol plugin gives Claude real-time go-to-definition, find-references, and live type errors for a specific language — the same intelligence your editor uses — so it makes fewer wrong-symbol and type mistakes. Anthropic ships eleven official LSP plugins, one per language. This guide covers what they do, the full list, how to set up typescript-lsp step by step, and how to fix the usual snags.
Last updated: July 2026.
Key Takeaways
If you remember nothing else:
- LSP plugins give Claude real-time type intelligence (go-to-def, find-refs, live errors) per language
- Anthropic ships 11 official language servers in
claude-plugins-official- Install the plugin and its language-server binary — the plugin wraps the server, it doesn't bundle it
- TypeScript:
/plugin install typescript-lsp@claude-plugins-official+ thetypescript-language-serverbinary on yourPATH- A "not working" LSP plugin is almost always a missing binary
Table of Contents
- What LSP Plugins Do
- The 11 Official Language Servers
- Setup: Plugin + Binary
- Verifying It Works
- Troubleshooting
- Conclusion
What LSP Plugins Do
Without a language server, Claude reasons about code from raw text — which works, but leaves room for wrong-symbol edits and type errors. An LSP plugin connects Claude to the same Language Server Protocol tooling your editor uses, giving it real-time answers to "where is this defined," "what references this," and "does this type-check." The payoff is more accurate edits, especially in large or strongly-typed codebases. LSP plugins are part of Anthropic's official Claude Code plugins set.
The effect is most noticeable on exactly the tasks where AI usually stumbles: refactoring across many files, renaming a symbol used in a dozen places, or working in a large codebase where the right function lives three directories away. Instead of inferring a signature from nearby text and occasionally guessing wrong, Claude asks the language server and gets the authoritative answer. In a polyglot repository you can install several LSP plugins at once — one per language — so Claude has the same intelligence everywhere it works.
The 11 Official Language Servers
All eleven ship in Anthropic's official marketplace, anthropics/claude-plugins-official. Each installs as <name>@claude-plugins-official and requires the listed binary:
| Language | Plugin | Requires binary |
|---|---|---|
| TypeScript | typescript-lsp |
typescript-language-server |
| Python | pyright-lsp |
pyright-langserver |
| Go | gopls-lsp |
gopls |
| Rust | rust-analyzer-lsp |
rust-analyzer |
| C / C++ | clangd-lsp |
clangd |
| C# | csharp-lsp |
csharp-ls |
| Java | jdtls-lsp |
jdtls |
| Kotlin | kotlin-lsp |
kotlin-language-server |
| Lua | lua-lsp |
lua-language-server |
| PHP | php-lsp |
intelephense |
| Swift | swift-lsp |
sourcekit-lsp |
See the full first-party catalog in our official Claude Code plugins list.
Setup: Plugin + Binary
Setting up an LSP plugin is always two steps — install the plugin, then install the server binary it wraps. Using TypeScript as the worked example:
# 1. Install the plugin (official marketplace is auto-registered)
/plugin install typescript-lsp@claude-plugins-official
# 2. Install the language-server binary and put it on your PATH
npm install -g typescript typescript-language-server
Then run /reload-plugins. The same pattern applies to every language — swap in the plugin and binary from the table above (for Python, pyright-lsp + pyright-langserver; for Go, gopls-lsp + gopls, and so on). For the general install flow, see how to install Claude Code plugins.
Verifying It Works
Confirm the binary is reachable (typescript-language-server --version should print a version), then check the plugin is enabled in the /plugin manager. With both in place, Claude gains real-time type information automatically — you will notice it referencing exact symbols and catching type errors as it edits.
Troubleshooting
- The plugin seems installed but gives no intelligence. The language-server binary is almost certainly missing or not on your
PATH. Install it and confirm with<binary> --version, then/reload-plugins. - Wrong language. Make sure you installed the plugin matching your stack (e.g.
pyright-lsp, nottypescript-lsp). - Still nothing after installing the binary. Reload the session and confirm the plugin is enabled in
/plugin. For a shortlist of high-leverage plugins to pair with your LSP, see the tested best Claude Code plugins.
Conclusion
LSP plugins are among the highest-leverage official plugins for anyone writing typed code: install the one for your language plus its server binary, and Claude Code trades guesswork for real intelligence. Start with your primary stack, verify the binary is on your PATH, and layer in others as needed. The official Claude Code plugins list and the best Claude Code plugins roundup cover what to add next.
Related Resources
Frequently Asked Questions
-
LSP (Language Server Protocol) plugins give Claude Code real-time code intelligence for a specific language — go-to-definition, find-references, and live type errors — instead of guessing from raw text. Anthropic ships eleven official LSP plugins, one per language, in the claude-plugins-official marketplace. Installing the one for your stack measurably reduces wrong-symbol edits and type mistakes.
-
Two steps. Install the plugin with /plugin install typescript-lsp@claude-plugins-official, then make sure the language-server binary it wraps — typescript-language-server — is installed and on your PATH. Once both are in place, Claude gets real-time TypeScript type information automatically. Run /reload-plugins to apply the plugin in an existing session.
-
As of July 2026, Anthropic ships eleven: TypeScript, Python (pyright), Go, Rust, C/C++ (clangd), C#, Java, Kotlin, Lua, PHP, and Swift. Each is installed as
-lsp@claude-plugins-official and requires its underlying language-server binary. Languages without an official plugin can still be used, just without the real-time intelligence an LSP provides. -
Yes. The plugin wraps a language server but does not bundle it, so you must install the server binary yourself — for example typescript-language-server for TypeScript, pyright-langserver for Python, or gopls for Go — and ensure it is on your PATH. If the binary is missing, the plugin cannot provide intelligence; installing it is the usual fix for an LSP plugin that seems inactive.
-
The most common cause is a missing or unreachable language-server binary. Confirm the binary is installed and on your PATH, then run /reload-plugins. Also check the plugin is enabled in the /plugin manager and that you installed the correct one for your language. Once the binary resolves, real-time intelligence should activate automatically.
Join 50k+ subscribers
Web dev, SaaS, growth & marketing. Weekly.
Keep Learning
More articles you might find interesting.
