{"report":{"v":1,"package":"lsp-mcp-server","version":"1.1.27","ranAt":"2026-11-16T11:31:22.531Z","install":{"ok":true,"integrity":"sha512-GW/2/DJ3RfGG9FzwRJzXF5RQR2tWMXdEOr3VuBJZKm2x+q3TXTyhOrpjsiN+xbFukwRGrGlaL4W6q6Wa1+EQCA==","deps":98,"scripts":[],"bins":["lsp-mcp-server"],"license":"MIT","engines":"node >=18.0.0","repository":"git+https://github.com/ProfessioneIT/lsp-mcp-server.git","bin":"lsp-mcp-server"},"start":{"ok":true,"ms":156,"serverName":"lsp-mcp-server","serverVersion":"1.1.27","protocol":"2025-06-18","stderr":"[2026-11-16T11:31:26.131Z] [INFO] Starting LSP-MCP server...\n[2026-11-16T11:31:26.136Z] [INFO] LSP-MCP server running on stdio\n"},"tools":[{"name":"lsp_goto_definition","description":"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 definition.","params":["file_path","line","column"]},{"name":"lsp_goto_type_definition","description":"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 declared.","params":["file_path","line","column"]},{"name":"lsp_find_references","description":"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.","params":["file_path","line","column","include_declaration","limit","offset"]},{"name":"lsp_find_implementations","description":"Find all concrete implementations of an interface, abstract class, or abstract method. Use to understand how an abstraction is actually used in practice.","params":["file_path","line","column","limit"]},{"name":"lsp_hover","description":"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.","params":["file_path","line","column"]},{"name":"lsp_signature_help","description":"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.","params":["file_path","line","column"]},{"name":"lsp_document_symbols","description":"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 yourself.","params":["file_path"]},{"name":"lsp_workspace_symbols","description":"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.","params":["query","kinds","limit"]},{"name":"lsp_file_exports","description":"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 the entire file.","params":["file_path","include_signatures"]},{"name":"lsp_file_imports","description":"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.","params":["file_path"]},{"name":"lsp_related_files","description":"Find files connected to a given file: what it imports and what imports it. Use to understand a file's dependencies and dependents before refactoring.","params":["file_path","relationship"]},{"name":"lsp_diagnostics","description":"Get 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.","params":["file_path","severity_filter"]},{"name":"lsp_workspace_diagnostics","description":"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 includes files opened in this session.","params":["severity_filter","limit","group_by"]},{"name":"lsp_completions","description":"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 completion.","params":["file_path","line","column","limit"]},{"name":"lsp_rename","description":"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 than find-and-replace.","params":["file_path","line","column","new_name","dry_run"]},{"name":"lsp_code_actions","description":"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 execute an action.","params":["file_path","start_line","start_column","end_line","end_column","kinds","apply","action_index"]},{"name":"lsp_call_hierarchy","description":"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.","params":["file_path","line","column","direction"]},{"name":"lsp_type_hierarchy","description":"Explore inheritance: find parent classes/interfaces (supertypes) and child classes/implementations (subtypes). Use to understand class relationships before modifying a base class or interface.","params":["file_path","line","column","direction"]},{"name":"lsp_format_document","description":"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.","params":["file_path","tab_size","insert_spaces","apply"]},{"name":"lsp_smart_search","description":"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 about something instead of making multiple separate queries.","params":["file_path","line","column","include","references_limit"]},{"name":"lsp_find_symbol","description":"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 name but not where it is defined.","params":["name","kind","include","references_limit"]},{"name":"lsp_server_status","description":"Check which language servers are running and their state. Use to verify LSP is available before analysis or to debug connection issues.","params":["server_id"]},{"name":"lsp_start_server","description":"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.","params":["server_id","workspace_root"]},{"name":"lsp_stop_server","description":"Stop a running language server to free resources. Servers auto-stop after idle timeout, so manual stop is rarely needed.","params":["server_id","workspace_root"]},{"name":"lsp_document_highlights","description":"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 file (e.g., quick local rename preview or read-vs-write analysis).","params":["file_path","line","column"]},{"name":"lsp_inlay_hints","description":"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. Ideal for understanding heavily inferred code (TypeScript const/let, Rust let, etc.) at scale.","params":["file_path","start_line","start_column","end_line","end_column","limit"]},{"name":"lsp_selection_range","description":"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., \"extract this expression vs the whole statement\").","params":["file_path","line","column"]},{"name":"lsp_folding_ranges","description":"Get the foldable regions of a file (functions, classes, blocks, imports, comments). Use as a quick structural overview before reading specific sections.","params":["file_path","kind_filter"]},{"name":"lsp_index_files","description":"Open 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.","params":["files"]}],"toolsHash":"6791b431baf9e21e3afc7aca0e70cdcdb104b2b69cbf333be28293e486975b90","wrote":[],"callsAt":"2026-11-16T11:31:28.148Z","calls":[{"tool":"lsp_server_status","ok":true,"ms":3,"bytes":19}],"host":{"commit":"eaaffffaf52255d1b77dc4aacffdfaf353f0c12c","run":"https://github.com/itsHaddad/bragproof/actions/runs/43857070216"},"network":{"names":["registry.npmjs.org"],"conns":[],"callNames":[],"callConns":[]}},"summary":{"outcome":"started","needs":[],"contacts":[],"flags":[],"tools":29,"wrote":0,"callsTried":1,"callsAnswered":1,"callContacts":[]},"history":[{"package":"lsp-mcp-server","version":"1.1.27","ranAt":"2026-11-16T11:31:22.531Z","outcome":"started","tools":29,"contacts":0,"flags":0,"serious":0,"toolsHash":"6791b431baf9e21e3afc7aca0e70cdcdb104b2b69cbf333be28293e486975b90"}],"page":"https://bragproof.smaverk.com/r/lsp-mcp-server"}