modelcontextprotocol/csharp-sdk
Watch
1
0
Fork
You've already forked csharp-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

Add 2025-11-25 as supported version (#1130)

Browse source 
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: stephentoub <2642209+stephentoub@users.noreply.github.com>
This commit is contained in:
Copilot 2026-01-15 09:59:42 -05:00 • committed by GitHub
commit 774411b22c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 28 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/concepts/elicitation/samples/server/Elicitation.http
View file

@ -5,7 +5,7 @@
POST {{HostAddress}}/
Accept: application/json, text/event-stream
Content-Type: application/json
MCP-Protocol-Version: 2025-06-18
MCP-Protocol-Version: 2025-11-25
{
"jsonrpc": "2.0",
@ -34,7 +34,7 @@ Content-Type: application/json
"capabilities": {
"elicitation": {}
},
"protocolVersion": "2025-06-18"
"protocolVersion": "2025-11-25"
}
}
@ -46,7 +46,7 @@ POST {{HostAddress}}/
Accept: application/json, text/event-stream
Content-Type: application/json
Mcp-Session-Id: {{SessionId}}
MCP-Protocol-Version: 2025-06-18
MCP-Protocol-Version: 2025-11-25
{
"jsonrpc": "2.0",

2
docs/concepts/httpcontext/samples/HttpContext.http
View file

@ -3,7 +3,7 @@
POST {{HostAddress}}/
Accept: application/json, text/event-stream
Content-Type: application/json
MCP-Protocol-Version: 2025-06-18
MCP-Protocol-Version: 2025-11-25
{
"jsonrpc": "2.0",

4
docs/concepts/logging/logging.md
View file

@ -9,7 +9,7 @@ uid: logging
MCP servers can expose log messages to clients through the [Logging utility].
[Logging utility]: https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/logging
[Logging utility]: https://modelcontextprotocol.io/specification/2025-11-25/server/utilities/logging
This document describes how to implement logging in MCP servers and how clients can consume log messages.
@ -43,7 +43,7 @@ dropped when sending messages to the client.
MCP servers that implement the Logging utility must declare this in the capabilities sent in the
[Initialization] phase at the beginning of the MCP session.
[Initialization]: https://modelcontextprotocol.io/specification/2025-06-18/basic/lifecycle#initialization
[Initialization]: https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle#initialization
Servers built with the C# SDK always declare the logging capability. Doing so does not obligate the server
to send log messages&mdash;only allows it. Note that stateless MCP servers might not be capable of sending log

4
docs/concepts/logging/samples/server/Logging.http
View file

@ -14,7 +14,7 @@ Content-Type: application/json
"version": "0.1.0"
},
"capabilities": {},
"protocolVersion": "2025-06-18"
"protocolVersion": "2025-11-25"
}
}
@ -27,7 +27,7 @@ Content-Type: application/json
POST {{HostAddress}}/
Accept: application/json, text/event-stream
Content-Type: application/json
MCP-Protocol-Version: 2025-06-18
MCP-Protocol-Version: 2025-11-25
Mcp-Session-Id: {{SessionId}}
{

2
docs/concepts/progress/progress.md
View file

@ -9,7 +9,7 @@ uid: progress
The Model Context Protocol (MCP) supports [progress tracking] for long-running operations through notification messages.
[progress tracking]: https://modelcontextprotocol.io/specification/2025-06-18/basic/utilities/progress
[progress tracking]: https://modelcontextprotocol.io/specification/2025-11-25/basic/utilities/progress
Typically progress tracking is supported by server tools that perform operations that take a significant amount of time to complete, such as image generation or complex calculations.
However, progress tracking is defined in the MCP specification as a general feature that can be implemented for any request that's handled by either a server or a client.

2
docs/concepts/progress/samples/server/Progress.http
View file

@ -3,7 +3,7 @@
POST {{HostAddress}}/
Accept: application/json, text/event-stream
Content-Type: application/json
MCP-Protocol-Version: 2025-06-18
MCP-Protocol-Version: 2025-11-25
{
"jsonrpc": "2.0",