Overview
Elicitation errors are thrown during the MCP elicitation flow — the mechanism that allows tools to request additional user input during execution. These errors cover unsupported clients, timeouts, fallback flows, store initialization, encryption failures, and subscription issues.Error Reference
ElicitationNotSupportedError
Thrown when attempting to elicit from a client that does not support elicitation or when the transport is unavailable.sendElicitationResult call could be matched to that caller.
ElicitationNotOwnedError
Thrown bysendElicitationResult when the caller answering is not the one the elicitation was asked of. A pending fallback elicitation belongs to the session the server verified when the tool asked, or to the authenticated caller when there was no session. Mapped to JSON-RPC -32003.
ElicitationTimeoutError
Thrown when an elicitation request times out waiting for the user’s response.ElicitationFallbackRequired
Thrown when elicitation is requested but the client doesn’t support the standard protocol. This is not a failure — it triggers the fallback flow where the tool returns instructions to the LLM, and the LLM usessendElicitationResult to continue.
This error has a
statusCode of 200 because it is not a failure — it’s a signal to switch to the fallback elicitation flow.ElicitationStoreNotInitializedError
Thrown when attempting to access the elicitation store before scope initialization has completed. Callers shouldawait scope.ready before accessing elicitationStore.
ElicitationDisabledError
Thrown when elicitation is used but disabled in server configuration. Enable via@FrontMcp({ elicitation: { enabled: true } }).
"Elicitation is disabled on this server."