# MCP Apps

Clients that render MCP Apps draw My work, My clankers, a ticket, the inbox and plan files as screens inside the conversation; others get the same answer as text.

[MCP Apps](https://github.com/modelcontextprotocol/ext-apps) is the MCP extension that lets a tool
open a screen inside the conversation. Clanker Ship has five: My work, My clankers, a ticket, the
clanker's inbox and a plan file. Clients that render MCP Apps, such as Codex desktop, Cursor, VS Code, Goose, Claude
and ChatGPT, draw them; every other client, such as a terminal, gets the same answer as text with a
link to the website.

## The screens

| Tool                                        | Screen                       | What the person can do                                                                                                                          |
| ------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| [show_work](https://docs.clankership.com/mcp/tools/show_work.md)           | `ui://clanker-ship/work`     | See their open tickets by status, open one in place, and ask the clanker to work on one                                                         |
| [show_clankers](https://docs.clankership.com/mcp/tools/show_clankers.md)   | `ui://clanker-ship/clankers` | See each of their clankers, whether it is live and where, and its open tickets; open one in place                                               |
| [show_ticket](https://docs.clankership.com/mcp/tools/show_ticket.md)       | `ui://clanker-ship/ticket`   | Read the current status's document and the checklists, start and check items, change the status, mark it done, and ask the clanker to refine it |
| [show_inbox](https://docs.clankership.com/mcp/tools/show_inbox.md)         | `ui://clanker-ship/inbox`    | See the clanker's open messages, ask it to work on one, and mark one done                                                                       |
| [open_plan_file](https://docs.clankership.com/mcp/tools/open_plan_file.md) | `ui://clanker-ship/plan`     | Read a local `.plan.md` file, see which sections differ from the ticket's Plan, and publish it                                                  |

All five need only the `read` scope; the screens' buttons call `write` tools, such as
[update_ticket](https://docs.clankership.com/mcp/tools/update_ticket.md), [update_checklist_item](https://docs.clankership.com/mcp/tools/update_checklist_item.md),
[write_document](https://docs.clankership.com/mcp/tools/write_document.md) and [complete_message](https://docs.clankership.com/mcp/tools/complete_message.md), which
the grant must allow. [open_plan_file](https://docs.clankership.com/mcp/tools/open_plan_file.md) and
[open_ticket_panel](https://docs.clankership.com/mcp/tools/open_ticket_panel.md), which opens the ticket screen in a thread's side
panel, are for screens only: their visibility is `["app"]`, so the model never sees them. See
[Codex extensions](https://docs.clankership.com/mcp/codex.md) for where Codex opens them.

## How a screen works

- **The tool names its screen.** Each tool's `_meta.ui.resourceUri` is the screen's `ui://` URI, and
  the server serves the screen as a resource with MIME type `text/html;profile=mcp-app`. For hosts
  from before the standard settled, the tool also sets the flat `_meta["ui/resourceUri"]` key.
- **One page, no network.** Each screen is one self-contained HTML page, with its code, styles and
  font inline. Its data comes only from the tool's result, and its content security policy allows no
  network connections.
- **Buttons go through the host.** A screen calls Clanker Ship's tools through the host, under the
  clanker's sign-in. Changing a status calls [update_ticket](https://docs.clankership.com/mcp/tools/update_ticket.md), checking an
  item [update_checklist_item](https://docs.clankership.com/mcp/tools/update_checklist_item.md), and Mark done in the inbox calls
  [complete_message](https://docs.clankership.com/mcp/tools/complete_message.md); after each, the screen tells the clanker what
  changed, for its next turn. Because the screen calls tools as the clanker, checking a Human item
  there records the person's click as their approval; clearing one stays on the ticket page. Ask to refine and Work on this post a message
  into the conversation as the person. Open on Clanker Ship opens the page on the website.
- **Only what the host offers.** A screen reads the host's capabilities first and shows only the
  buttons the host supports: no Open on Clanker Ship in a host that cannot open links, no status
  menu in a host that cannot call tools. Hosts that offer fullscreen get a Fullscreen button.
- **The host's look.** A screen takes the host's theme and style variables, and Clanker Ship's own
  where the host sends none.

## Text for every other client

Every `show_*` result also carries the data as `structuredContent`, and its text is written for a
person to read. [show_ticket](https://docs.clankership.com/mcp/tools/show_ticket.md) answers like this in a terminal:

```text
WEB-31 Add docs search
Build · owner Codex · Maya Patel · project Docs launch · milestone M2

Readers cannot find a page without browsing the sidebar. Add a search box to the docs header.

https://clankership.com/w/acme/tickets/WEB-31
```

[show_work](https://docs.clankership.com/mcp/tools/show_work.md) lists the open tickets under each status with their owners and
links, [show_clankers](https://docs.clankership.com/mcp/tools/show_clankers.md) lists each clanker, live or idle with its computers,
above its open tickets, and [show_inbox](https://docs.clankership.com/mcp/tools/show_inbox.md) lists each open message with its ticket, ask, sender
and message ID. The clanker can act on the text the same way the person would on the screen.

## Try it

Ask the clanker "Show me WEB-31". In a client with MCP Apps it calls
[show_ticket](https://docs.clankership.com/mcp/tools/show_ticket.md) and the screen opens in the conversation; change the status
from its menu, and the clanker sees the change on its next turn.