Overview
Transport errors are thrown by the MCP transport layer — the component responsible for managing HTTP connections, sessions, and message framing. Most are internal errors exceptUnsupportedContentTypeError, which is a client-facing 400 error.
Error Reference
MethodNotImplementedError
Thrown when calling an abstract or placeholder method that has not been implemented.UnsupportedTransportTypeError
Thrown when an unsupported transport type is specified in configuration.TransportBusRequiredError
Thrown when a transport bus is required but not provided.InvalidTransportSessionError
Thrown when a transport session is invalid or missing.TransportNotConnectedError
Thrown when an operation is attempted on a transport that is not connected.TransportAlreadyStartedError
Thrown when attempting to start a transport that is already running.UnsupportedContentTypeError
Thrown when a request uses an unsupportedContent-Type header. This is a public error since it represents a client-side issue.