mcpserver.lol
registry/professioneit-lsp-mcp-server
Connection check local install

professioneit-lsp-mcp-server

An MCP (Model Context Protocol) server that bridges Claude Code to Language Server Protocol (LSP) servers, enabling semantic code intelligence capabilities.

Tools 29
GitHub stars 21
Installs / wk 2.8k
Licence MIT
Transport stdio
Last checked never

Tools & capabilities

29 tools

Read from the published package source — this server runs locally, so there is no endpoint to query. Names are taken from the code, not observed at runtime, and descriptions are often absent.

lsp_call_hierarchy from source
Trace 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_code_actions from source
Get 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…
lsp_completions from source
Get 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…
lsp_diagnostics from source
Get compiler errors, warnings, and hints for a file. Use after making changes to check for type errors, missing imports, or other issues. Results are cached from language server no…
lsp_document_highlights from source
Find 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 fi…
lsp_document_symbols from source
Get 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…
lsp_file_exports from source
Get 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 th…
lsp_file_imports from source
Get 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_find_implementations from source
Find all concrete implementations of an interface, abstract class, or abstract method. Use to understand how an abstraction is actually used in practice.
lsp_find_references from source
Find 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_symbol from source
Find 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 n…
lsp_folding_ranges from source
Get the foldable regions of a file (functions, classes, blocks, imports, comments). Use as a quick structural overview before reading specific sections.
lsp_format_document from source
Format 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_goto_definition from source
Find 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 defin…
lsp_goto_type_definition from source
Find 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 dec…
lsp_hover from source
Get 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_index_files from source
lsp_inlay_hints from source
Get 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. Ide…
lsp_related_files from source
Find files connected to a given file: what it imports and what imports it. Use to understand a file\
lsp_rename from source
Rename 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 tha…
lsp_selection_range from source
Get 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.,
lsp_server_status from source
Check which language servers are running and their state. Use to verify LSP is available before analysis or to debug connection issues.
lsp_signature_help from source
Get 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_smart_search from source
Get comprehensive information about a symbol in one call: type signature, definition location, all references, implementations, and call hierarchy. Use when you need full context a…
lsp_start_server from source
Start 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_server from source
Stop a running language server to free resources. Servers auto-stop after idle timeout, so manual stop is rarely needed.
lsp_type_hierarchy from source
Explore inheritance: find parent classes/interfaces (supertypes) and child classes/implementations (subtypes). Use to understand class relationships before modifying a base class o…
lsp_workspace_diagnostics from source
Get 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 inclu…
lsp_workspace_symbols from source
Find 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.