# MCP URL elicitation pauses for consent in the Everruns UI

> When an MCP tool asks a person to finish a step in the browser, the turn now pauses on a consent card and the secret never enters the model context.

Source: <https://everruns.com/docs/changelog/2026-09-03-mcp-url-elicitation-consent/>

Date: 2026-09-03
Products: Platform, Cloud
Category: Feature
Available: In 0.24.0
Pull request: everruns/everruns#3354

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](https://everruns.com/docs/features/mcp-url-elicitation/) and [Complete a URL elicitation](https://everruns.com/docs/how-to/complete-a-url-elicitation/). [#3354](https://github.com/everruns/everruns/pull/3354)