MCP Transports User Guide

These guides cover picking a transport for a server and configuring the HTTP ones for real deployment. Start with Getting started if you have not assigned a transport yet.

Guides

Guide	Scope	API starting points
Choosing a transport	The comparison and the two questions that settle it, STDIO and Named Pipe in detail, the client-side transports, writing a transport of your own, and error reporting, logging, and diagnostics.	`TTMSMCPTransport`, `TTMSMCPStdioTransport`, `TTMSMCPNamedPipeTransport`
HTTP transports	Streamable HTTP and SSE, session lifetime, TLS, reverse proxies and `PublicHost`, CORS, custom headers, and OAuth 2.1 bearer authentication.	`TTMSMCPStreamableHTTPTransport`, `TTMSMCPSseTransport`, `TTMSMCPAccessTokenValidation`

MCP Server owns the Transport property, and its session features only work on a transport that has sessions.
MCP Client is the other end, and selects a client transport from each server entry's transport type.
Authentication covers the deployment side: certificates on Windows, running as a service, and fronting with IIS.

See Also