News for hackers. Stuff that matters.
Re:Figma restricts MCP access to whitelisted clients, exclud... by rixed on Friday October 02, 2026 @12:20AM (#49929806)
Exactly my experience. Yet, I believe app will not only provide data but also some custom, short lived UI widgets in places where a more specific and consistent UX makes sense. But apps will definitively lose control over the navigation and even lose track of the user (they will identify and authorize only one : the harness; who sits behind will remain a mystery)

I've written about this "UI to AI" pivot for my own Saas (cloudywithachanceoflatency.net). I believe it's a big win/win for every party.

Re:Figma restricts MCP access to whitelisted clients, exclud... by einsteinx2 on Friday October 02, 2026 @05:43PM (#49938970)
> they will identify and authorize only one : the harness; who sits behind will remain a mystery

This doesn’t sound right to me. To connect to the MCP server the user must authenticate. It’s not like all Claude users connect to Figma using the same account, the user connects using their Figma account. So the app still has a direct customer connection even if they lose the ability to control the UI. Unless you’re imagining some other way this would work that I’m not seeing.

Re:Figma restricts MCP access to whitelisted clients, exclud... by rixed on Saturday October 03, 2026 @12:29AM (#49941354)
I don't believe actual users will login. The LLM through their harness will, using an identity and password found in some shared vault. The app will still do authentication but no user management. Behind an access token there might be zero, one or several humans. Dystopian version: The allow-list for the oauth redir will become the new gatekeeper in a world without local compte, and the redir client the billed entity.