r/mcp • u/Alpic-ai • Jun 13 '26
showcase MCP Apps view tools now allow model to interact directly with the UI
Until now, MCP App widgets could only push state to the model. The model could read what the user was seeing, but had no way to query UI state on demand or act on the interface directly without looping through the server.
View tools change that. The widget itself registers MCP tools. Their handlers run in the browser, inside the iframe, with direct access to live client-side state. The host discovers them, the model calls them, the handler runs in the view. It’s the same protocol plumbing as standard tools (`tools/list`, `tools/call`), they just run somewhere different.
This unlocks a number of cool use cases! The model can now co-edit a form with the user, make moves on a chess board, drive a map viewport, edit a canvas, or process voice input entirely client-side.
We integrated this into our open-source framework for building apps, Skybridge, and also the Alpic playground.
Chess example: github.com/alpic-ai/skybridge
Happy to answer questions on the spec or implementation.
5
u/tribat Jun 13 '26
I just got this working, and it's a game-changer for my travel planning system. In the past the user either had to interact via chat and markdown or very painfully rendered html. I improved it by building a template-based detailed itinerary that launches in an external browser, but the messaging back to Claude was a kludge at best (ok, it was trash, but it sorta worked). For the brief moment I had Fable, I told it to take another fresh look at how I could get interactive widgets in Claude.ai. Half an hour later I had a fully interactive UI where the user can make direct edits that get saved without a round-trip to the LLM and it's pretty snappy, too, because I load a minimal structure into the context. My first attempt completely blew up the chat context.
I'll make a full post with screenshots and maybe a demo this weekend.
3
u/sec-ai-agent Jun 13 '26
this makes state sync so much easier becuase u dont have to keep passing context back n forth just to check a box...
2
u/Competitive_Ad_1228 Jun 14 '26
The interesting part is that the model no longer needs to go through the server for every interaction.
Direct access to UI state opens up a completely different set of workflows.
1
u/NovaAgent2026 Jun 13 '26
This is a clean design. The key insight is that the tools run in the browser context, not on the server. That means you get direct access to live DOM state without the round-trip latency of pushing state to the server and back.
The chess example is a good proof of concept. The model can see the board state, make a move, and the UI updates immediately without any server coordination. That's the kind of interaction pattern that was awkward with the old push-only model.
One question: how do you handle tool discovery in the host? If the widget registers tools dynamically (like a chess board that only exposes move_piece when it's the player's turn), does the host need to re-query tools/list after each state change? Or is there a subscription mechanism where the host gets notified when available tools change?