codetopo
Related Servers
Alternatives to codetopo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceCodeGraph — Open-source code intelligence MCP server. Builds a semantic graph of your codebase (functions, classes, imports, call chains) and exposes it through 31 tools. Callers, callees, impact analysis, complexity metrics, unused code detection, AI context assembly, persistent memory, cross-project search. 15 languages via tree-sitter. Single Rust binary, local-first.348 npm-
- AlicenseAqualityAmaintenanceLocal code search for AI agents over a tree-sitter index of your repo: exact symbol lookup, scope-aware usages, call graph and impact analysis, AST pattern search, indexed grep and semantic search. 28 MCP tools, 19 languages, runs fully offline.2812MIT
- AlicenseNot gradedqualityAmaintenanceStandalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.7Apache 2.0
- AlicenseCqualityAmaintenanceLocal search over your code and documents for AI agents. Hybrid search and a code graph over your code and documents (PDF, Word, PowerPoint, Excel, EPUB), served over MCP with file and line spans, from one Rust binary on your machine.2810Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal MCP server that gives your coding agent a code graph of your repository: who calls a function, what a change reaches, which tests cover it.1,098Apache 2.0

mcp-reposkeinofficial
AlicenseAqualityAmaintenanceDeterministic code-graph (GraphRAG) over your repo for LLM agents — local-first, git-native, zero-infra, served via MCP. Python, TS/JS, Rust, Go, Java, C#.813Apache 2.0
TDQS
Scored across 20 tools
Most tools have distinct purposes: search vs get_symbol (discovery vs exact), metrics vs rank vs communities vs topo_sort each measure different things. There is mild overlap among the traversal tools—ancestors, descendants, neighborhood, blast_radius, and path all walk the graph from a node—but the descriptions differentiate directionality and semantics (blast_radius specifically covers dependents/overriders/implementers).
All names are snake_case with a consistent codetopo_ prefix, giving a predictable, readable pattern. The only deviation is mixed verb-style vs noun-style names (get_symbol/search_symbols vs stats/metrics/communities), but this is coherent enough to navigate.
20 tools is on the heavy side for the 3-15 sweet spot, but this is a rich code-graph analysis domain with indexing, traversal, metrics, ranking, partitioning, topology, rendering, diffing, and auditing—each tool earns a distinct place. Borderline but defensible rather than redundant.
The surface covers the full lifecycle: indexing, schema description, discovery, exact retrieval, multiple traversal modes, structural metrics, ranking, communities, topo-sort, rendering, diff, snapshot, verification, diagnostics, and stats. Read/analysis needs are comprehensively met with no obvious dead ends.