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.5 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 gradedqualityBmaintenanceEnables 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 gradedqualityBmaintenanceIndexes 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.90 npm4Apache 2.0
- AlicenseAqualityAmaintenanceToken-safe code search for AI agents: queries the language-server index (clangd / Roslyn / tsserver / pyright) instead of grep and returns a token-capped file:line list — ~20x fewer tokens. Symbol-level editing + a grep→index rewrite hook. Local-only, no IDE.1613MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to perform deterministic, model-free repository analysis and patch operations—tree-sitter repo maps, symbol/reference lookup, and SEARCH/REPLACE parsing/validation—via a CLI or MCP stdio server, without ever calling a language model.1MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: structure for code layout, diff for changes, hash for fingerprinting, status for per-repo health, health for store-wide health, and locate for symbol resolution. There is no meaningful overlap; even structure and locate are distinct (broad structure vs. specific lookup).
All tool names are single-word, lowercase, with no underscores or mixed casing. This is perfectly consistent, even though they mix nouns and verbs. The pattern is predictable and easy to learn.
Six tools is a well-scoped set for a code analysis server. Each tool covers a distinct aspect of the domain without redundancy or bloat, and the count is within the ideal 3-15 range.
The tools cover core workflows: inspecting structure, diffing snapshots, hashing, checking health, and locating symbols. However, there is no direct way to list enrolled repositories or manage snapshots, which are minor gaps that agents may need to work around.