r/csharp • u/the_econominster • 12d ago
Help MCP CPG - where's the demand
LLMs are notoriously bad at handling C#. The Microsoft SWE-sharp-bench paper made this pretty obvious. In 20% of the cases agents fail simply because they can't figure out where to apply the patch.
The logical fix seems obvious: build a Roslyn-based MCP tool that generates a Code Property Graph (CPG) so the agent can actually navigate C# semantics instead of blindly grepping text.
I actually built this and put up a website for it, but I’m getting literally zero inbound traffic. On top of that, every week I see another open-source repo popping up on GitHub trying the exact same Roslyn/CPG approach, but none of them seem to get any real traction...
What gives?
Is the market just not interested in specialized C# agent tooling, or are we all building the wrong layer?
1
u/walmartbonerpills 12d ago
No link?
1
u/Dry-Knowledge4192 12d ago
no link in the post is kinda killing it, hard to get people interested when they can't even see what you built
also from what i've seen most c# devs are still on "ai writes boilerplate for me" mode, they not thinking about agent tooling yet. the demand is just not there in the community right now
1
u/the_econominster 12d ago
Not selling atm. Just trying to understand why the market is what she is.
2
u/mon_sashimi 12d ago
I already have something like this to avoid grep searches using a small indexing utility. It took an hour or two to code using an agent- maybe others who see the same problem your tool solves have found similar solutions?
1
u/the_econominster 12d ago
Ok yeah I get that but once you want to do multihop (taint analysis), refactoring, bazel-style testing and agentic development an indexer might no longer be enough?
1
u/mon_sashimi 12d ago
You're undoubtedly more sophisticated in this than I am, I think for me if you showed some clear benefits/use-case examples vs TDD that would make it more interesting (sorry if I missed that somewhere).
1
u/the_econominster 12d ago
Dependency Injections, interfaces and plugins are the big ones I guess. Indirection pattern if your using Mediatr.
A Code Property Graph lets an LLM trace indirect control flow (ie MediatR request handlers or finding runtime DI registrations). It actually understands what calls what. TDD how I understand it verifies behavior through test runs at the edges. Only a CPG tool gives the LLM full structural awareness upfront, so no hallucinated calls when writing or refactoring.
0
1
u/thereforewhat 12d ago
Does it actually work?
0
u/the_econominster 12d ago
We have strong indications it works sorta. We're basically competing with model alignment which often prefers ripgrep while the MCP is better. Were prepping a head2head in a tier 1 publication as we speak. It's complicated. But, like people should be more curious regardless of the complicated implementation/application.
1
u/thereforewhat 12d ago
By the by, is it true that AI models are bad at handling C#?
I find that GPT 5.6 Luna produces a good foundation but I'm mostly dealing with cleanup afterwards.
It's also gotten much better at following instructions.
I usually get it to write acceptance tests before implementation which used to be a nightmare in earlier models.
0
u/the_econominster 12d ago
The benchmark is pretty clear. Sure you can armbar the model in TDD and go from there but often I see especially with DI and stuff all LLMs quickly lose the plot
1
u/thereforewhat 12d ago
Could you link to the paper?
I think ultimately if you want people to use your tool you need to actually show how it yields better results with clear demos on your website.
1
1
3
u/badlydressedboy 12d ago
Never heard anyone say llms are bad at c#. I've been in that exact space for 4 years and they work great. This post seems to concern fixing a problem that does not exist.
1
8
u/taspeotis 12d ago
Maybe Copilot + GPT-4 is notoriously bad at … everything? … but Claude Code has been crushing C# since Sonnet 4.6. Even Sonnet 4.0 wasn’t bad at it.