Caplets Catalog
official
spiritledsoftware/caplets

LSP

Language Server Protocol tools for project-aware code intelligence through language-server-mcp.

Install
caplets install spiritledsoftware/caplets lsp

Inspect before installing

  • Local controlThis Caplet can operate against local project or machine state.
  • Project Binding requiredThis Caplet needs a Project Binding before it can run in the intended environment.
CAPLET.md

Frontmatter

FieldValue
nameLSP
descriptionLanguage Server Protocol tools for project-aware code intelligence through language-server-mcp.
useWhenUse for language-server-specific, project-aware code intelligence such as definitions, references, diagnostics, types, symbols, code actions, formatting, and rename edits.
avoidWhenAvoid for syntax-pattern or text searches that do not require language-server semantics; use ast-grep or text search instead.
tagsmcp, code, lsp, language-server, diagnostics
projectBinding.requiredtrue
mcpServer.commandnpx
mcpServer.args-y, language-server-mcp@latest

LSP

Inspection and Edits

Diagnostics, hover or type information, and definition lookup provide a focused starting point for a specific file and symbol. References and symbols show the blast radius of a refactor. Code actions, formatting, and rename operations can be reviewed as proposed edits before application, with source and tests used to validate behavior-sensitive conclusions.

Project Context

Project Binding is required. LSP operations depend on a trustworthy bound project root for workspace-relative files, language-server startup, diagnostics, and edit containment.

File-targeted paths must resolve inside the bound workspace. A serverId disambiguates files handled by multiple language servers and is required for some applied edits.

Safe Operation and Lifecycle

language-server-mcp uses conservative defaults for file modification and process execution:

  • Edit-producing tools return edits without writing unless apply: true is supplied.
  • When multiple matching LSP servers could produce edits, apply: true also requires serverId.
  • Applied edits remain inside the workspace root unless the downstream server enables security.allowExternalFiles: true.
  • workspace/executeCommand is enabled by default. Operators can disable it globally or restrict it with per-server command allowlists.
  • LSP servers start lazily on first use and stop after an idle timeout by default.