mcp elicitation support #450
Description
What you'd like to see
The docker-mcp gateway supports forwarding of elicitation messages from servers that it's running. It also uses a few internal tools that will check whether a client supports elicitations and then potentially raise elicitation messages for some use cases.
This is relatively low priority because so many clients do not support them. The gateway checks for client support before attempting to either use or forward them.
Why you'd like to see it
Using elicitations when a remote server is added dynamically could be a good way to elicit a custom consent screen. The nanobot client currently support elicitations.
Workarounds?
Fallbacks for elicitations are standard practice so we're doing fine without them. I just don't think it's okay for an mcp gateway to not support them. We want to encourage MCP authors to use them.