better-code-review-graph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| graphC | Build and manage the code knowledge graph. Actions: build (full_rebuild, base, repo_root), update (base, repo_root), stats (repo_root), embed (repo_root), export (format, output_path, repo_root), import (import_path, repo_root), summarize (max_nodes, repo_root). Use |
| queryB | Query the code knowledge graph for relationships, search, and impact analysis. Actions: query (pattern, target), search (search_query), impact (changed_files|base), large_functions (min_lines), spot_check (n -- random callsite snippets from last callers_of/callees_of/inheritors_of/importers_of result), renamed_in_diff (base -- symbols whose callsite line shifted vs base ref), diff (from_sha, to_sha -- nodes added/removed/modified between two commit SHAs). Use |
| reviewA | Generate token-efficient review context for code changes. Actions: context (default — auto-detects changed files from git diff, returns structural summary, impacted nodes, source snippets, and review guidance), delta (from_sha, to_sha — wraps the |
| configC | Server configuration, status, and credential setup. Actions: status (show state), set (key, value -- keys: log_level), cache_clear (wipe embeddings), setup_status (credential state), setup_start (relay browser setup), setup_skip (local mode), setup_reset (clear credentials), setup_complete (re-resolve from env). Use |
| helpA | Get full documentation for any tool. Topics: graph | query | review | config | security | recipes. Use when compressed descriptions are insufficient. |
| securityA | Security scanning over the code knowledge graph. Actions: scan (engine='heuristic'|'semgrep', repo_root), report (format='json'|'sarif', repo_root), suppress (rule_id, remove=false, repo_root), rule_list (engine='heuristic'|'semgrep'). Use |
| config__open_relayA | Get the relay configuration URL for better-code-review-graph, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.