Official .NET / C# SDK for ACP?

[gimmickj]

Hi ACP maintainers,

I'm a .NET developer looking at integrating ACP into the Microsoft Agent Framework (MAF) / ASP.NET Core ecosystem. ACP has official SDKs for Rust, TypeScript, Python, Kotlin and Java, but I couldn't find an official C#/.NET one. A few questions:

1. Is there a plan or roadmap item for an official .NET SDK?
2. Would the team welcome a community C# implementation? Following the PHP/Swift threads, is the path still: community SDK -> listed on the community libraries page -> official if it gains adoption and maintainers?
3. Which artifacts should a .NET SDK build against: the published JSON Schema (schema/v1/schema.json, schema.unstable.json) and meta.json, or is there other guidance beyond CONTRIBUTING.md? Is agentclientprotocol/acp-tck the recommended conformance check for agent-side implementations?
4. Would you recommend starting client-side, agent-side, or both? Any preference on transport scope (stdio first vs. WebSocket too) or how to track protocol versioning?

I'd be glad to build and maintain a .NET SDK if the team is open to it, starting as a community library and following whatever process you prefer. I believe an official .NET SDK would make ACP much easier to adopt in ASP.NET Core services and agent frameworks such as MAF.

Thanks!

[benbrandt]

Yes feel free to make one and submit it to the docs!

[gimmickj]

Thanks Ben, that matches what I expected from the PHP/Swift threads.

To be upfront about my own capacity: I was mainly trying to understand the official stance and whether a .NET SDK is on the roadmap, and I can't commit to authoring and maintaining a full SDK on my own right now, so I don't want to over-promise here.

Two follow-ups:

• Is anyone in the community already working on a C#/.NET implementation? If so, I'd be glad to test it against Microsoft Agent Framework / ASP.NET Core and give feedback.
• If not, would it make sense to leave this thread open as a pointer for whoever picks it up? I'm happy to help with review, test scenarios and docs once someone starts.

Either way, thanks for confirming the community-library path.