We have competition: GitNexus

[Mharbulous]

It seems we have some competition. I stumbled across: https://github.com/abhigyanpatwari/GitNexus. The architecture is strikingly similar — tree-sitter for AST parsing, MCP-exposed tools, same target IDEs (Claude Code, Cursor, Windsurf), same core value proposition of giving AI agents structured, token-efficient access to codebases instead of raw file reads. I put together a side-by-side tool comparison below that I think is worth the team's attention.

Category	jCodeMunch-MCP	GitNexus
Search / Discovery	search_symbols	query
Symbol detail	get_symbol_source	context
Blast radius / impact	get_blast_radius	impact
Change → affected code	get_changed_symbols	detect_changes
Safe rename	plan_refactoring	rename
Repo structure	get_repo_outline	list_repos
File structure	get_file_outline	—
Import analysis	find_importers	—
Call hierarchy	get_call_hierarchy	—
Class/inheritance hierarchy	get_class_hierarchy	—
Dead code detection	find_dead_code	—
Untested symbols	get_untested_symbols	—
Dependency cycles	get_dependency_cycles	—
Coupling metrics	get_coupling_metrics	—
Architectural centrality	get_symbol_importance	—
Churn/complexity hotspots	get_hotspots	—
Module topology	get_tectonic_map	—
Signal propagation tracing	get_signal_chains	—
Token-budgeted context	get_ranked_context	—
Git lineage / provenance	get_symbol_provenance	—
PR risk profile	get_pr_risk_profile	—
AST structural search	search_ast	—
Multi-constraint filtering	winnow_symbols	—
Pre-read planning	plan_turn	—
Config / token audit	audit_agent_config	—
Session telemetry	get_session_stats	—
Cross-session perf analysis	analyze_perf	—
Retrieval weight tuning	tune_weights	—
Embedding drift detection	check_embedding_drift	—
Auto-reindex status	get_watch_status	—
Raw graph queries	—	cypher
API route impact	—	api_impact
Route → handler map	—	route_map
MCP/RPC tool definitions	—	tool_map
Response shape validation	—	shape_check
Multi-repo: list groups	—	group_list
Multi-repo: sync contracts	—	group_sync
Multi-repo: search	—	group_query
Multi-repo: symbol context	—	group_context
Multi-repo: blast radius	—	group_impact

The table reveals a clear strategic divergence. jCodeMunch goes deep — 25 tools with no GitNexus equivalent, covering dead code, test gaps, coupling metrics, churn hotspots, AST pattern matching, git provenance, and retrieval tuning. It's built for agents that need to understand a single codebase at every level. GitNexus goes wide — its unique tools are mostly about breadth: raw graph access via Cypher, API/route-specific analysis for backend services, and five dedicated multi-repo tools for monorepo and microservice environments. If your codebase is a single well-bounded repo, jCodeMunch's depth wins. If you're coordinating across multiple services, GitNexus's group tooling fills a gap jCodeMunch doesn't yet address.