Clone this repo:
  1. d908441 Bug 564839: Conflicting handlers with org.eclipse.lsp4e.operations.rename.LSPRenameHandler and Papyrus rename handler by Vincent Lorenzo · 11 days ago master
  2. 7ec1496 Bug 564437 - Hover loses the highlighting markdown when is focused by Victor Rubezhny · 3 weeks ago
  3. fc687d5 Bug 563966 - Integrate rendering for ```lang markdown syntax for hover help by Victor Rubezhny · 4 weeks ago
  4. a734832 Revert "Refactor command handlers to use setEnabled()" by Brian de Alwis · 5 weeks ago
  5. a2d44c0 NPE: workspace/symbol request may return in null by Brian de Alwis · 5 weeks ago

Eclipse LSP4E

Eclipse LSP4E makes Eclipse IDE able to consume the Language Server protocol and the Debug Adapter protocol.

Target audience are Eclipse plugin developers or Language developers willing to integrate a language which ships a Language Server or Debug Adapter into Eclipse IDE. End-users can also take advantage of this as LSP4E also defines a way to bind Eclipse IDE to existing language servers from UI.

Install it into Eclipse IDE, or add it to your target-platform using one of this p2 repository:


Language Server in Eclipse in the Eclipse IDE

Debug Adapter in action in the Eclipse IDE



LSP4E mostly ships extensions to the Generic Editor proposal for Eclipse Platform Text. But those classes can be reused in any editor or other extensions.

At the moment, it provides regular JFace/Platform Text classes for:

  • detection of language server for given file
  • synchronization of files with Language Server
  • diagnostics as problem markers
  • completion
  • hover
  • jump to declaration
  • formatting
  • rename refactoring
  • Find References
  • File symbols (as Outline or Quick Outline)
  • Workspace symbols
  • Language Server messages as notifications


Support for the Debug Adapter Protocol includes usual debug operations (breakpoints, step forward, step into, view variable value, evaluate expression, change variable value...) in the Platform Debug framework and its related UI components.


Examples of integration contain:

  • Eclipse Corrosion Rust support plugin for Eclipse IDE, edition is powered by LSP4E and RLS.
  • Eclipse aCute C# edition in Eclipse IDE using LSP4E and OmniSharp LSP implementation.
  • End-user using Language Server from Docker image, providing edition feature in the IDE without creating specific Eclipse IDE plugin:
  • Eclipse WildWebDeveloper HTML, CSS, JavaScript, TypeScript, Node.js, Angular, JSON, YAML (+Kubernetes) and XMLL edition, using LSP4E and various language servers from SourceGraph and VSCode.
  • language-servers-for-eclipse Binds various language servers to the Eclipse IDE.
  • Solargraph Binds a Ruby language server to the Eclipse IDE.

All those examples are already good for usage as they provide advanced edition features, and great for showcase of the LSP4E project.


Contributions are highly welcome. See how

Related projects

The Language Server protocol specification is an open-source project.

As the Language Server Protocol doesn't include support for syntax highlighting, most adopters of LSP4E usually pair it with the Eclipse TM4E project to provide Syntax Highlighting according to TextMate grammars.

Possible integration with Docker images as language-server are made possible thanks to Eclipse Docker Tools, which are part of the Eclipse LinuxTools project.


This has been initiated during the EclipseCon France 2016 Unconference. Some initial documentation is still available (although it may not be up to date).