Skip to content

Commit a72baf9

Browse files
Remove duplicated sample code
Co-authored-by: Stephen Halter <halter73@gmail.com>
1 parent 84c331d commit a72baf9

File tree

1 file changed

+0
-12
lines changed

1 file changed

+0
-12
lines changed

docs/concepts/transports/transports.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -159,18 +159,6 @@ SSE-specific configuration options:
159159

160160
The ASP.NET Core integration supports SSE transport alongside Streamable HTTP. The same `MapMcp()` endpoint handles both protocols — clients connecting with SSE are automatically served using the legacy SSE mechanism:
161161

162-
```csharp
163-
var builder = WebApplication.CreateBuilder(args);
164-
165-
builder.Services.AddMcpServer()
166-
.WithHttpTransport()
167-
.WithTools<MyTools>();
168-
169-
var app = builder.Build();
170-
app.MapMcp(); // Handles both Streamable HTTP and SSE clients
171-
app.Run();
172-
```
173-
174162
No additional configuration is needed. When a client connects using the SSE protocol, the server responds with an SSE stream for server-to-client messages and accepts client-to-server messages via a separate POST endpoint.
175163

176164
### Transport mode comparison

0 commit comments

Comments
 (0)