Codegraph

io.github.codegraph-ai由 GitHub 账号 codegraph-ai 发布v0.21.0更新于 Oct 24, 2026

Semantic code graph: 42 tools, 38 languages. Callers, impact, AI context, memory, PR review.

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

CodeGraph 为本地代码库构建语义图,并通过 42 个工具让助手进行代码导航、影响分析、PR 审查、文档检索与笔记记录。

可以做什么
在 38 种已解析语言中搜索和查看符号、签名、导入与调用图,支持关键词与语义混合检索。分析影响范围、复杂度、循环依赖、热点路径、未使用导入和模块概要。审查变更:一次调用即可给出 PR 的影响范围、测试缺口、过期文档和建议审查人。索引工作区、文件或目录,并进行增量重建。存储、搜索和停用项目级记忆,索引 Markdown 文档以进行语义检索、核对设计与代码是否一致并生成架构文档。
适用场景
适合助手在大型或多语言代码库中工作、需要按结构、调用方和影响范围导航而不是逐文件搜索的场景。也适合在 CI 中做 PR 审查,以及让设计文档和项目笔记与代码保持关联。
运行要求
以本地进程通过 stdio 运行,可从 npm 包安装,或首次运行时下载原生引擎二进制。服务器默认索引当前工作目录;工作区路径、排除目录、嵌入模型和工具配置通过命令行参数设置。可选环境变量包括 CODEGRAPH_STATIC_MODEL、CODEGRAPH_SKIP_MODEL_FETCH、CODEGRAPH_SKIP_MEMORY_CHECK 和 CODEGRAPH_TOOL_PROFILE。Linux 需要 glibc 2.30 以上以及 GCC 11 的 libstdc++。
安装前请注意
引擎是以用户权限运行的原生二进制,IDE 客户端会先询问再下载而非静默安装。索引会把源文件和函数体读入本地图数据库与向量,指向含密钥的仓库前应检查排除规则;内置跳过规则覆盖凭据目录和密钥类文件扩展名。记忆与文档工具会写入持久数据,重建索引会改变已存储的向量。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Codegraph,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

CodeGraph

Cross-language code intelligence for AI agents and developers.

[License]

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):

json
{  "mcpServers": {    "codegraph": {      "command": "/path/to/codegraph-server",      "args": ["--mcp"]    }  }}

The server indexes the current working directory automatically.

VS Code Extension

Install the VSIX:

bash
code --install-extension codegraph-0.21.0.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:

bash
codegraph-server --graph-only \  --run-tool codegraph_pr_context \  --tool-args '{"baseBranch":"main","format":"markdown"}'

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

FlagDefaultDescription
--workspace <path>current dirDirectories to index (repeatable for multi-project)
--exclude <dir>—Directories to skip (repeatable)
--embedding-model <model>bge-smallbge-small (384d, fast), jina-code-v2 (768d, 6× slower), granite-97m (384d, 32K ctx, ~3× slower), or static (model2vec, 256d — ~100× faster indexing, no ONNX; needs a local model dir, see below)
--full-body-embeddingtrueEmbed full function body (~50 lines) for better semantic search and duplicate detection. Takes a value: --full-body-embedding=false turns it off
--split-identifierstrueAlso embed the word-split form of identifiers whose words are run together, so getUserById embeds as "get user by id" too. Names already separated by _ or - are left alone, since they tokenise into the same words; a leading or trailing delimiter separates nothing, so _handleClick is split like handleClick. Takes a value: --split-identifiers=false embeds raw names, as releases up to 0.20.1 did
--max-files <n>5000Maximum files to index
--profile <name>allFilter the exposed MCP tool surface to a named subset (see below)
--graph-onlyoffSkip embedding generation — build the graph and serve structural tools only. No ONNX model load, 10-50× faster indexing. Semantic search and memory tools unavailable. For CI / one-shot graph queries.
--run-tool <name>—One-shot mode: index, run a single tool, print its result, exit. No MCP handshake. Pair with --tool-args '<json>'.

--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-mcp from npm downloads it into that default location for you (best-effort; set CODEGRAPH_SKIP_MODEL_FETCH=1 to 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_MODEL unset and let the engine resolve it. To use a model kept somewhere else, set codegraph.staticModelPath in VS Code, or Settings → Tools → CodeGraph → Embeddings → Static model directory in JetBrains; each client then passes that path as CODEGRAPH_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):

ProfileToolsUse when
all (default)every tool (community + pro)normal sessions
core8 — search + symbol info + AI contextchatty agent sessions where you only need lookups
graph17 — callers/callees/deps/impact/traverse/PR contextrefactoring + structural analysis
memory14 — codegraph_memory_* plus the docs toolsnote-taking / knowledge-base workflows
securitypro security tools only (empty on community)pro security audits

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)

