runecho
Related Servers
Alternatives to runecho
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes a codebase's symbol graph and symbol-aware editing tools to AI agents, enabling targeted symbol lookup, impact analysis, and atomic multi-file edits with reduced context tokens.7 npmMIT
- FlicenseAqualityAmaintenanceDeterministic code intelligence engine — indexes 27 languages into a queryable symbol graph for real-time blast-radius analysis, no embeddings or LLM calls.526-
- 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.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore a repository by querying a pre-built structural knowledge graph of symbols and their relationships — definitions, callers, callees, blast radius, and file-level impact — instead of grepping and reading files. This cuts the tokens spent on code exploration by roughly 96–99% while running entirely on local SQLite with tree-sitter parsing.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.46 PyPI3MIT
- AlicenseNot gradedqualityAmaintenanceIndexes a codebase into a symbol-level graph and exposes tools for finding symbols, querying relationships, and assessing impact, letting AI coding agents answer structural questions in a single call within a token budget.39 npm4Apache 2.0
TDQS
Scored across 6 tools
Most tools are cleanly separated and the descriptions explicitly cross-reference each other (status vs health, diff vs structure). The only real overlap is between structure and locate, both of which surface files/symbols, but the descriptions differentiate full-structure listing from targeted symbol lookup well enough.
All six names are single lowercase words with a uniform style, which is easy to predict. The only slight inconsistency is that some are nouns (structure, hash, status, health) and others are verbs (diff, locate), so the semantic pattern shifts even though the form is consistent.
Six focused tools is well-scoped for a deterministic code-structure/index server, and none appears redundant. Each tool earns its place in the read/inspection workflow.
The surface is read-only and coherent, but every tool repeatedly says it 'errors if the repo is not enrolled,' yet there is no enroll tool, and diff references snapshot ids/labels with no snapshot-creation tool. These are notable missing lifecycle operations that create dead ends for a fresh agent.