The ModelContextProtocol specification continues to evolve rapidly, and it’s important for the C# SDK to remain current with specification additions and updates. All NuGet packages follow Semantic Versioning 2.0.0.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/modelcontextprotocol/csharp-sdk/llms.txt
Use this file to discover all available pages before exploring further.
Semantic Versioning
Given a version number MAJOR.MINOR.PATCH, the package versions increment the:- MAJOR version when incompatible API changes are included
- MINOR version when functionality is added in a backward-compatible manner
- PATCH version when backward-compatible bug fixes are included
A prerelease version indicates that the version is unstable and might not satisfy the intended compatibility requirements.
Supported Versions
Beginning with the 1.0.0 release, the following support policy applies for the official C# ModelContextProtocol SDK packages:New Functionality
New functionality and additive APIs will be introduced in MINOR releases within the current MAJOR version only.Bug Fixes
Bugs will be fixed in either:- A PATCH release against the latest MAJOR.MINOR version within the latest MAJOR version only
- A MINOR release against the latest MAJOR version within the latest MAJOR version only
Critical Bug Fixes
Bugs deemed by the maintainers to be critical or blocking will be fixed in both:- A PATCH release against the latest MAJOR version, within its latest MAJOR.MINOR version
- A PATCH release against one previous MAJOR version, within its latest MAJOR.MINOR version
Experimental APIs
MAJOR or MINOR version updates might introduce or alter APIs annotated as[Experimental]. This attribute indicates that an API is experimental and might change at any time—including within PATCH or MINOR version updates.
Experimental APIs require suppression of diagnostic codes specific to the MCP SDK APIs, using an MCP prefix.
See the Experimental APIs documentation for details on working with experimental features.
Breaking Changes
Before 1.0.0
Prior to the release of a stable 1.0.0 set of NuGet packages, the SDK remains in preview and breaking changes can be introduced without prior notice.After 1.0.0
The SDK follows Semantic Versioning and breaking changes against stable releases require increments to the MAJOR version. If feasible, the SDK will support all versions of the MCP spec. However, if breaking changes to the spec make this infeasible, preference will be given to the most recent version of the MCP spec. This would be considered a breaking change necessitating a new MAJOR version.Specification Schema Changes
If the MCP specification changes the schema for JSON payloads, the C# SDK might use theMcpSession.NegotiatedProtocolVersion to dynamically change the payload schema, potentially using internal data transfer objects (DTOs) to achieve the needed deserialization behavior.
These techniques will be applied where feasible to maintain backward-compatibility and forward-compatibility between MCP specification versions.
Prototypes
For illustrations of how this could be achieved, see the following prototypes:- Support multiple contents in sampling results
- Support multiple contents in sampling results (using DTOs)
Obsolete APIs
If APIs within the SDK become obsolete due to changes in the MCP spec or other evolution of the SDK’s APIs, the[Obsolete] attribute will be applied to the affected APIs.
Deprecation Process
Within a MINOR version update
Within a MINOR version update
APIs might be marked as
[Obsolete] to produce build warnings while the API remains functional. The build warnings will provide guidance specific to the affected APIs.Within a MAJOR version update (errors)
Within a MAJOR version update (errors)
APIs might be marked as
[Obsolete] to produce build errors indicating the API is no longer functional and always throws exceptions. The build errors will provide guidance specific to the affected APIs.Within a MAJOR version update (removal)
Within a MAJOR version update (removal)
Obsolete APIs might be removed. API removals are expected to be rare and avoided wherever possible, and
[Obsolete] attributes will be applied ahead of the API removal.Beginning with the 1.0.0 release, all obsoletions will use diagnostic codes specific to the MCP SDK APIs, using an
MCP prefix.Next Steps
- Learn about experimental APIs
- Check the roadmap for planned changes
- View release notes on GitHub