Overview
Remote errors are thrown when interacting with remote MCP servers via the@App() decorator’s remote app configuration. They cover connection failures, timeouts, not-found resources, auth issues, execution failures, transport problems, capability mismatches, configuration errors, and retry validation.
Connection Errors
RemoteConnectionError
Thrown when the initial connection to a remote MCP server fails.RemoteDisconnectError
Thrown when a remote MCP server disconnects unexpectedly.Timeout Errors
RemoteTimeoutError
Thrown when a remote MCP operation exceeds the configured timeout.Not Found Errors
RemoteToolNotFoundError
Thrown when a tool is not found on the remote server.RemoteResourceNotFoundError
Thrown when a resource is not found on the remote server.RemotePromptNotFoundError
Thrown when a prompt is not found on the remote server.Auth Errors
RemoteAuthError
Thrown when authentication to a remote server fails (missing credentials).RemoteAuthorizationError
Thrown when authorization to a remote resource/tool fails (insufficient credentials).Execution Errors
RemoteToolExecutionError
Thrown when a remote tool execution fails.RemoteResourceReadError
Thrown when reading a remote resource fails.RemotePromptGetError
Thrown when getting a remote prompt fails.Transport Errors
RemoteTransportError
Thrown when transport initialization fails for a remote app.RemoteUnsupportedTransportError
Thrown when an unsupported transport type is specified for a remote app.Capability Errors
RemoteCapabilityDiscoveryError
Thrown when capability discovery fails for a remote server.RemoteCapabilityNotSupportedError
Thrown when a remote server doesn’t support a required capability.Configuration Errors
RemoteConfigurationError
Thrown when a remote app’s configuration is invalid.RemoteNotConnectedError
Thrown when an operation is attempted on a remote app that is not connected.Retry Errors
InvalidRetryOptionsError
Thrown when retry configuration is invalid (e.g.,maxAttempts < 1).