CSG - Code Structure with Graph
CSG is a local code intelligence tool for building a graph index of a source repository and exposing that index to AI coding agents through MCP.
It parses source code with deterministic AST tooling, stores symbols and relationships in an embedded Kuzu graph database, and provides MCP tools for code exploration, impact analysis, change review, and graph-aware navigation.
Install
uv tool install --python 3.12 --index-url https://pypi.org/simple --refresh code-knowledge-graph-tool
Upgrade later with:
uv tool upgrade code-knowledge-graph-tool
One-Time OpenAI Setup
Semantic embeddings use OpenAI embeddings. Configure your key once:
csg config set openai-api-key sk-your-openai-api-key
This key is stored in CSG's local user config and is reused by:
csg analyze --embeddingscsg watchcsg mcplaunched by Claude Code, Codex, or VS Code MCP clients
You can also use OPENAI_API_KEY or CSG_OPENAI_API_KEY as environment
overrides. If no key is configured, CSG still builds the graph and skips
embeddings with a clear reminder.
Basic Workflow
Run these commands from the repository you want to index:
cd /path/to/your/repo
csg analyze . --embeddings
csg setup .
csg analyze builds the local graph index. csg setup installs repo-local
agent guidance files and registers the CSG MCP server for supported agent CLIs.
To keep indexed repositories fresh while you work:
csg watch
To open the local web UI:
cd /path/to/your/repo
csg web --open
The browser UI runs at http://127.0.0.1:8080 by default and can upload,
analyze, and visualize repositories locally. If the directory where you launch
csg web has already been analyzed, the UI loads that graph automatically.
MCP Usage
After setup, AI agents can use CSG MCP tools automatically:
csg_list_repos: discover indexed repositoriescsg_explore: search and explore graph layerscsg_context: inspect a symbol with callers, callees, and source contextcsg_impact: check blast radius before editscsg_detect_changes: map git changes to affected symbols and flowscsg_rename: preview graph-aware symbol renamescsg_analyze: index a repository from the MCP client
Manual MCP registration is also possible:
claude mcp add --transport stdio --scope user csg -- csg mcp
codex mcp add csg -- csg mcp
MCP clients that use JSON configuration can launch:
{
"mcpServers": {
"csg": {
"command": "csg",
"args": ["mcp"]
}
}
}
Common Commands
csg analyze . # Build graph index
csg analyze . --force # Rebuild index
csg analyze . --embeddings # Build graph plus OpenAI embeddings
csg setup . # Install agent files and register MCP
csg setup-agents . # Install repo-local agent files only
csg status # Show index status for current repo
csg list # List indexed repositories
csg web --open # Start the local browser UI
csg watch # Watch indexed repos for changes
csg logs # Show MCP logs
csg clean # Delete current repo index
Data Storage
For normal local repositories, CSG stores graph data inside the target checkout:
<repo>/.csg/
meta.json
lbug/
cache/
A small global registry is also maintained so MCP clients can discover indexed repositories.
Notes
- Indexing does not require an LLM.
- Embeddings require an OpenAI key.
- No local PyTorch, CUDA, or Hugging Face embedding model is installed by the package.
- If embeddings are skipped, graph navigation, context, impact analysis, and BM25 search still work.
Metadata
Release files for code-knowledge-graph-tool 0.1.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| code_knowledge_graph_tool-0.1.15.tar.gz | 1.7 MB | Without provenance | Details for code_knowledge_graph_tool-0.1.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| code_knowledge_graph_tool-0.1.15-py3-none-any.whl | Python 3 | none | any | Details for code_knowledge_graph_tool-0.1.15-py3-none-any.whl |
Total release size: 2.7 MB
Release files / code_knowledge_graph_tool-0.1.15.tar.gz
| Download URL | code_knowledge_graph_tool-0.1.15.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c22ed7d33510419f3ba0699583c58675401bec39a2bbcd8489c4c79c6af848b1
|
|
BLAKE2b-256 checksum How to use checksums |
0f627c7968f8c1d46b1dc0fe7141bdc913f902465d17e97ef794d13cf6427e79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / code_knowledge_graph_tool-0.1.15-py3-none-any.whl
| Download URL | code_knowledge_graph_tool-0.1.15-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0545fc6fabf30dd45686ce314497b0f7eb55e7920145911fd3ee127ea57a689
|
|
BLAKE2b-256 checksum How to use checksums |
5faa93c4eff10bdcda1ac6d201ae6d0cfdd03bb1213f641fcbf43d81b5f3f571
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for code-knowledge-graph-tool 0.1.15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.