
Codegraph
io.github.codegraph-aiPublished by GitHub account codegraph-aiv0.21.0Updated Oct 24, 2026
Semantic code graph: 42 tools, 38 languages. Callers, impact, AI context, memory, PR review.
Overview
CodeGraph builds a semantic graph of a local codebase and exposes it to an assistant through 42 tools for navigation, impact analysis, PR review, docs and notes
- What you can do
- Search and inspect symbols, signatures, imports and call graphs across 38 parsed languages, with hybrid keyword and semantic search. Analyze impact, complexity, circular dependencies, hot paths, dead imports and module summaries. Review changes: one call reports blast radius, test gaps, stale docs and suggested reviewers for a PR. Index workspaces, files or directories, and reindex incrementally. Store, search and retire project-scoped memories, and index markdown docs to search them, verify design against code and generate architecture docs.
- When to use it
- Useful when an assistant works on a large or multi-language repository and should navigate structure, callers and impact instead of grepping through files. Also suited to PR review in CI and to keeping design docs and project notes tied to the code.
- Requirements
- Runs as a local process over stdio, installed from the npm package or as a native engine binary downloaded on first run. The server indexes the current working directory by default; workspace paths, exclusions, embedding model and tool profile are set by flags. Optional environment variables include CODEGRAPH_STATIC_MODEL, CODEGRAPH_SKIP_MODEL_FETCH, CODEGRAPH_SKIP_MEMORY_CHECK and CODEGRAPH_TOOL_PROFILE. Linux needs glibc 2.30 or newer and a GCC 11 libstdc++.
Installation
In SourceWeft
- Open Codegraph in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CodeGraph
Cross-language code intelligence for AI agents and developers.
CodeGraph builds a semantic graph of your codebase — functions, classes, imports, call chains — and exposes it through 42 MCP tools, a VS Code extension, a JetBrains IDE plugin, and a persistent memory layer. Parses 38 languages via tree-sitter. AI agents get structured code understanding instead of grepping through files.
Quick Start
MCP Server (Claude Code, Cursor, any MCP client)
Add to ~/.claude.json (or your MCP client config):
The server indexes the current working directory automatically.
VS Code Extension
Install the VSIX:
One VSIX serves every platform.
The analysis engine is not bundled: on first activation the extension offers to download the engine built for your platform, verifies it against the published checksum, and installs it into ~/.codegraph/bin - the same location the JetBrains plugin uses, so one download serves both.
The download is offered rather than performed automatically, because it is a native binary that runs with your permissions.
Decline it and run CodeGraph: Download Analysis Engine from the command palette whenever you are ready.
Once an engine is present, the extension starts it automatically and registers all tools as Language Model Tools for Copilot.
JetBrains IDEs
A plugin for IntelliJ IDEA, PyCharm, GoLand, Android Studio and the rest of the
family drives the same engine over LSP: Code Vision, Symbols and Memories tool
windows, a graph panel, and one-click MCP registration for the AI Assistant.
It resolves or downloads the engine the same way the VS Code extension does,
sharing ~/.codegraph/bin.
→ jetbrains/README.md for surfaces, engine resolution order, and building from source.
Rules for AI agents
Pre-configured rule files that teach AI coding agents (Claude, Cursor,
Windsurf, Codex, Cline) to use CodeGraph MCP tools before falling back
to grep / multi-file reads. Maps natural-language intent to the right
codegraph_* tool.
→ codegraph-ai/codegraph-rules-for-agents
Setup is cp <agent>/codegraph.md ~/<agent>/ (one line per agent — see
the rules repo's README).
GitHub Action — PR review in CI
Drop a workflow into your repo to get an automatic code-graph analysis
comment on every PR — blast radius, test gaps, stale docs, suggested
reviewers. Runs graph-only (no embeddings, no ONNX model), so it's
fast and needs no API keys — just the built-in GITHUB_TOKEN.
Copy .github/workflows/codegraph-pr.yml
into your repo. The core invocation is a single command:
This prints a ready-to-post markdown comment. The --graph-only flag
skips embedding generation (10-50× faster indexing); --run-tool runs
one tool and exits without the MCP stdio handshake — ideal for scripting.
Upgrading to 0.21
Each project re-embeds once, in the background, the first time 0.21 opens it. Stored vectors now record the model and settings that built them, and an index from 0.20.1 or earlier records none. Keyword search keeps working while it runs.
Restart any --watch daemon after upgrading.
A daemon left running keeps writing vectors that 0.21 will not load, and sessions attached to it run without semantic search until it restarts.
Identifiers whose words run together, like getUserById, are now also embedded in word-split form.
This mostly helps natural-language search in camelCase languages such as TypeScript, Java and C#.
Pass --split-identifiers=false to keep the old behaviour.
--full-body-embedding=false now takes effect; in 0.20.1 the flag was always on.
Configuration
MCP Server flags
--split-identifiers and --full-body-embedding both change the text every symbol is embedded from, and vectors built from different text cannot be ranked against each other.
A project's stored vectors are therefore stamped with the settings that built them - --embedding-model included, since models differ in dimension - and are ignored by any process configured differently.
Changing any of the three re-embeds in the background rather than requiring a manual reindex.
Run --watch with the same flags as the sessions that read the project, so both sides share one set instead of re-embedding over each other.
For what this means when upgrading from 0.20.1 or earlier, see Upgrading to 0.21.
--embedding-model static — model2vec fast indexing
Static (model2vec) embeddings replace the ONNX transformer with a token→vector
lookup table: indexing is ~100× faster (this repo's 5,873 symbols embed in
~1 s vs ~3.4 min with BGE) and there's no ONNX runtime or 1.5 GB RAM gate.
Retrieval stays hybrid (BM25 + semantic), so end-to-end quality is ~90% of BGE.
The model is not bundled with any client — it needs a local model directory
(config.json + tokenizer.json + model.safetensors) at
~/.codegraph/static_models/jina-code-static-256, or wherever
CODEGRAPH_STATIC_MODEL points:
- Installing
@astudioplus/codegraph-mcpfrom npm downloads it into that default location for you (best-effort; setCODEGRAPH_SKIP_MODEL_FETCH=1to skip, and the install never fails over it). - Otherwise fetch the prebuilt one with
scripts/fetch-static-model.sh, or distill your own from any sentence-transformer (Apache-2.0 Jina-Code by default) in ~30 s on CPU:python scripts/distill_static_model.py. - A model in the default location needs no IDE setting: both IDE clients leave
CODEGRAPH_STATIC_MODELunset and let the engine resolve it. To use a model kept somewhere else, setcodegraph.staticModelPathin VS Code, or Settings → Tools → CodeGraph → Embeddings → Static model directory in JetBrains; each client then passes that path asCODEGRAPH_STATIC_MODEL.
CODEGRAPH_SKIP_MEMORY_CHECK — force the embedding model past the RAM gate
Before loading the ONNX model, the server checks available memory and, if under
~1.5 GB, skips the model to avoid an OOM-kill (running graph-only instead).
Set CODEGRAPH_SKIP_MEMORY_CHECK=1 (also accepts true/yes) to bypass that
check and always load the model.
Use it if embeddings are disabled even though the machine has plenty of free
RAM.
A reading of 0 MB available is treated as a detection failure and the model
loads anyway (macOS parks reclaimable memory in inactive/speculative pages that
some memory readers do not count as free), so this override is mainly for other
cases where the reported figure is low but wrong.
It works in both MCP and one-shot --run-tool modes.
--profile — narrow the MCP tool surface
The full 42-tool surface is convenient but inflates the agent's prompt-context cost. A profile exposes only the slice you need (also settable via the CODEGRAPH_TOOL_PROFILE env var):
VS Code settings
The codegraph.* settings are documented once, next to the extension that
reads them:
→ vscode/README.md — Configuration
Full-body embeddings are enabled by default. Function body text is captured at parse time with zero I/O overhead.
Built-in exclusions (always skipped) cover ~47 directories across three categories:
- Build / cache:
node_modules,target,dist,build,out,.git,__pycache__,vendor,.venv,venv,.tox,.pytest_cache,.mypy_cache,.ruff_cache,.next,.nuxt,.svelte-kit,.parcel-cache,.npm,.yarn,.pnpm-store,.cache,.cargo,.bundle,.gradle,DerivedData,Pods,xcuserdata,cmake-build-* - IDE / IaC state:
.idea,.vscode-test,.fleet,.terraform,.terragrunt-cache,.serverless - Sensitive credential dirs:
.aws,.ssh,.gnupg,.kube,.docker
Plus glob patterns for binary archives, native libraries, OS metadata, and secret file extensions (*.pem, *.key, *.p12, *.pfx, *.crt, *.gpg, *.kdbx, SSH key conventions like id_rsa, etc.) — defense in depth against accidentally embedding credentials.
Indexing produced zero files, or something else looks wrong? See docs/troubleshooting.md.
Tools
42 community tools, plus 27 more (17 of them security analyzers) in CodeGraph Pro.
Code Analysis (11)
Code Navigation (13)
Indexing (3)
Memory (7)
Persistent AI context across sessions — debugging insights, architectural decisions, known issues.
Pairs well with Tempera — an episodic memory system that captures transferable debugging strategies and solutions across projects. CodeGraph's memory tools store project-scoped notes; Tempera captures cross-project BKMs (best-known methods) that improve over time.
PR / Change Analysis (1)
Documentation (7)
Persistent project documentation — index design docs, search them semantically, verify code matches the design, generate architecture docs from the code graph.
All tool names are prefixed with codegraph_ (e.g. codegraph_get_ai_context). Tools that target a specific symbol accept uri + line or nodeId from symbol_search results.
Usage examples
Index a design doc and search it:
Check if the code matches the design:
Find what's described in docs but not yet implemented:
Generate architecture docs from the code graph:
Save a debugging insight for future sessions:
Get AI context with graph compression stats + design doc augmentation:
Review a PR — blast radius, test gaps, stale docs, reviewers in one call:
Narrow the tool surface for chatty sessions:
CodeGraph Pro
Additional tools available in CodeGraph Pro:
Cross-cutting features (all security_check_* tools):
include_tests/treat_as_production— first-class skip for tests/samples/vendoredcheck_compile_gates— C/C++ findings inside#ifdef Xare marked DEFENSIVE_GATED_OFF when X isn't defined by CMake/Cargo/Makefile- 25-marker suppression honoring (
# nosec,// NOLINT,// codeql[ignore],# rubocop:disable, etc.) at line and function level - Telemetry blocks per scan:
path_filter(examined/matched/skipped) +compile_gate(gated_off count)
Languages
38 languages parsed via tree-sitter — functions, classes, imports, call graph, complexity metrics, dependency graphs, symbol search, and impact analysis:
HTTP handler detection: Python (FastAPI/Flask/Django), TypeScript (NestJS), Java (Spring/JAX-RS), Go (stdlib/Gin/Echo/Fiber), C# (ASP.NET), Ruby (Rails), PHP (Laravel/Symfony).
Community vs full builds: COBOL, Fortran, Perl, Dart, Zig, and R are compiled only with
--features extra-languages. The default community binary omits them — they had zero usage in telemetry and their tree-sitter grammars add ~25 MB (COBOL's parse tables alone are 30 MB). The other 32 languages are always available.
Architecture
A single Rust binary serves both MCP and LSP protocols.
- Indexing: ~60 files/sec. Incremental re-indexing on file changes via FNV-1a content hashing.
- Persistence: Graph and embeddings persist to
~/.codegraph/graph.db(RocksDB). Instant startup on restart — no re-parsing, no re-embedding. - Queries: Sub-100ms. Cross-file import and call resolution at index time.
- Embeddings: Full-body (function bodies captured at parse time, zero disk I/O). Vectors stored in RocksDB alongside the graph. Auto-downloads model on first run.
Supported platforms
The engine is a native binary, downloaded for your platform on first run.
Linux requires glibc 2.30 or newer and a libstdc++ from GCC 11 or newer
(GLIBCXX_3.4.29). The second requirement is the binding one, and it is not
implied by the first — the engine embeds ONNX Runtime, which is built with
GCC 11.
Both Linux architectures have identical requirements. If the engine exits immediately with a message like
the distribution's C++ runtime is older than the engine needs; installing a
newer libstdc++ (for example RHEL 8's gcc-toolset-11) resolves it without
upgrading the distribution.
Building from Source
Requires rustup (it installs the Rust version pinned in rust-toolchain.toml), Node.js 18+, VS Code 1.90+.
Support the project
CodeGraph is free, open-source, and maintained by a solo developer. If it saves you time, consider sponsoring on GitHub — it helps keep the project alive and growing.
License
Apache-2.0
Source: README.md at commit 590c2ca
Tools
0Version history
2- v0.21.0LatestOct 6, 2026
- v0.20.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts