When a client can't answer an MCP server's mid-call question, the official fallback is "proceed on a default" — this is the out-of-band answer channel instead.
The server hands the bridge an elicitation/create (form schema or URL); the bridge renders it out-of-band to the operator (hosted page / email; SMS optional), enforces accept/decline/cancel semantics and expiry, binds the answer to the session + requestState, and returns it in the shape the session's protocol era expects — a bare ElicitResult for the initialize-declared eras (2025-03 / 2025-11), or an MRTR inputResponses entry bound to requestState for 2026-07. Decline and cancel stay first-class — never silently converted to a default. Expiry resolves to cancel, uncharged, and does not consume your one free ask. Form mode refuses secret-named fields at create; URL mode completes via an opaque callback and the secret never enters the bridge, its logs, the client, or the model result.
Form-mode ask $0.25/ask · URL-mode ask $0.50/ask · Server plan $9.99/mo per server including 100 form-mode asks/mo, then $0.25/ask (URL-mode always $0.50/ask, including on the plan). First bridged ask free, once per operator account, ever.
Limitations, stated plainly: the exposed subset of MCP servers — those whose tools need one human answer mid-call — is unmeasured. Rendering runs through an in-process inbox double at $0, so production notification/rendering cost sits in the $0.01–$0.05/ask memo band for a hosted page + real notification. Era shapes are grounded in the vendored corpus schemas (2025-11-25 + 2026-07-28). Default TTL 300 s. Support: support@textforagents.com.
API: https://textforagents.com/products/elicitation-bridge-unsupported-clients/ · Terms · Privacy