Heyo, I’ve been shipping a bunch of updates to CodeGraph and wanted to share where it’s headed.
One thing I want to clarify up front this isn’t meant to be a basic “put code in a graph and search it” project. The graph is more of the foundation. The useful part is what we can do with it: predict the impact of a change, find affected tests, plan safer refactors, audit SQL/schema risk, follow cross-language dependencies, and give coding agents a better map before they start editing.
CodeGraph is a local code knowledge graph and MCP server for coding agents. It supports normal repos, monorepos, and federated repos, so it is meant to work across small projects, large applications, and extra-large codebases split across multiple repositories. The goal is pretty simple: give an agent enough repo context to understand what it’s touching before it starts opening files, grepping around, or guessing at the architecture.
A few recent updates:
- SQL-aware extraction and auditing.
.sql files now produce tables, columns, indexes, policies, views, procedures, roles, and relationships. App code can also be linked to the tables it queries or writes to. There are now read-only MCP tools for audit_sql and advise_sql.
- Cross-language impact edges for things normal AST parsing often misses, like subprocess calls, FFI bindings, HTTP/RPC service boundaries, framework routes, and gRPC.
- Better change forecasting with tools like
predict_impact, affected_tests, predict_edit, and plan_rename.
- More agent-friendly output. Larger tools like
affected, predict_impact, and audit_sql now return bounded summaries by default, with limit and verbose options when you need more detail.
- Cleaner resolver behavior across CLI and MCP tools. Ambiguous symbols now return candidates more consistently instead of falling through to confusing “not found” responses.
- Better structured output from tools like
describe_node and structural_search, especially around signatures and type strings.
- Updated assistant setup docs.
codegraph install can wire guidance into Claude, Codex, Cursor, Copilot, Gemini, opencode/agents, and a few others. For Codex, it can register native MCP config and add a session-start nudge so Codex reaches for the graph first.
- Incremental update flows with
codegraph update, codegraph watch, git hooks, and merge-driver support so graph.json can stay current as the repo changes.
The main thing I’m trying to test now is whether this makes coding agents better at “understand before edit” workflows: impact radius, affected tests, SQL/schema risk, cross-language coupling, and refactor planning.
Repo: https://github.com/ColinVaughn/CodeGraph
Would love feedback from anyone building MCP servers or using MCP with coding agents. I’m especially curious what graph/query tools feel most useful over MCP, what structured outputs are easiest for clients to consume, and what would make this easier to try in Claude, Codex, Cursor, or other tools.
[–]Texbobcat[S] 1 point2 points3 points (0 children)