Can this be used as a general code knowledge tool rather than a code reviewer?

[sultannaufal]

Is there anything similar to this project that isn’t specifically for code review

[tirth8205]

Great question, yes, absolutely. The name says "code review" but the graph is a general-purpose code knowledge base. Most of the 22 MCP tools have nothing to do with code review:

Architecture & navigation:

• get_architecture_overview — auto-generated architecture map from community detection
• list_communities / get_community — discover how your code clusters
• query_graph — callers, callees, importers, inheritance chains
• list_flows / get_flow — trace execution paths from entry points

Search & discovery:

• semantic_search_nodes — find code entities by name or meaning
• get_impact_radius — "if I change this function, what breaks?"
• find_large_functions — find complex areas that need attention

Documentation:

• generate_wiki — auto-generate markdown documentation from the graph structure
• get_wiki_page — retrieve generated docs per module/community

Refactoring:

• refactor — rename preview, dead code detection, refactoring suggestions
• apply_refactor — execute a refactoring safely

People are using it for onboarding onto new codebases, understanding monorepos, planning refactors, and generating docs — not just code review.

To answer your other question: I haven't found anything else that does "persistent incremental structural graph exposed via MCP." The closest concept is Aider's repo-map (also Tree-sitter based), but it's embedded in Aider only, not standalone, and doesn't do blast radius, flows, or community detection. Repomix is another option but it just packs your whole repo into a file — no intelligence, no incremental updates.

[sultannaufal]

thanks, great work!

[HarishHary]

hello, great work here @tirth8205 but what about graphify?