MCP tools have only ever returned text for the model to read.
@tan_stack67K followers
133,087 views
32 Comments
Comments from the original post on X (Twitter)

@A_Pasevin
Love this! Can imagine multiple possibilities! But I hope this is not the beginning of something awful like marketing banners in your MCP responses :)) Next coming up add blocker for MCPs :PP
7 likes

@vitobotta
This was always the direction for MCP. Returning just text from a tool that controls a UI was always going to feel limiting.
5 likes

@rbbydotdev
need a api description language, or OpenAPI extension scheme to get this right
5 likes

@MarkSteadmanWD
Looks cool! 😊 That said, I'm looking forward to seeing more updates around TanStack Start again. My timeline has been very AI-heavy lately, and I'd love to see more of the core framework too.
3 likes

@shaunaksri
love to see MCP's resource primitives done right 🤌
3 likes

@NabhaniMehdi
This is so helpful! Now I can remove my workaround 🤪
2 likes

@TheHolyCoder
So we are back to ui now?
2 likes

@BruzWJ
tbh surprised MCP renders real widgets now, but i'd only trust it for decisions once the model handles broken UI cleanly
2 likes

@ApplyWiseAi
the model now shipping pixels back is a real shift. does the client treat those ui:// widgets as sandboxed by default or does the host app own the trust boundary
2 likes

@husamujahed
This is clean
2 likes

@adelbucetta
that changes everything. now we're not just writing code, we're building user experiences directly into the model itself.
2 likes

@sebuzdugan
the hard part is not rendering it's keeping widget state after tool retries
2 likes

@nickventuri
text chats feel like dial up now
2 likes

@Timur_Yessenov
The `ui://` bit is a real product shift. Text tools make the model narrate state; widgets let the user fix state in place. I’d test stale widget data and cancelled tool calls before celebrating the demo.
2 likes

@blakeyoder
Very nice! I custom built this in vercels ai-sdk but nice to see first-class support
2 likes

@gnrybooil
wow smth that @fastmcp had for a while
1 like

@hottubjohn
ya'll crazy for this one.
1 like

@dipankarsarkar
the real shift here isn't text to UI. it's tool to runtime. once a server can ship interactive widgets, MCP stops being a protocol and becomes an app platform. and platforms live or die on the trust boundary, not the render layer. who gets to draw in your agent's context is the question now.
1 like

@pawan_gangs
Woww
1 like

@mfrachet
@abhiaiyer @damien_schneid use chat + MessageFactory I guess
1 like












