Enables AI agents to query a repository's symbol graph to perform impact analysis, call tracing, and structural audits across Python, TypeScript, and Go.
Also known as zaebee/codegraph-brain, codegraph-brain
- Stars
- 2
- Tools
- 11
- Downloads, 30 days
- 2,281
- Latest version
- 0.39.2
- Last commit
- Nov 8, 2026
- License
- MIT
What is CGIS Code Graph MCP?
CGIS Code Graph is an MCP server. Enables AI agents to query a repository's symbol graph to perform impact analysis, call tracing, and structural audits across Python, TypeScript, and Go. It exposes 11 tools, such as cgis_ingest, cgis_overview, cgis_find_symbol.
Summary generated from the project's README
About CGIS Code Graph MCP server
CGIS Code Graph Intelligence System provides a way for AI agents to navigate codebases using a structured symbol graph instead of relying on text searches or file reading. It parses repositories using tree-sitter to map calls, imports, and containment between symbols, storing this data in a local SQLite database. This approach allows agents to perform precise impact analysis and call tracing across Python, TypeScript, and Go projects.
The system runs locally without requiring accounts or telemetry, ensuring the graph remains on your disk. Developers can integrate it with MCP clients like Claude Desktop or Cursor using uvx to fetch the server from PyPI. It offers specialized tools for structural audits, such as checking reachability for authorization or measuring architectural drift. By resolving calls to fully qualified names, it prevents the hallucinations common in standard text-based retrieval methods.
What you can do with it
- 1Perform impact analysisDetermine which upstream components will break if a specific function or method is modified.
- 2Trace execution flowFollow the transitive chain of calls to see exactly what a specific method invokes.
- 3Audit security coverageVerify that every request handler successfully reaches its intended authorization guard.
- 4Measure code quality metricsAnalyze the codebase for god classes, coupling, and package cohesion.
Written from the project's README. Every use case is checked against a quote from it.
How to install CGIS Code Graph MCP
Formats verified 10 Nov 2026Install CGIS Code Graph MCP in Claude Code
$ claude mcp add codegraph-brain -- uvx codegraph-brainInstall CGIS Code Graph MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"codegraph-brain": {
"command": "uvx",
"args": [
"codegraph-brain"
]
}
}
}Install CGIS Code Graph MCP in VS Code
.vscode/mcp.json
{
"servers": {
"codegraph-brain": {
"type": "stdio",
"command": "uvx",
"args": [
"codegraph-brain"
]
}
}
}Install CGIS Code Graph MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"codegraph-brain": {
"command": "uvx",
"args": [
"codegraph-brain"
]
}
}
}Install CGIS Code Graph MCP in Codex
~/.codex/config.toml
[mcp_servers.codegraph-brain] command = "uvx" args = ["codegraph-brain"]
Install CGIS Code Graph MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"codegraph-brain": {
"command": "uvx",
"args": [
"codegraph-brain"
]
}
}
}CGIS Code Graph MCP tools 11
Detected from the READMEcgis_ingestcgis_overviewcgis_find_symbolcgis_analyze_impactcgis_trace_flowcgis_get_structurecgis_contextcgis_metricscgis_audit_reachabilitycgis_driftcgis_validate
| cgis_ingest | — | |
| cgis_overview | — | |
| cgis_find_symbol | — | |
| cgis_analyze_impact | — | |
| cgis_trace_flow | — | |
| cgis_get_structure | — | |
| cgis_context | — | |
| cgis_metrics | — | |
| cgis_audit_reachability | — | |
| cgis_drift | — | |
| cgis_validate | — |
Configuration
GUARDIAN_PROVIDERGUARDIAN_SKEPTIC
| Name | Description | |
|---|---|---|
| GUARDIAN_PROVIDER | — | |
| GUARDIAN_SKEPTIC | — |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub🧠 CGIS: Code Graph Intelligence System
A code graph your AI agent can query instead of guess
Ask "what breaks if I change this?" and get the call chain, not a guess.
CGIS parses a repository with tree-sitter into a graph of fully qualified symbols and the calls, imports and containment between them, stores it in SQLite, and serves it to AI agents over MCP. An agent that would otherwise grep and read whole files asks the graph instead.
- Languages: Python · TypeScript / TSX · Go (structure and metrics only; its impact answers are a lead to confirm by reading — exp4, measured on one library, golang/crypto, mostly its ssh package; not measured on applications) · JSON and YAML (data key declarations only, when data keys are enabled with
--data-keys: no symbols, calls or impact) - Runs: locally — no account, no telemetry; the graph never leaves your disk (the one opt-in exception)
$ cgis ingest src --output graph.db
$ cgis impact cgis.query.engine.QueryEngine.get_flow_graph --db graph.db --depth 2
🔍 Analyzing transitive upstream callers of: cgis.query.engine.QueryEngine.get_flow_graph
METHOD cgis.query.engine.QueryEngine.get_flow_graph (cgis/query/engine.py:215)
├── FUNCTION cgis.query.context.context_service._collect_callees (cgis/query/context/context_service.py:44)
│ └── FUNCTION cgis.query.context.context_service.build_context (cgis/query/context/context_service.py:96)
└── METHOD cgis.guardian.collector.ContextCollector._graph_sections (cgis/guardian/collector.py:174)
├── METHOD cgis.guardian.collector.ContextCollector.collect_graph_context (cgis/guardian/collector.py:213)
└── METHOD cgis.guardian.collector.ContextCollector.collect_for_chunk (cgis/guardian/collector.py:303)
Real output — CGIS run on its own source.
🚀 Quickstart
In Claude Code (fastest)
/plugin marketplace add zaebee/codegraph-brain
/plugin install cgis@codegraph-brain
That ships the MCP server, a skill that teaches the agent when to query the graph instead of reading files, and /cgis:ingest to build the graph on first use. The server is pulled from PyPI on demand via uvx, so there is nothing to clone or build.
Any other MCP client (Cursor, Claude Desktop, …)
{
"mcpServers": {
"cgis": { "command": "uvx", "args": ["--from", "codegraph-brain", "cgis-mcp"] }
}
}
From the terminal
# No install needed — uvx fetches it from PyPI
uvx --from codegraph-brain cgis ingest ./my-project --output graph.db
uvx --from codegraph-brain cgis impact "my_module.core_function" --db graph.db --depth 5 # who calls this
uvx --from codegraph-brain cgis trace "my_module.MyClass.run" --db graph.db --depth 3 # what this calls
# add --format mermaid (or json) to either for a diagram or machine-readable output
Or install it for good: pip install codegraph-brain (Python 3.12+), then use cgis directly. The full command list is in CLI_USAGE.md.
📈 Proof at Real Scale
CGIS runs on a working twelve-repository estate — four languages, 8,146 commits, shipping daily. On its FastAPI backend it classifies 82.7% of 87,845 edges definitively and prints the remaining 17.3% rather than inventing targets for them — including the part that is CGIS's own gap.
That share rose from 11.4% in #459, which stopped counting calls to missing symbols as resolved. About 4 points of what is left is a known resolver gap, not something undiscoverable: ingesting app/ strips the app. prefix its imports carry, and the import path does not yet reconcile the two — the same backend ingested at its package root reports 13.2%. The number is what the tool admits it cannot place today, and it is allowed to move the unflattering way.
Read the case study → — every figure measured and reproducible, including what CGIS doesn't cover.
🤔 Why a graph, and how this differs
Text retrieval hands an agent chunks that look related. It cannot say which of three functions named save a call reaches, or what sits five callers up. CGIS resolves every call site to a fully qualified name when the source allows it — and when it does not, the edge stays marked unresolved and is counted, never filled with a plausible guess.
| If you use… | CGIS adds |
|---|---|
| grep / file reads in the agent | Transitive callers and callees in one call, without spending context on whole files |
| LSP-backed symbol tools (e.g. Serena) | A persisted whole-repo graph for multi-hop impact, coupling, PageRank and drift |
| A repo map (e.g. aider) | Resolved edges you can traverse and audit, with the resolved/unresolved ratio reported |
🤖 MCP Tools
The main tools:
| Tool | Answers |
|---|---|
cgis_ingest |
Build or incrementally refresh the graph |
cgis_overview |
Where to start: sizes and the largest packages, when you have no FQN yet |
cgis_find_symbol |
Partial name → candidate FQNs |
cgis_analyze_impact |
What breaks upstream if this changes? |
cgis_trace_flow |
What does this call, transitively? |
cgis_get_structure |
Class / module hierarchy |
cgis_context |
A compact GraphRAG context package for one symbol |
cgis_metrics |
Coupling, god classes, PageRank, package cohesion |
cgis_audit_reachability |
Authz / IDOR coverage — does every handler reach its guard? |
cgis_drift |
How far each domain has moved from its declared pattern |
cgis_validate |
Graph integrity: resolved vs unresolved edges |
All 16 tools, with parameters: MCP_REFERENCE.md.
🏗️ How It Works
- Extract — tree-sitter parsers turn each file into nodes and raw call edges.
- Resolve — the
ResolverEnginemaps raw calls to fully qualified names, or leaves them explicitly unresolved. - Store — SQLite holds the graph; queries are breadth-first traversals over it.
graph LR
A[Source Code] --> B[Extractors]
B --> C[Resolver Engine]
C --> D[(SQLite Graph DB)]
D --> E[MCP Server]
D --> F[Prompt Compiler]
E --> G[AI Agents]
F --> G
The details — and a pipeline graph CGIS regenerates from its own source on every change — are in HOW_IT_WORKS.md, and the full map of every document with its generated cross-references to the code is in docs/INDEX.md.
🛡️ Guardian: Graph-Aware Code Review
Guardian is CGIS's built-in LLM reviewer — it reviews pull requests using the graph as context, not just the diff text. It runs in CI and posts inline comments anchored to the exact line.
- Two-stage, recall-first: a finder surfaces every plausible defect (optimised for recall), then a separate skeptic pass filters false positives — closer to how human reviewers work, and far more reliable than a single precision-gated prompt.
- Local or cloud, no lock-in: point it at Ollama (
qwen2.5-coder,llama3.1,granite-code, …) for free local inference, or at Mistral / Gemini / Claude / OpenCode Go (DeepSeek) in the cloud. You can even mix them — a strong cloud finder with a free local cross-model skeptic. - Graph-aware context: the reviewer sees impact graphs, architectural drift, and project ontology — so it catches structural and convention defects a flat-diff reviewer can't.
- Deterministic anchoring: every inline comment is positioned by a verbatim quote from the diff, not the model's (often wrong) line guess.
- Dogfooded & measured: Guardian reviews CGIS's own pull requests, and a benchmark harness scores it against curated ground truth — so prompt changes are validated, not guessed.
# Build the graph, then review a PR with a local model (no API key).
# --inline posts over HTTPS with GH_TOKEN (or GITHUB_TOKEN); no gh CLI needed.
# The reusable workflow exports GH_TOKEN for you.
cgis ingest ./src --output graph.db
GUARDIAN_PROVIDER=ollama GUARDIAN_MODEL=qwen2.5-coder:14b \
uv run python scripts/guardian_review.py --pr 123 --db graph.db --inline
# Or OpenCode Go / DeepSeek: deepseek-v4.1-flash unless GUARDIAN_MODEL names another.
# GUARDIAN_OPENCODE_EFFORT is low unless set (the catalog lists low|high|max; other values
# pass through to the gateway). GUARDIAN_OPENCODE_BASE_URL pins a different gateway.
# No ANTHROPIC_API_KEY is needed for this provider.
GUARDIAN_PROVIDER=opencode-go GUARDIAN_MODEL=deepseek-v4.1-flash OPENCODE_API_KEY=... \
uv run python scripts/guardian_review.py --pr 123 --db graph.db --inline
# Or a Claude skeptic over a Mistral finder: Claude Haiku 5.5 unless GUARDIAN_SKEPTIC_MODEL names
# another, at GUARDIAN_ANTHROPIC_EFFORT=low unless set (low|medium|high|xhigh|max). Claude models
# reject a sampling temperature, so GUARDIAN_TEMPERATURE must be unset.
GUARDIAN_SKEPTIC=anthropic ANTHROPIC_API_KEY=... MISTRAL_API_KEY=... \
uv run python scripts/guardian_review.py --pr 123 --db graph.db --inline
In GitHub Actions, opencode-go needs no static key: the reusable workflow exchanges a short-lived GitHub OIDC token for inference access immediately before the review. Enable OIDC for GitHub Actions in the Opencode console, set the calling repository's OPENCODE_CLIENT_ID variable, and grant the review job id-token: write. OPENCODE_API_KEY is then minted at run time and never stored as a secret. Sign-in happens when GUARDIAN_PROVIDER is opencode-go, opencode, or unset (unset means the minted key makes opencode the auto-detected provider); an explicit other provider skips it.
No GPU on hand? Benchmark it on a notebook GPU → — free end to end, since the fixtures score without an LLM judge. Or point Guardian at a remote Ollama → — over an frp stcp tunnel, no public port, and a guard that refuses a review of a silently truncated prompt.
🔒 Privacy
CGIS collects nothing: no telemetry, no analytics, no account. Your code and the graph built from it stay on your machine. The one exception is opt-in: Guardian, if you run it with a cloud model, sends the reviewed diff to the provider you chose. See PRIVACY.md.
🛠️ Development
Requires Python 3.12+ and uv.
git clone https://github.com/zaebee/codegraph-brain && cd codegraph-brain
uv sync
make pytest
See CONTRIBUTING.md for the standards: strict MyPy, linting, ontology compliance.
💼 Architecture Audit
CGIS is free and you can run it yourself. If you would rather have the analysis than the tool, I run a fixed-price audit of your codebase's structure — authorisation coverage, blast radius, coupling, architectural drift — delivered in five working days, $2,400 fixed, with an explicit list of what the analysis cannot see. Read what's included →
CGIS Code Graph MCP questions
How do I add CGIS Code Graph MCP to Claude Code?
Run claude mcp add codegraph-brain -- uvx codegraph-brain in your terminal. Add --scope user to make it available in every project.
How do I add CGIS Code Graph MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does CGIS Code Graph MCP provide?
It exposes 11 tools, including cgis_ingest, cgis_overview, cgis_find_symbol, cgis_analyze_impact, cgis_trace_flow.
What languages does CGIS support?
It supports Python, TypeScript/TSX, and Go (for structure and metrics), as well as JSON and YAML for data key declarations.
Is my code sent to a server?
No, the tool runs locally with no telemetry or accounts, and the graph stays on your disk, except when using cloud models for the Guardian reviewer.
How can I use this with Claude Code?
You can add it using the plugin marketplace command: /plugin marketplace add zaebee/codegraph-brain and then /plugin install cgis@codegraph-brain.