jdtls-lsp connects the Java (Eclipse JDT.LS) language server to Claude Code, giving it code intelligence and diagnostics for java files. The plugin only wires up the server; the server binary must be installed separately.
What it does
Where jdtls LSP runs and what it adds, from its documentation
Registers the jdtls language server (command: jdtls (startupTimeout 120000 ms)) via the marketplace lspServers entry
Maps file extensions to the language: .java
Gives Claude Code code intelligence and diagnostics for Java (Eclipse JDT.LS) projects
When to use it
Good fit
Working in a Java (Eclipse JDT.LS) codebase where Claude Code should use real language-server analysis
Wanting diagnostics and navigation from jdtls without leaving Claude Code
Not for
Projects in other languages (it only maps the extensions listed)
Setups where you cannot install the jdtls binary on PATH
How to install jdtls LSP
You need: Claude Code; jdtls binary on PATH; Java 17 or later (JDK, not just JRE)
Install the language server binary first (the plugin does not bundle it):
macOS: brew install jdtls
Arch Linux (AUR): yay -S jdtls; other distros need manual installation
Manual: download from Eclipse JDT.LS releases, extract (e.g. ~/.local/share/jdtls), create a wrapper script named jdtls in your PATH
Install the plugin: /plugin install jdtls-lsp@claude-plugins-official
Permissions and security
What it can access
Launches the jdtls process locally and reads the project files it analyzes
Security notes from the maintainers
Marketplace README: make sure you trust a plugin before installing, updating, or using it
Review the source before granting an agent access to credentials or production systems. We document what the maintainers state; we do not audit code.
Limitations
Requires the language server to be installed separately; the plugin does not install it
