lsp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| AnalyzeFileC | Run a file through analysis. You MUST provide a valid Path for the file. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as analyzing a file, leaving no room for confusion or misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'AnalyzeFile' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is too few for a server named 'lsp-mcp', which suggests a Language Server Protocol domain. A single analysis tool lacks the expected scope for language features like diagnostics, completions, or refactoring, making it feel incomplete and thin.
The tool set is severely incomplete for an LSP-related server. It only provides file analysis, missing essential operations such as getting diagnostics, providing code completions, or handling references, which are core to language server functionality.