Timeline for stable release and production readiness #744
-
|
Hello, I have noticed that the C# MCP SDK is currently in preview. Is there any timeline or roadmap for when the project will reach a stable release? Additionally, is it considered safe to use the SDK in production environments at this stage, or are there known risks and limitations? P.S Thank you for your guidance! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
We have no clear timeline defined for the moment, since the underlying MCP specification itself is still not stable. While we strive to ensure that the SDK faithfully implements the most recent version of the specification, the specification itself is still subject to breaking changes. |
Beta Was this translation helpful? Give feedback.
-
|
Until then I suggest that in organizations that do not allow the use of preview libraries for production code (I'm in one), there are usually ways to request temporary exemptions, and to make use of such. The SDK isn't in preview because of lacking quality, security, or other similar concerns (my personal opinion, not an authoritative judgement) - and often there are ways to mark your own versions accordingly. But I empathize with those who're facing red tape because of the preview status - it does seem unfair that using one of the other SDKs which have chosen not to go with similar versioning - gets one off the hook but this one requires exemptions. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in a similar company, which is why I'm asking this question. 😄 It's important to me that the SDK implements the current MCP specification stably. Agree with you @PederHP, The instability of the MCP specification itself does not make the SDKz unstable for use. Thank you guys for our response. |
Beta Was this translation helpful? Give feedback.
Until then I suggest that in organizations that do not allow the use of preview libraries for production code (I'm in one), there are usually ways to request temporary exemptions, and to make use of such. The SDK isn't in preview because of lacking quality, security, or other similar concerns (my personal opinion, not an authoritative judgement) - and often there are ways to mark your own versions accordingly. But I empathize with those who're facing red tape because of the preview status - it does seem unfair that using one of the other SDKs which have chosen not to go with similar versioning - gets one off the hook but this one requires exemptions.