20.3 How an MCP App works
- Approved by
- Panaversity ·
In everyday life. A hotel lets a restaurant set up a menu board in its lobby. Guests read the board and point at a dish. The board does not cook and does not take money. A hotel clerk takes the order to the kitchen. The clerk acts for the hotel, on behalf of that guest.
What you will learn. The four steps from a tool to a screen, and the path one button press takes.
Why it matters. The question of this chapter, whose call a button makes, is answered by the path. Without it, a screen looks like part of the connector. It is not.
One request, start to finish. At 10:15, Luis asks Claude for Cedar Ridge's open invoices.
- The model calls
list_open_invoices. As in 17.1, the AI app sends the call, with Luis's token. The connector returns five rows, a handle for the next page, and a text answer. - The AI app sees that the tool has a page. The tool's description carries a pointer to a page,
ui://brightline/open-invoices.html. - The AI app fetches the page and draws it in a sealed box inside the chat, and hands it the tool's result. Luis sees a table of five rows.
- At 10:16, Luis presses Next page. The page sends a message to the AI app: "please call this tool, with this handle". The AI app sends that call to the connector, the same way it sent the model's, and passes the new rows back to the page.
What are the parts?
MCP Apps became the first official MCP extension on January 26, 2026, and its specification is stable.1,2 Its name in the protocol is io.modelcontextprotocol/ui. It adds three things to the MCP you know. Each has a name in the code, given here once, in brackets. The rest of the chapter uses the plain names.
- A
ui://page, a resource whose address starts withui://and whose content is a web page. It is usually one HTML file with its code inside (its type istext/html;profile=mcp-app). - A pointer on a tool (
_meta.ui.resourceUri), which says "show this page when this tool runs". The AI app may fetch the page early, before the tool is ever called.3 - Messages between the page and the AI app, sent through the browser's message channel. Some are the MCP messages you know, such as
tools/call. Others are new, such as the first message the page sends, to say hello and get the AI app's settings (ui/initialize).2

Figure 20.5. One press, there and back. The page asks, the AI app calls with the person's token, and the rows come back the same way.
What does the page get, and when?
After the page's first message, the AI app sends it the tool's full input, then its result when the tool finishes. Some AI apps also send the input while the model is still writing it, so the screen can fill in early. That is optional, so a page must work from the complete input alone.2
What does the pointer look like?
This is a shortened tool description from Brightline's connector. The last lines point the tool to its page:
{
"name": "list_open_invoices",
"description": "List the signed-in company's open invoices, five a page, with a handle for the next page.",
"inputSchema": { "type": "object", "properties": { "handle": { "type": "string" } } },
"_meta": {
"ui": { "resourceUri": "ui://brightline/open-invoices.html" }
}
}Can the model work inside the screen?
Yes, in AI apps that support it. So far the page calls the connector's tools. The page can also offer tools of its own, called app tools, which the AI app shows to the model while the screen is open. The model calls one, such as "add a row" or "go to page three", and the page changes what the person sees.4 An app tool runs in the page, on what is showing. Anything that must be saved still goes to the connector, through a tool call that the connector checks (20.4).
How big can the screen get?
An AI app shows the page in one of its display modes: inline, in the conversation, or full screen. In Claude, a page that asks for full screen after a click opens in a side panel next to the chat. The page must still work wherever it is shown.5 A page can also hold a whole web app of yours, as an embedded site, once Claude allows that site's address for your connector.6
Can you build something like Claude Docs or Claude Slides?
Now that you know the parts, here is the full answer to the overview's question. Claude Docs are living documents that you write with Claude and your team. Claude Slides are decks you edit and present without leaving Claude.7 As of November 15, 2026, an MCP App can give your own connector most of that experience:
| What Docs and Slides give you | Can your connector's screen do it? |
|---|---|
| A full editor, not a small preview | Yes. In Claude, a screen can open beside the chat or full screen. Notion and Confluence already open their full editors in Claude this way8,5 |
| Claude makes changes while you watch | Yes. The page offers its own tools, called app tools, and the model calls them to change what is on the screen. Changes appear in the tool as Claude makes them, and the person approves them as for any connector action4,8 |
| You edit by hand as well | Yes. The page is your own web page, so it can hold any editor you build |
| Your existing web app inside the chat | Yes, as an embedded site, once Claude allows its address for your connector6 |
| The work is saved | Yes, on your server. The page saves through your tools, and the screen itself keeps nothing (20.8) |
| Opening it without a prompt | In Claude, yes. People can open a connected tool without a prompt, pin it, and keep it beside their artifacts in the sidebar8 |
Companies already ship this. At launch, Notion lets people create docs and databases, Atlassian lets them write and edit Confluence pages, Box lets them revise files and compare versions, and Adobe lets them edit photos and PDFs, all inside Claude.8 Each one is a connector with its own screens, built on the same standard as Brightline's.
Three things stay different:
- Where the work lives. A Claude Docs document or a Slides deck is kept in Claude, in the Artifacts tab, and exports to Word, PowerPoint or PDF.7 Your editor's documents live on your server. Storing, sharing and exporting them is your job.
- Where it works. Screens inside the chat work in many AI apps.3 Full apps, app tools and embedded sites are newer: in Claude they are in public preview for developers,8 and many other AI apps do not support app tools yet.9
- Who protects it. Every save is a call to your connector, made by a person or by the model. Chapters 18 and 19 still decide who may change what, and this chapter's question applies to every keystroke that saves.
So the answer is yes: you can build an editor that feels like Claude Docs inside the chat, and it can work beyond Claude. But the document is yours to store, share and protect. This chapter starts smaller, with a read-only screen, because every editor is built from the same three parts: a page, the tools it calls, and the checks behind them. The optional Lab 20b builds the full app.
Is it the same on a phone?
Mostly. In Claude's iOS and Android apps, the page runs in the phone's own web view instead of a sandboxed frame. It has no camera, microphone or location there, and a person must add the connector on the web or the desktop app before it appears on the phone.10
At work. The builder's coding agent adds the pointer to list_open_invoices and serves the page. Ana checks the table's columns against the contract from Chapter 17 and its list of fields that may leave (17.7): invoice number, vendor, amount and due date, and never the bank account ending.
The operating rule: a screen is a page that the AI app draws and sends calls for. The page asks, the AI app calls, the connector answers.
Check yourself
Question 1 / 3
0 answered
How does an AI app know that list_open_invoices has a screen?
Sources
- MCP Apps: the first official MCP extension, Model Context Protocol blog, 26 January 2026.↑
- MCP Apps specification, revision 2026-01-26, Model Context Protocol, accessed 15 November 2026.↑↑2↑3
- MCP Apps, Model Context Protocol, accessed 15 November 2026.↑↑2
- App tools, Claude documentation, accessed 15 November 2026.↑↑2
- Display modes, Claude documentation, accessed 15 November 2026.↑↑2
- Embedded sites, Claude documentation, accessed 15 November 2026.↑↑2
- What are artifacts and how do I use them?, Claude Help Center, accessed 15 November 2026.↑↑2
- Open your apps in Claude and work in them together, Claude, 10 November 2026.↑↑2↑3↑4↑5
- Extension Support Matrix, Model Context Protocol, accessed 15 November 2026.↑
- MCP Apps design guidelines, Claude documentation, accessed 15 November 2026.↑
- Owner
- Panaversity