W3 MCP LSP Server
Related Servers
Alternatives to W3 MCP LSP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceExposes TypeScript language service tools (completions, go-to-definition, type info, diagnostics) via MCP for use by AI or IDE clients.71-
- FlicenseNot gradedqualityBmaintenanceExposes LSP features (definition, hover, references, etc.) over MCP, spawning an isolated language server process per project.-
- AlicenseNot gradedqualityDmaintenanceExposes Language Server Protocol (LSP) features as MCP tools, enabling IDE-grade semantic navigation including go-to-definition, find references, hover info, and symbols across multiple programming languages (Python, Rust, C/C++, TypeScript/JavaScript, React, HTML, CSS).3MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.4020 npm3MIT
- AlicenseBqualityDmaintenanceTypeScript-based MCP server designed to enhance code editing experiences by providing features such as hover information, code completion, and diagnostics.355 npm26MIT
- AlicenseNot gradedqualityBmaintenanceSelf-contained MCP server providing type-aware code intelligence for TypeScript, JavaScript, and Vue files, exposing tools like hover, definition, references, and diagnostics to Claude Code without requiring global language server installations.MIT
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.