No user-submitted related servers found.
Scored across 30 tools
Several tools overlap in purpose: outline_file and get_file_skeleton both summarize a file's declarations, get_context with include:body overlaps get_symbol_context, and find_definition vs search_symbols both locate a symbol by name, while search_code vs find_references are both textual searches. However, the unusually detailed descriptions contain explicit routing guidance ('for symbols prefer find_definition/find_references', 'drop to get_symbol_context') that makes correct selection likely in most cases.
The dominant verb_noun snake_case convention is well-established and organized into clear subfamilies: get_*, find_*, search_*, memory_*, plus index_repo, read_lines, outline_file, replace_symbol, install_hook. Minor deviations exist: digest_get/digest_save invert the verb_noun order, one-word names (snapshot, recap, brief, stats, batch) break the pattern, and repo_map/dep_graph/context_pack are noun_noun compounds.
Thirty tools is on the heavy side, and the memory/persistence cluster alone consumes nine identifiers (memory_* x5, digest_* x2, brief, recap) while outline_file is largely redundant with get_file_skeleton. The broad scope (indexing, search, reading, editing, memory, stats, hooks) justifies most of the surface, but a trimmed design around 20-24 tools would be tighter.
The core workflow is fully covered: orient (brief, repo_map, digest_get), discover (search_code, search_symbols, search_intent, context_pack), read cheaply (read_lines, get_file_skeleton, get_symbol_context), edit safely (replace_symbol with snapshot and re-index), and remember (full memory CRUD). Minor gaps include no symbol delete/rename primitive and no general whole-file write tool, though replace_symbol is explicitly designed to complement ordinary client-side edit tools.