mcp-gtags-server
Related Servers
Alternatives to mcp-gtags-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- AlicenseNot gradedqualityDmaintenanceProvides IDE-like code navigation and search for local repositories, enabling AI assistants to perform symbol search, trigram indexing, and semantic navigation.AGPL 3.0
- 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.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to search and navigate indexed codebases through lexical, semantic, and hybrid queries, with tools for symbols, call graphs, outlines, spans, impact analysis, and recall.9Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to quickly search and navigate large codebases by indexing symbols and references, offering tools for fuzzy symbol lookup, file outlining, and reference discovery without a language server.1MIT
- AlicenseNot gradedqualityDmaintenanceExposes type-aware code navigation and fast file search to AI agents via language servers, enabling definitions, references, symbols, and file lookup without reading entire codebases.2,580 npmMIT
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes — definition lookup, reference enumeration, caller/callee analysis, body extraction, file outline, and reachability — and the verbose descriptions reinforce those boundaries. However, find_callers and find_references both surface call sites (one deduplicated by enclosing function, one listing every use), and find_definition overlaps with get_symbol_body enough that an agent could misselect without reading closely.
Four tools follow a clean find_<plural-noun> pattern (find_callers, find_definition, find_references, find_callees), and list_file_symbols, get_symbol_body, and update_index all use verb_noun as well. The bare noun 'reachability' breaks the pattern, and the mix of 'list'/'get'/'find' verbs is slightly varied, but the overall convention is predictable and readable.
Eight tools is well-scoped for a C/C++ code navigation server. Each tool provides a distinct index query — definition, references, callers, callees, call path, symbol body, file outline, and index refresh — with no apparent redundancy, so every tool earns its place.
The surface covers the core navigation lifecycle thoroughly: definition resolution, reference enumeration, incoming/outgoing call analysis, transitive reachability, body extraction, file-level outlines, and index maintenance. The notable gap is that symbol lookup requires exact names — there is no prefix/fuzzy search for similarly named symbols, even though find_definition's description hints at such a fallback rather than providing a tool for it.