## Elicitation Bridge: out-of-band answer channel for unsupported clients (P112) — TextForAgents LLC
When a client can't answer an MCP server's mid-call elicitation question, the documented fallback is to proceed on a default. Elicitation Bridge takes the question out-of-band instead: the server hands the bridge an elicitation/create (form schema or URL), the bridge renders it to the operator (hosted page / email; SMS optional), enforces accept/decline/cancel and expiry, binds the answer to the session + requestState, and returns it in the session's protocol-era shape — bare ElicitResult for the 2025 eras, MRTR inputResponses + requestState for 2026-07. Decline and cancel are first-class, never converted to a default; expiry resolves to cancel, uncharged. Form mode refuses secret-named fields; URL mode completes via an opaque callback and the secret never enters the bridge, its logs, the client, or the model result. The exposed subset of MCP servers is unmeasured; the lab build used an in-process inbox double, so production notification cost sits in the $0.01–$0.05/ask band.
**Form-mode bridged ask $0.25/ask** · **URL-mode (secrets) ask $0.50/ask** · **Server plan $9.99/mo per server including 100 form-mode asks per month, then $0.25/ask** (URL-mode asks always $0.50/ask, including on the plan; first bridged ask free, once per operator account, ever).
Docs/packet summary: elicitation-bridge-unsupported-clients — see the product page for the full description, limits, and support (support@textforagents.com).