better-code-review-graph
Related Servers
Alternatives to better-code-review-graph
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAI-powered codebase intelligence tool that builds a dependency graph of a git repo for structural Q&A and pre-PR code review. It exposes MCP tools for blast radius, review sessions, and static analysis, running locally over stdio with no LLM or network dependencies.MIT
- AlicenseAqualityCmaintenanceCode graph context engine that parses codebases with tree-sitter (170+ languages), builds structural dependency graphs, and provides 24 MCP tools for code intelligence. One prepare_context call gives your AI agent the right files for any task. Includes focus, blast radius, hotspots, dead code detection, and hybrid search.2442 PyPI1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceProvides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.11 npm1MIT

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- AlicenseAqualityAmaintenanceEnterprise-grade (40m+ lines) codebase intelligence in a zero-setup, private and local MCP: managed indexing, hybrid semantic search, polyglot code dependency graphs, and DB/API/infra knowledge. Benchmark: 61% less tokens, 84% fewer calls, 37x faster than standard AI grep.254,715 npm3,304AGPL 3.0
- AlicenseAqualityCmaintenanceCross-repository code knowledge graph MCP server for Java, Kotlin, JavaScript, and TypeScript. Indexes source code into embedded KuzuDB via tree-sitter and exposes 30+ tools for call-flow tracing, multi-hop taint analysis (OWASP/CWE/PCI/STIG), entry-point reachability filtering, performance hotspot detection, and license compliance — without reading source files. 95% fewer tokens vs source-read331MIT
TDQS
Scored across 7 tools
The core tools map to distinct concerns: graph management, querying, review context, security, and configuration. The main ambiguity is between `config` and `config__open_relay`, and `graph.summarize` could potentially be confused with `review.context`, but descriptions clarify the intended primary use.
Tool names are consistently short lowercase domain labels: graph, query, review, config, help, security. The `config__open_relay` tool breaks this pattern by promoting a sub-action with a double underscore to a top-level tool.
Seven tools is a well-scoped size for a code-review-graph server, with each tool grouping a coherent set of related actions. The count supports a broad feature set while remaining navigable and non-redundant.
The surface covers the full lifecycle: graph build/update/stats/embed/import/summarize, flexible querying and diff analysis, review-context generation, security scanning and suppression, plus configuration and credential setup. There are no obvious dead ends or missing core operations for the stated purpose.