Skip to content

Commit be2fee8

Browse files
committed
Undo docs/*.md changes
1 parent 89fad07 commit be2fee8

File tree

3 files changed

+21
-21
lines changed

3 files changed

+21
-21
lines changed

docs/concepts/elicitation/elicitation.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ The **elicitation** feature allows servers to request additional information fro
1111

1212
### Server Support for Elicitation
1313

14-
Servers request structured data from users with the [ElicitAsync] extension method on [McpServer].
15-
The C# SDK registers an instance of [McpServer] with the dependency injection container,
16-
so tools can simply add a parameter of type [McpServer] to their method signature to access it.
14+
Servers request structured data from users with the [ElicitAsync] extension method on [IMcpServer].
15+
The C# SDK registers an instance of [IMcpServer] with the dependency injection container,
16+
so tools can simply add a parameter of type [IMcpServer] to their method signature to access it.
1717

1818
[ElicitAsync]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.McpServerExtensions.html#ModelContextProtocol_Server_McpServerExtensions_ElicitAsync_ModelContextProtocol_Server_IMcpServer_ModelContextProtocol_Protocol_ElicitRequestParams_System_Threading_CancellationToken_
19-
[McpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.McpServer.html
19+
[IMcpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.IMcpServer.html
2020

2121
The MCP Server must specify the schema of each input value it is requesting from the user.
2222
Only primitive types (string, number, boolean) are supported for elicitation requests.

docs/concepts/logging/logging.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -51,15 +51,15 @@ messages as there may not be an open connection to the client on which the log m
5151

5252
The C# SDK provides an extension method [WithSetLoggingLevelHandler] on [IMcpServerBuilder] to allow the
5353
server to perform any special logic it wants to perform when a client sets the logging level. However, the
54-
SDK already takes care of setting the [LoggingLevel] in the [McpServer], so most servers will not need to
54+
SDK already takes care of setting the [LoggingLevel] in the [IMcpServer], so most servers will not need to
5555
implement this.
5656

57-
[McpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.McpServer.html
57+
[IMcpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.IMcpServer.html
5858
[IMcpServerBuilder]: https://modelcontextprotocol.github.io/csharp-sdk/api/Microsoft.Extensions.DependencyInjection.IMcpServerBuilder.html
5959
[WithSetLoggingLevelHandler]: https://modelcontextprotocol.github.io/csharp-sdk/api/Microsoft.Extensions.DependencyInjection.McpServerBuilderExtensions.html#Microsoft_Extensions_DependencyInjection_McpServerBuilderExtensions_WithSetLoggingLevelHandler_Microsoft_Extensions_DependencyInjection_IMcpServerBuilder_System_Func_ModelContextProtocol_Server_RequestContext_ModelContextProtocol_Protocol_SetLevelRequestParams__System_Threading_CancellationToken_System_Threading_Tasks_ValueTask_ModelContextProtocol_Protocol_EmptyResult___
60-
[LoggingLevel]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.McpServer.html#ModelContextProtocol_Server_IMcpServer_LoggingLevel
60+
[LoggingLevel]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.IMcpServer.html#ModelContextProtocol_Server_IMcpServer_LoggingLevel
6161

62-
MCP Servers using the MCP C# SDK can obtain an [ILoggerProvider] from the McpServer [AsClientLoggerProvider] extension method,
62+
MCP Servers using the MCP C# SDK can obtain an [ILoggerProvider] from the IMcpServer [AsClientLoggerProvider] extension method,
6363
and from that can create an [ILogger] instance for logging messages that should be sent to the MCP client.
6464

6565
[!code-csharp[](samples/server/Tools/LoggingTools.cs?name=snippet_LoggingConfiguration)]
@@ -73,23 +73,23 @@ and from that can create an [ILogger] instance for logging messages that should
7373
When the server indicates that it supports logging, clients should configure
7474
the logging level to specify which messages the server should send to the client.
7575

76-
Clients should check if the server supports logging by checking the [Logging] property of the [ServerCapabilities] field of [McpClient].
76+
Clients should check if the server supports logging by checking the [Logging] property of the [ServerCapabilities] field of [IMcpClient].
7777

78-
[McpClient]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.McpClient.html
79-
[ServerCapabilities]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.McpClient.html#ModelContextProtocol_Client_McpClient_ServerCapabilities
78+
[IMcpClient]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.IMcpClient.html
79+
[ServerCapabilities]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.IMcpClient.html#ModelContextProtocol_Client_IMcpClient_ServerCapabilities
8080
[Logging]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Protocol.ServerCapabilities.html#ModelContextProtocol_Protocol_ServerCapabilities_Logging
8181

8282
[!code-csharp[](samples/client/Program.cs?name=snippet_LoggingCapabilities)]
8383

8484
If the server supports logging, the client should set the level of log messages it wishes to receive with
85-
the [SetLoggingLevel] method on [McpClient]. If the client does not set a logging level, the server might choose
85+
the [SetLoggingLevel] method on [IMcpClient]. If the client does not set a logging level, the server might choose
8686
to send all log messages or none -- this is not specified in the protocol -- so it is important that the client
8787
sets a logging level to ensure it receives the desired log messages and only those messages.
8888

8989
The `loggingLevel` set by the client is an MCP logging level.
9090
See the [Logging Levels](#logging-levels) section above for the mapping between MCP and .NET logging levels.
9191

92-
[SetLoggingLevel]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.McpClientExtensions.html#ModelContextProtocol_Client_McpClientExtensions_SetLoggingLevel_ModelContextProtocol_Client_McpClient_Microsoft_Extensions_Logging_LogLevel_System_Threading_CancellationToken_
92+
[SetLoggingLevel]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.McpClientExtensions.html#ModelContextProtocol_Client_McpClientExtensions_SetLoggingLevel_ModelContextProtocol_Client_IMcpClient_Microsoft_Extensions_Logging_LogLevel_System_Threading_CancellationToken_
9393

9494
[!code-csharp[](samples/client/Program.cs?name=snippet_LoggingLevel)]
9595

docs/concepts/progress/progress.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,14 @@ This project illustrates the common case of a server tool that performs a long-r
1717

1818
### Server Implementation
1919

20-
When processing a request, the server can use the [sendNotificationAsync] extension method of [McpServer] to send progress updates,
20+
When processing a request, the server can use the [sendNotificationAsync] extension method of [IMcpServer] to send progress updates,
2121
specifying `"notifications/progress"` as the notification method name.
22-
The C# SDK registers an instance of [McpServer] with the dependency injection container,
23-
so tools can simply add a parameter of type [McpServer] to their method signature to access it.
22+
The C# SDK registers an instance of [IMcpServer] with the dependency injection container,
23+
so tools can simply add a parameter of type [IMcpServer] to their method signature to access it.
2424
The parameters passed to [sendNotificationAsync] should be an instance of [ProgressNotificationParams], which includes the current progress, total steps, and an optional message.
2525

26-
[sendNotificationAsync]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.McpEndpointExtensions.html#ModelContextProtocol_McpEndpointExtensions_SendNotificationAsync_ModelContextProtocol_McpSession_System_String_System_Threading_CancellationToken_
27-
[McpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.McpServer.html
26+
[sendNotificationAsync]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.McpEndpointExtensions.html#ModelContextProtocol_McpEndpointExtensions_SendNotificationAsync_ModelContextProtocol_IMcpEndpoint_System_String_System_Threading_CancellationToken_
27+
[IMcpServer]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Server.IMcpServer.html
2828
[ProgressNotificationParams]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Protocol.ProgressNotificationParams.html
2929

3030
The server must verify that the caller provided a `progressToken` in the request and include it in the call to [sendNotificationAsync]. The following example demonstrates how a server can send a progress notification:
@@ -38,10 +38,10 @@ Note that servers are not required to support progress tracking, so clients shou
3838

3939
In the MCP C# SDK, clients can specify a `progressToken` in the request parameters when calling a tool method.
4040
The client should also provide a notification handler to process "notifications/progress" notifications.
41-
There are two way to do this. The first is to register a notification handler using the [RegisterNotificationHandler] method on the [McpClient] instance. A handler registered this way will receive all progress notifications sent by the server.
41+
There are two way to do this. The first is to register a notification handler using the [RegisterNotificationHandler] method on the [IMcpClient] instance. A handler registered this way will receive all progress notifications sent by the server.
4242

43-
[McpClient]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.McpClient.html
44-
[RegisterNotificationHandler]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.McpSession.html#ModelContextProtocol_McpSession_RegisterNotificationHandler_System_String_System_Func_ModelContextProtocol_Protocol_JsonRpcNotification_System_Threading_CancellationToken_System_Threading_Tasks_ValueTask__
43+
[IMcpClient]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.Client.IMcpClient.html
44+
[RegisterNotificationHandler]: https://modelcontextprotocol.github.io/csharp-sdk/api/ModelContextProtocol.IMcpEndpoint.html#ModelContextProtocol_IMcpEndpoint_RegisterNotificationHandler_System_String_System_Func_ModelContextProtocol_Protocol_JsonRpcNotification_System_Threading_CancellationToken_System_Threading_Tasks_ValueTask__
4545

4646
```csharp
4747
mcpClient.RegisterNotificationHandler(NotificationMethods.ProgressNotification,

0 commit comments

Comments
 (0)