Augment conceptual docs with Docker-based MCP server deployment guidance (#1423)
Add a Docker deployment guide for ASP.NET Core MCP servers using Streamable HTTP (docs/concepts/deployment/docker.md), a Deployment/Docker entry in the conceptual nav (toc.yml, index.md), and cross-links from the transports and getting-started guides.
This commit is contained in:
parent
0d34048e5f
commit
71d7eead40
1 changed files with 125 additions and 1 deletions
|
|
@ -261,6 +261,8 @@ 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 (when [legacy SSE is enabled](xref:stateless#legacy-sse-transport)) should connect to `{route}/sse` (e.g., `https://host/mcp/sse`).
|
||||
|
||||
For containerized deployments of ASP.NET Core servers, see [Docker deployment](../deployment/docker.md).
|
||||
|
||||
### 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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue