All servers / Developer / LSP Bridge MCP server
LSP Bridge MCP server
MCP server bridging Codex, Claude Code, and other MCP clients to Language Server Protocol servers
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 1.1.27. Package: lsp-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.0 seconds including download)
- Tools offered: 29
- Last published: 2026-10-22
- Weekly downloads (npm): 2,935
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
lsp_goto_definition3 of 3 parameters describedFind where a function, class, or variable is defined. More accurate than grep—handles aliases, re-exports, and overloads correctly. Returns file path, line, and column of the definition.
lsp_goto_type_definition3 of 3 parameters describedFind the type that defines a variable, parameter, or return value. Use when you have a variable and want to see its interface/class definition, not where the variable itself is declared.
lsp_find_references6 of 6 parameters describedFind every usage of a symbol across the codebase. Use before renaming or deleting to understand impact. More complete than grep—finds semantic matches, not just text.
lsp_find_implementations4 of 4 parameters describedFind all concrete implementations of an interface, abstract class, or abstract method. Use to understand how an abstraction is actually used in practice.
lsp_hover3 of 3 parameters describedGet the type signature and documentation for any symbol. Use to understand what a function accepts/returns or what type a variable has, without reading its implementation.
lsp_signature_help3 of 3 parameters describedGet parameter hints for a function call. Use when you need to know what arguments a function expects and their types, especially for overloaded functions.
lsp_document_symbols1 of 1 parameter describedGet a structured outline of a file: all functions, classes, interfaces, and variables with their types and relationships. Faster and more accurate than reading and parsing the file yourself.
lsp_workspace_symbols3 of 3 parameters describedFind any function, class, interface, or type by name—no file path needed. Start here when exploring a codebase or locating where something is defined. Supports fuzzy matching.
lsp_file_exports2 of 2 parameters describedGet the public API surface of a file: top-level functions, classes, interfaces, and variables with their type signatures. Use to understand what a module exposes without reading the entire file.
lsp_file_imports1 of 1 parameter describedGet all imports/dependencies of a file. Shows what modules this file depends on, including ES modules, CommonJS require(), and dynamic imports. Use to understand file dependencies.
lsp_related_files2 of 2 parameters describedFind files connected to a given file: what it imports and what imports it. Use to understand a file's dependencies and dependents before refactoring.
lsp_diagnostics2 of 2 parameters describedGet compiler errors, warnings, and hints for a file. Use after making changes to check for type errors, missing imports, or other issues. Diagnostics come from the language server, published or, for servers such as TypeScript 7, requested.
lsp_workspace_diagnostics3 of 3 parameters describedGet all errors and warnings across the entire project—no file path needed. Use during initial analysis to find problems or after changes to check overall project health. Only includes files opened in this session.
lsp_completions4 of 4 parameters describedGet intelligent code completion suggestions at a position. Returns available methods, properties, variables, and types that are valid in that context. More accurate than text-based completion.
lsp_rename5 of 5 parameters describedRename a symbol across the entire codebase safely. Handles all references, imports, and re-exports. Use dry_run=true (default) to preview changes before applying. More reliable than find-and-replace.
lsp_code_actions8 of 8 parameters describedGet quick fixes and refactoring suggestions at a position. Use to auto-fix errors, organize imports, extract functions, or apply other automated transformations. Set apply=true to execute an action.
lsp_call_hierarchy4 of 4 parameters describedTrace function calls: who calls this function (incoming) and what it calls (outgoing). Essential for understanding code flow and assessing impact before modifying a function.
lsp_type_hierarchy4 of 4 parameters describedExplore inheritance: find parent classes/interfaces (supertypes) and child classes/implementations (subtypes). Use to understand class relationships before modifying a base class or interface.
lsp_format_document4 of 4 parameters describedFormat a file according to project style settings (prettier, eslint, etc.). Use after making edits to ensure consistent formatting. Set apply=true to write changes.
lsp_smart_search5 of 5 parameters describedGet comprehensive information about a symbol in one call: type signature, definition location, all references, implementations, and call hierarchy. Use when you need full context about something instead of making multiple separate queries.
lsp_find_symbol4 of 4 parameters describedFind a symbol by name alone—no file path or position needed. Returns the definition location plus full context (type info, references, call hierarchy). Use when you know a symbol name but not where it is defined.
lsp_server_status1 of 1 parameter describedCheck which language servers are running and their state. Use to verify LSP is available before analysis or to debug connection issues.
lsp_start_server2 of 2 parameters describedStart a language server manually for a workspace. Usually not needed—servers auto-start when you use other LSP tools. Use only when you need explicit control over server lifecycle.
lsp_stop_server2 of 2 parameters describedStop a running language server to free resources. Servers auto-stop after idle timeout, so manual stop is rarely needed.
lsp_document_highlights3 of 3 parameters describedFind all occurrences of the symbol at a position within the same file, classified as text/read/write. Faster and more local than lsp_find_references when you only care about one file (e.g., quick local rename preview or read-vs-write analysis).
lsp_inlay_hints6 of 6 parameters describedGet inferred type annotations and parameter-name hints for a range of code. Reveals variable types, return types, and named-parameter mappings without one hover per identifier. Ideal for understanding heavily inferred code (TypeScript const/let, Rust let, etc.) at scale.
lsp_selection_range3 of 3 parameters describedGet the chain of semantic ranges enclosing a position — the expression, then its statement, then its block, up to the file. Use to pick the right range for lsp_code_actions (e.g., "extract this expression vs the whole statement").
lsp_folding_ranges2 of 2 parameters describedGet the foldable regions of a file (functions, classes, blocks, imports, comments). Use as a quick structural overview before reading specific sections.
lsp_index_files1 of 1 parameter describedOpen a batch of files so language servers begin publishing diagnostics for them. Required warm-up before lsp_workspace_diagnostics (which only sees opened files) and before lsp_related_files imported_by. Use a small targeted set rather than the whole workspace.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.