Skip to content

Commit 6dd7a5c

Browse files
halter73Copilot
andcommitted
Update InMemoryTransport link to pinned lines
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 5737a99 commit 6dd7a5c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/concepts/sessions/sessions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@ The stdio transport creates a single server for the lifetime of the process. The
335335

336336
#### McpServer.Create (custom transports)
337337

338-
When you create a server directly with <xref:ModelContextProtocol.Server.McpServer.Create*>, you control the `IServiceProvider` and transport yourself. If you pass an already-scoped provider, you can set <xref:ModelContextProtocol.Server.McpServerOptions.ScopeRequests> to `false` to avoid creating redundant nested scopes. The [InMemoryTransport sample](https://github.com/modelcontextprotocol/csharp-sdk/tree/main/samples/InMemoryTransport) shows a minimal example of using `McpServer.Create` with in-memory pipes:
338+
When you create a server directly with <xref:ModelContextProtocol.Server.McpServer.Create*>, you control the `IServiceProvider` and transport yourself. If you pass an already-scoped provider, you can set <xref:ModelContextProtocol.Server.McpServerOptions.ScopeRequests> to `false` to avoid creating redundant nested scopes. The [InMemoryTransport sample](https://github.com/modelcontextprotocol/csharp-sdk/blob/51a4fde4d9cfa12ef9430deef7daeaac36625be8/samples/InMemoryTransport/Program.cs#L6-L14) shows a minimal example of using `McpServer.Create` with in-memory pipes:
339339

340340
```csharp
341341
Pipe clientToServerPipe = new(), serverToClientPipe = new();

0 commit comments

Comments
 (0)