What should CodeGraph MCP understand next?

[raghurammrsd]

CodeGraph MCP is now publicly available, and I'm starting to build the next layer around real developer feedback.

CodeGraph MCP gives AI coding agents deterministic repository intelligence through MCP — including:

• Symbols and references
• Callers, callees, and execution paths
• Routes and framework relationships
• Database models, tables, and data relationships
• Tests and impact analysis
• Runtime evidence and static/runtime reconciliation
• Evidence-backed, token-bounded context

The core idea is:

The AI reasons. CodeGraph interrogates the repository.

I'm now interested in what developers think is still missing.

What should CodeGraph understand next?

For example:

• Dynamic Python / TypeScript behavior
• Large monorepo architecture
• Git branch freshness
• More database intelligence
• Runtime behavior
• CI/CD relationships
• Infrastructure / cloud configuration
• Better context selection for AI agents
• Something completely different

I'm especially interested in feedback from people using Claude Code, Cursor, Codex, Antigravity, Cline, or other MCP-enabled coding agents.

CodeGraph is open source:
👉 https://github.com/raghurammrsd/CODE_GRAPH_MCP

I'm using this discussion to collect ideas and real-world feedback for the next releases.
Drop your hardest repository-understanding problem below.

I'll use the strongest ideas to shape the next releases.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[1soka]

One thing I’d love to see is Git-aware repository intelligence, especially understanding how the architecture changes across branches and commits.
For example, an agent could ask:

• What changed structurally between main and my current branch?
• Which callers/tests/configs are affected by this change?
• Is the context CodeGraph is giving me still valid for the current HEAD?
• Did a function disappear, move, or change behavior recently?
  I think combining the existing symbol/call graph with Git history + change impact analysis could be extremely useful for coding agents, especially on large or fast-moving repositories.
  Another useful addition would be a confidence/evidence score so the agent can distinguish between relationships CodeGraph knows deterministically and relationships inferred from dynamic behavior.
  Really interesting project — the “AI reasons, CodeGraph interrogates the repository” separation makes a lot of sense.

[raghurammrsd]

Really appreciate this — a lot of what you described lines up closely with the direction I’m taking CodeGraph MCP.
CodeGraph already has Git impact analysis, so the next step I’m interested in is making that more Git-aware and freshness-aware: understanding changes between branches/commits, identifying affected callers/tests/configuration, and letting the agent know whether the context it received is still valid for the current HEAD.
I also like your point about evidence/confidence. CodeGraph already uses explicit states like FACT, UNKNOWN, POSSIBLE, AMBIGUOUS, and CONFLICT, and runtime reconciliation gives another layer of evidence. Extending that so an agent can clearly distinguish deterministically verified relationships from inferred or runtime-supported ones would be really useful.
Your examples like “what changed structurally between main and my branch?” and “what is affected by this change?” are exactly the kind of repository-level questions I want CodeGraph MCP to answer next.
Thanks for the detailed feedback — this is exactly the kind of direction I was hoping real users would help shape.

I really hope you get a chance to use CodeGraph MCP in your daily coding sessions. I’d genuinely love to hear how it performs on your real projects and what you think is still missing.

[raghurammrsd]

Hey 1soka — wanted to follow up on this because your suggestion directly influenced the latest CodeGraph MCP release.
v2.3.0 is now live with the Git Intelligence layer you described.
It now includes:

• Git-aware repository freshness
• Structural AST diffs across commits/branches
• Deep change-impact analysis across callers, routes, tests, and DB relationships
• Context freshness validation against the current HEAD
• Semantic pre-merge conflict detection
• Deterministic symbol history with explicit evidence states
  So questions like “what changed between my branch and main?”, “what is affected by this change?”, and “is my current context still valid?” are now first-class CodeGraph MCP queries.
  Your point about distinguishing deterministic evidence from inferred/runtime evidence also fits directly into the existing FACT / UNKNOWN / POSSIBLE / AMBIGUOUS / CONFLICT model.
  Really appreciate the suggestion — this was one of the most useful pieces of feedback I’ve received so far.
  I’d genuinely love for you to try v2.3.0 in your daily coding workflow and tell me where it still falls short.

[queenofcorgis]

Thanks for posting in the GitHub Community and sharing your project, @raghurammrsd !

We’ve moved your post to our Programming Help 🧑‍💻 category, which is more appropriate for this type of discussion.

Please review our guidelines about the Programming Help category for more information.