ToolWhat it does
get_ai_contextPrimary context tool. Intent-aware (explain/modify/debug/test) with token budgeting. Returns source, related symbols, imports, siblings, debug hints.
get_edit_contextEverything needed before editing: source + callers + tests + memories + git history
get_curated_contextCross-codebase context for a natural language query ("how does auth work?")
analyze_impactBlast radius prediction — what breaks if you modify, delete, or rename
analyze_complexityCyclomatic complexity with breakdown (branches, loops, nesting, exceptions, early returns)
find_circular_depsDetect circular import/dependency chains across files
find_hot_pathsMost-called functions ranked by transitive caller count
find_dead_importsFind unused imports — modules imported but never referenced
get_module_summaryHigh-level summary of a directory: file count, functions, language breakdown, top complex functions
search_by_patternRegex search across function bodies, signatures, names, and docstrings
search_by_errorFind functions that throw, catch, or handle specific error types

Code Navigation (13)

ToolWhat it does
symbol_searchFind symbols by name or natural language (hybrid BM25 + semantic search)
get_callers / get_calleesWho calls this? What does it call? (with transitive depth)
get_detailed_symbolFull symbol info: source, callers, callees, complexity
get_symbol_infoQuick metadata: signature, visibility, kind
get_dependency_graphFile/module import relationships with depth control
get_call_graphFunction call chains (callers and callees)
find_by_importsFind files importing a module
find_by_signatureSearch by param count, return type, modifiers
find_entry_pointsMain functions, HTTP handlers, CLI commands, event handlers
find_implementorsFind all functions registered as ops struct callbacks
find_related_testsTests that exercise a given function
traverse_graphCustom graph traversal with edge/node type filters

Indexing (3)

ToolWhat it does
reindex_workspaceFull or incremental workspace reindex
index_filesAdd/update specific files without full reindex
index_directoryAdd directory to graph alongside existing data

Memory (7)

Persistent AI context across sessions — debugging insights, architectural decisions, known issues.

ToolWhat it does
memory_store / memory_get / memory_searchStore, retrieve, search memories (BM25 + semantic)
memory_contextGet memories relevant to a file/function
memory_list / memory_invalidate / memory_statsBrowse, retire, monitor

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)

ToolWhat it does
pr_contextOne-call PR review. Runs git diff against base branch, finds changed functions in the graph, reports: blast radius (callers), test coverage + gaps, affected modules, diff-aware change classification (signature vs body), stale-doc warnings, complexity, commit-message hint, suggested reviewers from git blame.

Documentation (7)

Persistent project documentation — index design docs, search them semantically, verify code matches the design, generate architecture docs from the code graph.

ToolWhat it does
index_markdownIndex a local .md file (ARCHITECTURE.md, API_DESIGN.md, etc.) into the persistent docs store. Heading-tree chunking with leaf-node embeddings.
search_docsSemantic search over indexed docs — returns matching sections with heading-path breadcrumbs
list_doc_sourcesList all indexed source files
remove_doc_sourceRemove all indexed chunks from a source file
verify_designCross-reference doc claims vs code graph. direction=forward (doc→code), reverse (code→doc), or both
design_gapsFind identifiers described in docs that don't exist in code yet — build TODO lists from specs
generate_architecture_docAuto-generate a structured ARCHITECTURE.md from the live code graph (modules, hot paths, complexity, circular deps)

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:

codegraph_index_markdown(path: "/projects/myapp/docs/ARCHITECTURE.md")codegraph_search_docs(query: "how does the auth module handle JWT refresh?")

Check if the code matches the design:

codegraph_verify_design(source: "/projects/myapp/docs/ARCHITECTURE.md", direction: "forward")// → "132/132 identifiers verified, 0 gaps"

Find what's described in docs but not yet implemented:

codegraph_design_gaps(source: "/projects/myapp/docs/API_DESIGN.md")// → "4 of 12 identifiers not found in code: PaymentService, RefundHandler, ..."

Generate architecture docs from the code graph:

codegraph_generate_architecture_doc(scope: "src/", topN: 5)// → Markdown with modules, complexity hotspots, hot paths, circular deps

Save a debugging insight for future sessions:

codegraph_memory_store(kind: "debug_context", title: "Nginx body size limit",  content: "The /upload endpoint fails on payloads > 1MB...",  problem: "API returns 500 on large uploads",  solution: "Increase nginx client_max_body_size to 10M",  agentSource: "claude")

Get AI context with graph compression stats + design doc augmentation:

codegraph_get_ai_context(uri: "file:///projects/myapp/src/auth.rs", line: 42, intent: "modify")// → Code context + graphStats: {entitiesInGraph: 13555, entitiesTraversed: 47, entitiesKept: 8}// → design_context section from indexed docs mentioning "auth"

Review a PR — blast radius, test gaps, stale docs, reviewers in one call:

