agy-lsp
Related Servers
Alternatives to agy-lsp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query locally installed language servers over stdio MCP for read-only code intelligence, including definitions, references, implementations, hover types, symbols, and diagnostics.37 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query language intelligence over MCP, including definitions, references, symbols, and code relationship graphs across many languages, all in one native process with no external language servers.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI coding agents to retrieve real-time language-server diagnostics, type and symbol information, definitions, references, workspace-wide renames, and file operations from an open editor. This provides accurate code navigation and editing context without waiting for slow tsc or eslint checks.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI coding agents to access real-time editor-native LSP diagnostics, type information, code navigation, and workspace-wide symbol renaming without waiting for slow tsc/eslint checks.MIT
- AlicenseNot gradedqualityBmaintenanceProvides IDE-like coding capabilities for AI agents via MCP, enabling semantic code retrieval, symbol-level editing, refactoring, and navigation across many programming languages.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceExposes VSCode's Language Server Protocol features through MCP, enabling AI assistants to perform language-aware operations like symbol navigation, reference tracking, safe renaming, type information retrieval, and hover documentation across codebases.-
TDQS
Scored across 11 tools
Most tools target clearly distinct LSP operations: diagnostics, status, definitions, references, rename, symbols, hover, and hierarchies. The only mild overlap is between prepare_call_hierarchy and call_hierarchy, where the preparatory step could be confused with the actual hierarchy query.
Names are consistently snake_case and mostly follow verb_noun or clear noun_phrase patterns, e.g. go_to_definition, find_references, rename_symbol, get_type_hierarchy. Minor deviations include single-word hover and noun-style lsp_status/call_hierarchy, but the set remains predictable.
Eleven tools is well-scoped for an LSP server, covering navigation, diagnostics, refactoring, symbols, and hierarchy queries without obvious bloat. Each tool appears to earn its place in the surface.
The server covers core LSP workflows: diagnostics, definition lookup, references, rename, document/workspace symbols, hover, and call/type hierarchies. Some secondary LSP capabilities such as code actions, formatting, or signature help are absent, but the main agent-facing operations are present.