using ModelContextProtocol.Protocol;
using System.Security.Claims;
using System.Threading.Channels;
namespace ModelContextProtocol.Server;
///
/// Provides an implementation using Server-Sent Events (SSE) for server-to-client communication.
///
///
///
/// This transport provides one-way communication from server to client using the SSE protocol over HTTP,
/// while receiving client messages through a separate mechanism. It writes messages as
/// SSE events to a response stream, typically associated with an HTTP response.
///
///
/// This transport is used in scenarios where the server needs to push messages to the client in real-time,
/// such as when streaming completion results or providing progress updates during long-running operations.
///
///
/// The response stream to write MCP JSON-RPC messages as SSE events to.
///
/// The relative or absolute URI the client should use to post MCP JSON-RPC messages for this session.
/// These messages should be passed to .
/// Defaults to "/message".
///
/// The identifier corresponding to the current MCP session.
public sealed class SseResponseStreamTransport(Stream sseResponseStream, string? messageEndpoint = "/message", string? sessionId = null) : ITransport
{
private readonly SseWriter _sseWriter = new(messageEndpoint);
private readonly Channel _incomingChannel = Channel.CreateBounded(new BoundedChannelOptions(1)
{
SingleReader = true,
SingleWriter = false,
});
private bool _isConnected;
///
/// Starts the transport and writes the JSON-RPC messages sent via
/// to the SSE response stream until cancellation is requested or the transport is disposed.
///
/// The to monitor for cancellation requests. The default is .
/// A task representing the send loop that writes JSON-RPC messages to the SSE response stream.
public async Task RunAsync(CancellationToken cancellationToken = default)
{
_isConnected = true;
await _sseWriter.WriteAllAsync(sseResponseStream, cancellationToken).ConfigureAwait(false);
}
///
public ChannelReader MessageReader => _incomingChannel.Reader;
///
public string? SessionId { get; } = sessionId;
///
public async ValueTask DisposeAsync()
{
_isConnected = false;
_incomingChannel.Writer.TryComplete();
await _sseWriter.DisposeAsync().ConfigureAwait(false);
}
///
public async Task SendMessageAsync(JsonRpcMessage message, CancellationToken cancellationToken = default)
{
Throw.IfNull(message);
// If the underlying writer has been disposed, just drop the message.
await _sseWriter.SendMessageAsync(message, cancellationToken).ConfigureAwait(false);
}
///
/// Handles incoming JSON-RPC messages received on the /message endpoint.
///
/// The JSON-RPC message received from the client.
/// The to monitor for cancellation requests. The default is .
/// A task representing the asynchronous operation to buffer the JSON-RPC message for processing.
/// is .
/// There is an attempt to process a message before calling .
///
///
/// This method is the entry point for processing client-to-server communication in the SSE transport model.
/// While the SSE protocol itself is unidirectional (server to client), this method allows bidirectional
/// communication by handling HTTP POST requests sent to the message endpoint.
///
///
/// When a client sends a JSON-RPC message to the /message endpoint, the server calls this method to
/// process the message and make it available to the MCP server via the channel.
///
///
/// If an authenticated sent the message, that can be included in the .
/// No other part of the context should be set.
///
///
public async Task OnMessageReceivedAsync(JsonRpcMessage message, CancellationToken cancellationToken = default)
{
Throw.IfNull(message);
if (!_isConnected)
{
throw new InvalidOperationException($"Transport is not connected. Make sure to call {nameof(RunAsync)} first.");
}
await _incomingChannel.Writer.WriteAsync(message, cancellationToken).ConfigureAwait(false);
}
}