Skip navigation
MCP tools have only ever returned text for the model to read.
0:00 / 0:45

MCP tools have only ever returned text for the model to read.

TANSTACK

@tan_stack67K followers

Visit on X
941 likesDownloadOriginal post

133,087 views

MCP tools have only ever returned text for the model to read. Now they return interactive UI. 🪄 TanStack AI's new MCP Apps support renders ui:// widgets right in the chat - static or fully interactive, with a client/server bridge.

32 Comments

Comments from the original post on X (Twitter)

  • Aleksandr Pasevin's profile picture

    @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

  • Vito Botta's profile picture

    @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's profile picture

    @rbbydotdev

    need a api description language, or OpenAPI extension scheme to get this right

    5 likes

  • Mark Steadman's profile picture

    @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

  • Shaunak Srivastava's profile picture

    @shaunaksri

    love to see MCP's resource primitives done right 🤌

    3 likes

  • Mehdi Nabhani's profile picture

    @NabhaniMehdi

    This is so helpful! Now I can remove my workaround 🤪

    2 likes

  • ADT's profile picture

    @TheHolyCoder

    So we are back to ui now?

    2 likes

  • BruzWJ's profile picture

    @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

  • Samian's profile picture

    @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

  • Husam's profile picture

    @husamujahed

    This is clean

    2 likes

  • Adel Bucetta's profile picture

    @adelbucetta

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

    2 likes

  • Sebastian Buzdugan's profile picture

    @sebuzdugan

    the hard part is not rendering it's keeping widget state after tool retries

    2 likes

  • Nick Venturi's profile picture

    @nickventuri

    text chats feel like dial up now

    2 likes

  • Timur Yessenov's profile picture

    @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

  • Blake Yoder's profile picture

    @blakeyoder

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

    2 likes

  • gnryboooil 🇺🇦's profile picture

    @gnrybooil

    wow smth that @fastmcp had for a while

    1 like

  • John's profile picture

    @hottubjohn

    ya'll crazy for this one.

    1 like

  • Dipankar Sarkar's profile picture

    @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 Gangwani's profile picture

    @pawan_gangs

    Woww

    1 like

  • Marvin's profile picture

    @mfrachet

    @abhiaiyer @damien_schneid use chat + MessageFactory I guess

    1 like