MCP URL elicitation pauses for consent in the Everruns UI

An MCP server can now ask a person to finish something in their browser, such as authorizing a charge, pasting an API key or clicking a consent screen, and Everruns handles it as both MCP client and MCP server. The value never passes through the MCP client, the model’s context or the event log.

In the UI: a tool call that stops on a URL elicitation pauses the turn on a confirmation card. The consent is single use and bound to the server, tool and domain you were shown.

For MCP clients of Everruns: the /mcp endpoint gains session_set_secret and connect, which point you at a form Everruns serves instead of taking the value.

See MCP URL elicitation and Complete a URL elicitation. #3354