From 1578e940dd6d57ba6190ef4589c53c01fd635cc3 Mon Sep 17 00:00:00 2001 From: Stephen Halter Date: Thu, 26 Feb 2026 16:23:09 -0800 Subject: [PATCH] Remove outdated README reference from transports.md (#1394) --- docs/concepts/transports/transports.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/concepts/transports/transports.md b/docs/concepts/transports/transports.md index 8ea3d78..31477c8 100644 --- a/docs/concepts/transports/transports.md +++ b/docs/concepts/transports/transports.md @@ -137,8 +137,6 @@ app.MapMcp("/mcp"); When using a custom route, Streamable HTTP clients should connect directly to that route (e.g., `https://host/mcp`), while SSE clients should connect to `{route}/sse` (e.g., `https://host/mcp/sse`). -See the `ModelContextProtocol.AspNetCore` package [README](https://github.com/modelcontextprotocol/csharp-sdk/blob/main/src/ModelContextProtocol.AspNetCore/README.md) for more configuration options. - ### SSE transport (legacy) The [SSE (Server-Sent Events)] transport is a legacy mechanism that uses unidirectional server-to-client streaming with a separate HTTP endpoint for client-to-server messages. New implementations should prefer Streamable HTTP.