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.386 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.32812MIT
- 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.6Apache 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#.812Apache 2.0- AlicenseAqualityAmaintenanceCall graph MCP server for Rust, Python, TypeScript, TSX, and JavaScript. Every caller and callee carries a resolution field showing how the reference was matched to a definition, plus multi-hop impact analysis for refactoring. Local-only, single binary, no network egress. Benchmarked against grep, ripgrep, and ctags on a 120-item hand-verified golden set, including the cases where it loses.3MIT
- AlicenseNot gradedqualityCmaintenanceMulti-language code-graph MCP server with 18 tools for structural code queries — find_symbol, callers, callees, blast_radius, dead_code, and cross-stack dataflow_trace from HTTP request through service layers to SQL. Tree-sitter parsing for Python, TypeScript, JavaScript, and Go; local-first, no API key required.19MIT
This server cannot be deployed
TDQS
Scored across 12 tools
Most tools target clearly distinct operations: indexing, traversal in one direction, blast-radius calculation, pathfinding, symbol lookup, schema description, export, and audit verification. The main potential confusion is between traversal tools like descendants, ancestors, neighborhood, and blast_radius, since all involve following graph edges, but the descriptions provide enough detail to distinguish their specific semantics.
All tool names use a consistent codetopo_ prefix and snake_case formatting, which makes them easy to scan. The naming mixes noun-style names (descendants, ancestors, path, stats, neighborhood) with verb-style and verb_noun names (index, verify, snapshot, get_symbol, search_symbols, describe_schema), but the pattern remains predictable and readable.
Twelve tools is a well-scoped set for a code graph database server, covering indexing, several complementary graph queries, schema introspection, snapshot export, and audit verification. Each tool appears to earn its place without obvious redundancy or filler.
The surface covers the core lifecycle: creating an index, discovering and inspecting symbols, traversing relationships, pathfinding, blast-radius analysis, schema description, export, and audit verification. Minor gaps might include listing or deleting existing indexes, but the read/query side is strongly covered for the stated purpose.