// Use CodeGraphContext (CGC) to index a repo into a graph DB and query it via CLI or MCP. Apply when the user wants semantic/code-graph search, call graphs, indexing, or configuring the codegraphcontext MCP server.
| name | codegraphcontext |
| description | Use CodeGraphContext (CGC) to index a repo into a graph DB and query it via CLI or MCP. Apply when the user wants semantic/code-graph search, call graphs, indexing, or configuring the codegraphcontext MCP server. |
cgc, choose a database backend, or wire MCP into an editor.codegraph_find_code, analyze_code_relationships, add_code_to_graph, etc.pip install codegraphcontext (or pipx install codegraphcontext). With uv, uv tool install codegraphcontext or uvx codegraphcontext … is supported; if a parser fails with ModuleNotFoundError: tree_sitter_c_sharp, run with an explicit extra package, e.g. uvx --with tree-sitter-c-sharp codegraphcontext ….~/.codegraphcontext/.env for DEFAULT_DATABASE, Neo4j URI, or Kùzu path. Run cgc doctor if connections fail.cgc index . (or cgc index --force . to rebuild). Ensure CLI and MCP use the same config so they see the same graph.cgc find, cgc query, …) or MCP tools after cgc mcp setup / cgc mcp start in the client config.cgc mcp setup and pick the editor, or add a server entry that runs cgc with args mcp start and the same env as the CLI.cgc with arguments mcp, start (same as other editors). Official OpenCode MCP overview: OpenCode MCP servers.Repository.path is missing in the DB, that row is skipped for path checks and a warning is logged when repositories are listed; suggest cleaning stale Repository nodes (see Neo4j example in logs) if it keeps happening.codegraphcontext.cli.maincodegraphcontext.server, tool_definitions.pydocs/docs/setup_workflows.md, docs/docs/guides/mcp_guide.mddocs/docs/agent_skill_codegraphcontext.md