lodesman
Related Servers
Alternatives to lodesman
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI coding agents to query a semantic cross-repository code graph for symbols, references, callers, dependencies, and change impact across registered repositories.1221Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.-
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to retrieve the code a change touches and the decisions behind it, with separate code and decision search, symbol explanations, and import/reference path finding.Apache 2.0
- AlicenseNot gradedqualityAmaintenanceSupercharges AI coding agents with a pre-indexed semantic code graph, enabling instant symbol relationships, impact analysis, and context retrieval across 20+ languages.121,709 npm73,826MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve precise symbol definitions and usages from codebases, eliminating the need to fetch entire files.5 npm2ISC
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.18 PyPI3MIT
TDQS
Scored across 11 tools
Most tools have distinct purposes, but a few overlap conceptually (e.g., find_symbol vs find_definition, explain_symbol vs get_symbol_body). The descriptions are detailed enough to reduce confusion, but an agent might still hesitate when selecting between similar navigation actions.
The majority follow a consistent verb_noun pattern (find_symbol, find_references, rename_symbol, etc.), but a few deviate: project_info, check, and blast_radius are not verb-first. The naming is still readable and predictable overall, just with minor inconsistencies.
With 11 tools, the server covers a comprehensive set of code navigation and analysis operations without being bloated. Each tool addresses a specific need, and the count fits well within the ideal range for a focused domain.
The tool set covers the full lifecycle of symbol exploration: finding, defining, referencing, implementing, renaming, inspecting, and checking diagnostics. It includes advanced features like blast radius and document outlines, leaving no obvious dead ends for common code navigation workflows.