Your logo on consent
The consent screen is the one place a person decides to let a client place orders for them. It now shows who they are trusting, not just the words.
What changed
When a person approves an MCP client that connects through OAuth, the screen that says “You are giving {client} permission to place orders on your behalf” shows the client's logo and the Layout mark side by side.
- The logo comes from your redirect host. It is the logo for the host your redirect URI points at, which is where the authorization is delivered. There is nothing to upload or configure.
- No logo is never an error. A
localhostredirect, a host with no recognisable brand, or a logo that cannot be found shows the Layout mark alone, exactly as the screen looked before. - A different logo domain, on request. If your callback host is not where your brand lives, a verified client can ask us to set the domain its logo is drawn from.
Why it matters
People approve what they recognise. Seeing your mark next to Layout's on the screen that grants ordering makes the connection feel like yours, and because the logo follows the host that receives the authorization, it always belongs to the client the person is approving.
What to do
Nothing, if your redirect URI is on your own domain. To check it, start a connection from your client and look at the consent screen. Clients that build a session with a Layout build token instead of OAuth never see this screen; see Connect.
Breaking changes
None. The consent flow, its scopes and its redirect behaviour are unchanged.