code-index
Related Servers
Alternatives to code-index
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables coding agents to query a local-first code intelligence graph of Python repositories—covering functions, classes, modules, and their relationships—via MCP, supporting subgraph retrieval, caller lookup, and impact analysis without re-reading the codebase.-
- FlicenseNot gradedqualityDmaintenanceIndexes Python codebases using AST and BM25, providing 8 MCP tools for code exploration and search.-
- FlicenseBqualityBmaintenanceEnables interaction with indexed Python repositories through MCP tools for repository map, symbol search, file reading, and reference lookup.4-
- AlicenseAqualityBmaintenanceIndexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.722MIT
- FlicenseNot gradedqualityFmaintenanceProvides a local code knowledge graph for Java projects, enabling querying of classes, methods, fields, calls, inheritance, and imports via MCP tools like query, context, impact, and cypher.1-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that indexes a local Python codebase into a SQLite graph for hybrid code search, file context, lazy explanations, dependency traces, and version-aware symbol history.MIT
TDQS
Scored across 6 tools
Each tool has a distinct purpose: callers, class hierarchy, structural context, dependencies, detailed node info, and SPARQL queries. There is no overlap or ambiguity between them.
Most tools follow the 'get_' prefix pattern (get_callers, get_class_hierarchy, etc.), but query_sparql deviates slightly by using 'query' instead. The naming is still clear and predictable overall.
With 6 tools, the set is well-scoped for a code indexing server. Each tool provides essential functionality without redundancy or excess.
The tools cover structural analysis (context, details) and relational queries (callers, hierarchy, dependencies). The SPARQL endpoint allows arbitrary queries, filling most gaps. Minor missing direct tool for listing all modules, but query_sparql can handle that.