Skip to main content

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 except UnsupportedContentTypeError, which is a client-facing 400 error.

Error Reference

MethodNotImplementedError

Thrown when calling an abstract or placeholder method that has not been implemented.
Example:

UnsupportedTransportTypeError

Thrown when an unsupported transport type is specified in configuration.
Example:

TransportBusRequiredError

Thrown when a transport bus is required but not provided.

InvalidTransportSessionError

Thrown when a transport session is invalid or missing.
Example:

TransportNotConnectedError

Thrown when an operation is attempted on a transport that is not connected.
Example:

TransportAlreadyStartedError

Thrown when attempting to start a transport that is already running.

UnsupportedContentTypeError

Thrown when a request uses an unsupported Content-Type header. This is a public error since it represents a client-side issue.
Example:

TransportServiceNotAvailableError

Thrown when the transport service is requested but not registered (typically a misconfigured server bootstrap).

SessionClaimConflictError

Thrown in HA deployments when another pod claims an active session ID. The local pod must drop its in-memory state for that session.