A high-performance code knowledge graph server implementing the Model Context Protocol (MCP). Indexes codebases into a structured AST knowledge graph with semantic search, call graph traversal, and HTTP route tracing — designed to give AI coding assistants deep, structured understanding of your code.
- Multi-language parsing — Tree-sitter AST extraction for TypeScript, JavaScript, Go, Python, Rust, Java, C, C++, HTML, CSS
- Semantic code search — Hybrid BM25 full-text + vector semantic search with Reciprocal Rank Fusion (RRF), powered by sqlite-vec
- Call graph traversal — Recursive CTE queries to trace callers/callees with cycle detection
- HTTP route tracing — Map route paths to backend handler functions (Express, Flask/FastAPI, Go)
- Impact analysis — Determine the blast radius of code changes by tracing all dependents
- Incremental indexing — Merkle tree change detection with file system watcher for real-time updates
- Context compression — Token-aware snippet extraction for LLM context windows (L0→full code, L1→summaries, L2→file groups, L3→directory overview)
- Embedding model — Optional local embedding via Candle (feature-gated
embed-model) - MCP protocol — JSON-RPC 2.0 over stdio, plug-and-play with Claude Code, Cursor, Windsurf, and other MCP clients
- Claude Code Plugin — First-class plugin with slash commands (
/understand,/trace,/impact), agents, skills, auto-indexing hooks, StatusLine integration, and self-updating
Unlike naive full-text search or simple AST dumps, code-graph-mcp builds a structured knowledge graph that understands the relationships between symbols across your entire codebase.
BLAKE3 Merkle tree tracks every file's content hash. On re-index, only changed files are re-parsed — unchanged directory subtrees are skipped entirely via mtime cache. When a function signature changes, dirty propagation automatically regenerates context for all downstream callers across files.
Combines BM25 full-text ranking (FTS5) with vector semantic similarity (sqlite-vec) via Reciprocal Rank Fusion (RRF) — so searching "handle user login" finds the right function even if it's named authenticate_session. Results are auto-compressed to fit LLM context windows.
The parser doesn't just find function calls — it tracks them within their proper scope context. Extracts calls, imports, inheritance, interface implementations, exports, and HTTP route bindings. Same-file targets are preferred over cross-file matches to minimize false-positive edges.
Unique to code-graph-mcp: trace from GET /api/users → route handler → service layer → database call in a single query. Supports Express, Flask/FastAPI, and Go HTTP frameworks.
Single binary, embedded SQLite, bundled sqlite-vec extension, optional local embedding model via Candle — no database server, no cloud API, no Docker required. Runs entirely on your machine.
Every design decision — from token-aware compression to node_id-based snippet expansion — is optimized for LLM context windows. Works out of the box with Claude Code, Cursor, Windsurf, and any MCP-compatible client.
Real-world benchmarks comparing code-graph-mcp tools against traditional approaches (Grep + Read + Glob) on a 33-file Rust project (~537 AST nodes).
| Scenario | Traditional | code-graph | Savings |
|---|---|---|---|
| Project architecture overview | 5-8 calls | 1 call (project_map) |
~85% |
| Find function by concept | 3-5 calls | 1 call (semantic_code_search) |
~75% |
| Trace 2-level call chain | 8-15 calls | 1 call (get_call_graph) |
~90% |
| Pre-change impact analysis | 10-20+ calls | 1 call (impact_analysis) |
~95% |
| Module structure & exports | 5+ calls | 1 call (module_overview) |
~80% |
| File dependency mapping | 3-5 calls | 1 call (dependency_graph) |
~75% |
| Similar code detection | N/A | 1 call (find_similar_code) |
unique |
| Metric | Without code-graph | With code-graph | Improvement |
|---|---|---|---|
| Tool calls per navigation task | ~6 | ~1.2 | ~80% fewer |
| Source lines read into context | ~8,000 lines | ~400 lines (structured) | ~95% less |
| Navigation token cost | ~36K tokens | ~7K tokens | ~80% saved |
| Full session token savings | — | — | 40-60% |
- Impact analysis — "Changing
connaffects 33 functions across 4 files, 78 tests at HIGH risk" — impossible to derive manually with Grep - Transitive call tracing — Follow
main→run_serve→handle_message→handle_tools_call→connin one query - Semantic search — Find
authenticate_sessionwhen searching "handle user login" - Dependency strength — Not just "file A imports file B", but "file A uses 38 symbols from file B"
| Use Case | Best Tool |
|---|---|
| Exact string / constant search | Grep |
| Reading a file to edit it | Read |
| Finding files by name pattern | Glob |
src/
├── mcp/ # MCP protocol layer (JSON-RPC, tool registry, server)
├── parser/ # Tree-sitter parsing, relation extraction, language support
├── indexer/ # 3-phase pipeline, Merkle tree, file watcher
├── storage/ # SQLite schema, CRUD, FTS5 full-text search
├── graph/ # Recursive CTE call graph queries
├── search/ # RRF fusion search combining BM25 + vector
├── embedding/ # Candle embedding model (optional)
├── sandbox/ # Context compressor with token estimation
└── utils/ # Language detection, config
Install as a Claude Code plugin for the best experience — includes slash commands, agents, skills, auto-indexing hooks, StatusLine health display, and automatic updates:
# Step 1: Add the marketplace
/plugin marketplace add sdsrss/code-graph-mcp
# Step 2: Install the plugin
/plugin install code-graph-mcpWhat you get:
- MCP Server — All code-graph tools available to Claude
- Slash Commands —
/understand <module>,/trace <route>,/impact <symbol> - Code Explorer Agent — Deep code understanding expert via
code-explorer - Auto-indexing Hook — Incremental index on every file edit (PostToolUse)
- StatusLine — Real-time health display (nodes, files, watch status) — compatible with other plugins' StatusLine via composite multiplexer
- Auto-update — Checks for new versions every 6h, updates silently
npm update -g @sdsrs/code-graphThen reconnect the MCP server in Claude Code with /mcp.
Note: Auto-update is disabled in the source repo directory (dev mode). Use manual update when developing the plugin itself.
Register as an MCP server without the plugin features:
claude mcp add code-graph-mcp -- npx -y @sdsrs/code-graphAdd to your MCP settings file (e.g. ~/.cursor/mcp.json):
{
"mcpServers": {
"code-graph": {
"command": "npx",
"args": ["-y", "@sdsrs/code-graph"]
}
}
}Run directly without installing:
npx -y @sdsrs/code-graphInstall globally, then run anywhere:
npm install -g @sdsrs/code-graph
code-graph-mcp# Uninstall the plugin
/plugin uninstall code-graph-mcp
# (Optional) Remove the marketplace
/plugin marketplace remove code-graph-mcp
# (Optional) Clean up all config and cache data
node ~/.claude/plugins/cache/code-graph-mcp/code-graph-mcp/*/scripts/lifecycle.js uninstallclaude mcp remove code-graph-mcpRemove the code-graph entry from your MCP settings file (e.g. ~/.cursor/mcp.json).
npm uninstall -g @sdsrs/code-graph| Tool | Description |
|---|---|
project_map |
Full project architecture: modules, dependencies, entry points, hot functions |
semantic_code_search |
Hybrid BM25 + vector + graph search for AST nodes |
get_call_graph |
Trace upstream/downstream call chains for a function |
trace_http_chain |
Full request flow: route → handler → downstream call chain |
impact_analysis |
Analyze the blast radius of changing a symbol |
module_overview |
High-level overview of a module's structure and exports |
dependency_graph |
Visualize dependency relationships between modules |
find_similar_code |
Find code snippets similar to a given pattern |
get_ast_node |
Extract a specific code symbol with signature, body, and relations |
Available when installed as a Claude Code plugin:
| Command | Description |
|---|---|
/understand <module> |
Deep dive into a module or file's architecture and relationships |
/trace <route> |
Trace a full HTTP request flow from route to data layer |
/impact <symbol> |
Analyze the impact scope of changing a symbol before modifying it |
/status |
Show code-graph index status and embedding progress |
/rebuild |
Force a full code-graph index rebuild |
TypeScript, JavaScript, Go, Python, Rust, Java, C, C++, HTML, CSS
Uses SQLite with:
- FTS5 for full-text search
- sqlite-vec extension for vector similarity search
- Merkle tree hashes for incremental change detection
Data is stored in .code-graph/index.db under the project root (auto-created, gitignored).
- Rust 1.75+ (2021 edition)
- A C compiler (for bundled SQLite / sqlite-vec)
# Default build (with local embedding model)
cargo build --release
# Without embedding model (lighter build)
cargo build --release --no-default-featuresAdd the compiled binary to your MCP settings:
{
"mcpServers": {
"code-graph": {
"command": "/path/to/target/release/code-graph-mcp"
}
}
}# Run tests
cargo test
# Run tests without embedding model
cargo test --no-default-features
# Check compilation
cargo checkSee LICENSE for details.