codegraph
Related Servers
Alternatives to codegraph
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to perform zero-execution, AST-based static analysis of JavaScript/TypeScript codebases, including symbol lookup, dependency tracing, change-impact analysis, dead-code detection, and risk assessment.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and terminal users to query codebases for callers, impact, tests, dependencies, and refactor previews using static AST analysis, with every match accounted for and uncertain relationships clearly marked.1,016 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a precise, local call/type/data graph so they can find who calls what, what breaks when code changes, and which tests to run, with every answer traced to file:line.99 PyPI1Functional Source , Version 1.1, ALv2 Future
- AlicenseAqualityCmaintenanceIndexes any TypeScript / React / Next.js repo into a queryable code graph and exposes 13 MCP tools — who-renders, who-calls, find-references, blast-radius, find-cycles, dead-code orphans, and local semantic search — so agents query structure instead of reading whole files. Built on ts-morph, so edges are resolved, not grepped.142MIT
- AlicenseNot gradedqualityDmaintenanceEnables querying and analyzing code relationships by building a lightweight graph of TypeScript and Python symbols. Supports symbol lookup, reference tracking, impact analysis from diffs, and code snippet retrieval through natural language.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local structural code graph, inspect relationships and impact, and retrieve focused project context before reading full files.24 npmMIT
TDQS
Scored across 9 tools
Most tools target clearly distinct analyses: search, callees, who_calls, dead_code, cycles, archaeology, hotspots, impact, trace. The only real overlap is who_calls vs impact (direct callers vs transitive reverse closure), but the descriptions make the boundary explicit (one-hop with locations vs risk-sorted closure with evidence chains). callees and who_calls are deliberate mirrors and are named accordingly.
All names are lowercase snake_case or single words (dead_code, who_calls, hotspots), so the surface is visually uniform. Minor deviation: 'search' is a verb while the rest are nouns/analysis names, and the set does not follow a verb_noun convention, but internally it is predictable.
Nine tools is well within the ideal 3-15 range and each maps to a distinct code-graph query (search, callers, callees, dead code, cycles, blame, ranking, impact, tracing). Nothing feels padded or redundant.
Covers discovery, bidirectional call navigation, transitive impact, dead code, import cycles, hotspot ranking, and git archaeology — a solid lifecycle for static code-graph analysis. Minor gaps: no forward import/dependency query (only cycle detection), and no dedicated symbol-detail/definition tool, though search plus call-site locations partly compensate.