squiggles
Related Servers
Alternatives to squiggles
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes LSP-backed code navigation and editing tools to LLM agents using a single global config file to route file extensions to language servers.MIT
- FlicenseNot gradedqualityDmaintenanceGive your AI coding agents superpowers — a local MCP server for fast, token-efficient code navigation, search & analysis.-
- AlicenseNot gradedqualityAmaintenanceMCP server that gives AI coding agents codebase navigation intelligence, enabling symbol lookup, reference finding, type inspection, and diagnostics through tools like locate, refs, hover, diagnostics, status, and rename.569 npmMIT
- FlicenseNot gradedqualityCmaintenanceA single MCP server that bridges to any LSP, enabling code intelligence features like hover, go-to-definition, references, and diagnostics for multiple languages via configurable language servers.1-
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.23 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents structured code understanding and precise code intelligence via local indexing of AST, call graphs, and semantic search.47 npm4Apache 2.0
TDQS
Scored across 21 tools
Each tool maps to a distinct LSP action (goto, references, rename, formatting, diagnostics, etc.). The several goto variants are clearly differentiated by description, and rename_prepare/rename, call_hierarchy_incoming/outgoing, and type_hierarchy are unambiguous.
The tools follow a consistent verb_noun snake_case pattern (goto_definition, find_references, rename_prepare, format). Minor deviations exist: 'goto' vs 'go_to' in ts_go_to_source_definition, and the ts_ prefix on TypeScript-specific tools, but these do not break the overall predictability.
At 21 tools, this is on the heavier side, but the server's purpose is to expose a comprehensive LSP surface, so the count is reasonable. Each tool covers a distinct LSP feature and none feel redundant, though the set could be trimmed by merging some goto variants.
The set covers core LSP workflows: navigation, references, rename, formatting, code actions, symbols, diagnostics, and call/type hierarchies. Minor gaps exist (e.g., no completion, document_highlight, or execute_command), but agents can accomplish most tasks without them.