- This also paves the way for better multi-session support - We should definitely rethink names for the transport API - For now, I kept the names similar as possible, so we can focus on the API shape Co-authored-by: Stephen Toub <stoub@microsoft.com>
14 lines
661 B
C#
14 lines
661 B
C#
namespace ModelContextProtocol.Protocol.Transport;
|
|
|
|
/// <summary>
|
|
/// Represents a transport mechanism for MCP communication (from the server).
|
|
/// </summary>
|
|
public interface IServerTransport
|
|
{
|
|
/// <summary>
|
|
/// Asynchronously accepts a transport session initiated by an MCP client and returns an interface for the duplex JSON-RPC message stream.
|
|
/// </summary>
|
|
/// <param name="cancellationToken">Used to signal the cancellation of the asynchronous operation.</param>
|
|
/// <returns>Returns an interface for the duplex JSON-RPC message stream.</returns>
|
|
Task<ITransport?> AcceptAsync(CancellationToken cancellationToken = default);
|
|
}
|