# Language Server Protocol (LSP)

**Source:** https://promtable.com/glossary/lsp

> LSP is the open standard for editor ↔ language tooling communication — autocomplete, jump-to-definition, find references, diagnostics — used by VS Code, Zed, Neovim, JetBrains, and most modern IDEs in 2026.

---
LSP is the open standard for editor ↔ language tooling communication — autocomplete, jump-to-definition, find references, diagnostics — used by VS Code, Zed, Neovim, JetBrains, and most modern IDEs in 2026.

Before LSP every editor implemented language features (completion, jump-to-def) per-language: huge duplication, language vendors had to ship plugins for each editor. LSP defined a JSON-RPC protocol the editor + language server speak — TypeScript Language Server, rust-analyzer, gopls, pyright. The editor handles UI, the server handles the language. By 2026 LSP is universal; AI IDEs build on top of LSP (using its symbol index for codebase navigation, diagnostics for error context). MCP ([[model-context-protocol]]) borrowed LSP's pattern — open protocol, server / client split. Understanding LSP matters when building AI tooling: the symbol graph LSP exposes is a high-signal context source.

## When to use

- Building language tooling.
- Understanding AI IDE internals.

## Common mistakes

- Building AI features without using LSP symbol info — much richer signal available for free.

## Related terms

- [ai-ide](https://promtable.com/glossary/ai-ide)
- [ide-agent](https://promtable.com/glossary/ide-agent)
- [model-context-protocol](https://promtable.com/glossary/model-context-protocol)

## Sources

- [LSP spec](https://microsoft.github.io/language-server-protocol/)

*Last updated: 2026-06-01*
---

Original page: https://promtable.com/glossary/lsp
Maintained by Promtable (https://promtable.com). Content: CC BY 4.0. Cite as "Promtable — https://promtable.com/glossary/lsp".
Contact: info@vibecodingturkey.com.