W3 MCP LSP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ROOT | No | Root directory of your project. Defaults to current directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lsp_goto_definitionA | Jump to symbol definition location. š“ CRITICAL: Line and character are STRICTLY 0-INDEXED (0, 1, 2...), NOT 1-indexed! ā WRONG (what editor displays): Editor shows: "Ln 5, Col 10" ā DON'T use: {"line": 5, "character": 10} ā CORRECT (0-indexed): ā DO use: {"line": 4, "character": 9} Formula: lsp_value = editor_value - 1 CHARACTER COUNTING (0-indexed from start of line): Line: "const greeting = "Hello";" Index: 0123456789... ā¢ 'c' in const ā character: 0 ā¢ 'o' in const ā character: 1 ā¢ 'g' in greeting ā character: 6 ā¢ 'H' in string ā character: 18 Args: params (LSPInput): Must provide line and character as 0-indexed values Returns: str: "file:line:column" or "Definition not found" Example: ā {"file_path": "src/app.ts", "line": 4, "character": 9} ā "/path/src/app.ts:15:5" |
| lsp_hoverA | Get type information and documentation for symbol at position. š“ CRITICAL: Line and character are STRICTLY 0-INDEXED (0, 1, 2...), NOT 1-indexed! ā WRONG (what editor displays): Editor shows: "Ln 5, Col 10" ā DON'T use: {"line": 5, "character": 10} ā CORRECT (0-indexed): ā DO use: {"line": 4, "character": 9} Formula: lsp_value = editor_value - 1 CHARACTER COUNTING (0-indexed from start of line): Line: "const greeting = "Hello";" Index: 0123456789... ā¢ 'c' in const ā character: 0 ā¢ 'o' in const ā character: 1 ā¢ 'g' in greeting ā character: 6 ā¢ 'H' in string ā character: 18 Args: params (LSPInput): Must provide line and character as 0-indexed values Returns: str: Type signature like "(parameter) name: string" or "No info available" Example: ā {"file_path": "src/app.ts", "line": 4, "character": 9} ā "(parameter) greeting: string" |
| lsp_find_referencesA | Find all usages/references of symbol at position. file:line:column ..." or "No references found" /path/src/app.ts:5:9 /path/src/utils.ts:10:2" |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct LSP operation: definition lookup, hover information, and reference search. There is no overlap in their purposes, making selection unambiguous.
All tools share the 'lsp_' prefix and follow an action-oriented naming pattern. However, 'lsp_hover' lacks the object component found in 'lsp_goto_definition' and 'lsp_find_references', creating a minor structural inconsistency.
The three tools represent a focused, minimal set of LSP navigation features. Each earns its place without unnecessary bloat, and the count falls within the well-scoped range.
The core navigation operations (definition, hover, references) are covered, providing a usable foundation. However, other common LSP features such as document symbols, implementation, or code completion are missing, which could require workarounds for certain tasks.