codegraph_pr_context(baseBranch: "main")// → "PR changes 4 files (+263/-77, 12 functions). 37 direct callers, 8 tests, 3 untested. Risk: medium."// → test_gaps: [refresh_token, revoke_session] — functions with 0 test callers// → stale_docs: ["auth.rs described in ARCHITECTURE.md > Authentication — doc may need updating"]// → suggested_reviewers: [{author: "anvanster", lines_owned: 3200}]// → commit_hint: "feat(mcp): <describe the change>"

Narrow the tool surface for chatty sessions:

bash
codegraph-server --mcp --profile=core  # Only 8 tools: search + symbol info + AI context

CodeGraph Pro

Additional tools available in CodeGraph Pro:

ToolWhat it does
scan_securitySecurity vulnerability scan: 40+ dangerous function patterns, source-to-sink taint tracing, auth coverage for HTTP endpoints (7 languages/frameworks), architectural layer violations, weak crypto, hardcoded secrets
analyze_couplingModule coupling metrics and instability scores
find_unused_codeDead code detection with confidence scoring
find_duplicatesDetect duplicate/near-duplicate functions
find_similar / cluster_symbols / compare_symbolsEmbedding-based code similarity
cross_project_searchSearch across all indexed projects
mine_git_history / mine_git_history_for_file / search_git_historyGit history mining and semantic search
security_control_flowMap every execution path through a function — "can this return without hitting the auth check?"
security_trace_data_flowFollow a variable from birth to death — "does user input reach this SQL query?"
security_generate_sbomCycloneDX SBOM from 8 lockfile formats
security_audit_depsOSV vulnerability check on dependencies
security_check_unchecked_returns / _resource_leaks / _misconfig / _input_validation / _error_exposure5 heuristic analyzers covering ~80% of CWE Top 25
security_scan_iacDocker / Kubernetes / Terraform misconfiguration scan
security_check_licensesLockfile license policy enforcement (copyleft detection)
security_check_secrets_entropyShannon-entropy hardcoded-secret detection
security_detect_injectionFocused SQL/XSS/cmd/path/deser/template injection detection (20 patterns)
security_check_search_pathUntrusted search-path / DLL-hijacking detection (CWE-426/CWE-427)
security_check_cryptoCryptographic misuse: weak ciphers/hashes/PRNG/keys, static IVs, timing-leak comparisons (CWE-208/326-330/338/916, 35 patterns)
security_export_sarifAggregate findings as SARIF 2.1.0 (GitHub Code Scanning, GitLab SAST)

Cross-cutting features (all security_check_* tools):

  • include_tests / treat_as_production — first-class skip for tests/samples/vendored
  • check_compile_gates — C/C++ findings inside #ifdef X are 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:

CategoryLanguages
SystemsC, C++, Rust, Zig, Objective-C
JVMJava, Kotlin, Scala, Groovy, Clojure
Web/ScriptingTypeScript/JS, Python, Ruby, PHP, Perl, Lua, Elixir, Elm
Web/StyleCSS
MobileSwift, Dart
FunctionalHaskell, OCaml, Julia, Erlang, Elm, Clojure
EnterpriseC#, COBOL, Fortran, Go
BlockchainSolidity
Shell/ConfigBash, Dockerfile, HCL/Terraform, TOML, YAML
HardwareVerilog/SystemVerilog, Tcl
Data ScienceR, Julia

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

MCP Client (Claude, Cursor, ...)   VS Code Extension   JetBrains Plugin        |                                  |                  |    MCP (stdio)                       LSP Protocol       LSP Protocol        |                                  |                  |        └───────────┐               ┌──────┴──────────────────┘                    ▼               ▼            ┌─────────────────────────────┐            │       codegraph-server      │            ├─────────────────────────────┤            │  38 tree-sitter parsers     │            │  Semantic graph engine      │            │  AI query engine (BM25)     │            │  Memory layer (RocksDB)     │            │  Docs store (RocksDB+HNSW)  │            │  Full-body embeddings (BGE) │            │  HNSW vector index          │            └─────────────────────────────┘

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.

PlatformArchitectures
macOSApple Silicon (arm64) and Intel (x64)
Linuxx64 and arm64
Windowsx64 (Windows on ARM runs the x64 build under emulation)

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.

RunsDoes not run
SLES 15 SP4Ubuntu 20.04
Ubuntu 22.04 and newerDebian 11
Debian 12 and newerRHEL / CentOS 8
RHEL 9 and newerAmazon Linux 2
Amazon Linux 2023

Both Linux architectures have identical requirements. If the engine exits immediately with a message like

version `GLIBCXX_3.4.29' not found (required by codegraph-server)

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

bash
git clone https://github.com/codegraph-ai/codegraphcd codegraphcargo build --release -p codegraph-server    # Rust servercd vscode && npm install && npm run esbuild  # VS Code extensionnpx @vscode/vsce package                     # VSIX

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

来源:README.md,提交 590c2ca

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v0.21.0最新Oct 6, 2026
  2. v0.20.1Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分