# MCP Apps: Extending the Frontier — Ido Salomon & Liad Yosef

Source: [AI Engineer](https://www.youtube.com/watch?v=-jY2T2PiJBE)  
Feed7 permalink: https://feed7.dev/p/mcp-apps-extending-the-frontier-ido-salomon-liad-yosef-1gtlsr9  
Published: 2026-08-02T23:30:06.000Z  
Trust: Source Linked (source_linked)

## Why Included

MCP Apps let servers return sandboxed, interactive UI instead of text alone while the host retains control of prompts and tool calls—a useful pattern for agent workflows needing charts or controls.

## Source Summary

MCP Apps lets an MCP tool link to an HTML resource that a compatible host renders as a **sandboxed interactive view**. UI events travel back to the host, which decides whether to issue a prompt, tool call, resource request, or other action.

## Practical Implication

For agent-facing tools, return a focused chart or control when text obscures the task. Keep mutations behind host-mediated tool calls, and consider the official SDK so spec changes flow into the implementation. The same app code is presented as portable across supporting hosts.

## Agent-Ready Context

MCP Apps lets an MCP tool link to an HTML resource that a compatible host renders as a **sandboxed interactive view**. UI events travel back to the host, which decides whether to issue a prompt, tool call, resource request, or other action.

For agent-facing tools, return a focused chart or control when text obscures the task. Keep mutations behind host-mediated tool calls, and consider the official SDK so spec changes flow into the implementation. The same app code is presented as portable across supporting hosts.

The specification is **still evolving**: reusable view tools and interoperability with declarative or generative UI approaches remain active work. Portability also depends on each target host implementing MCP Apps and its interaction protocol consistently.

## Connected Context

Feed7 judgment across 330 accumulated Signals:

MCP Apps extends MCP from textual tool results to portable interactive views while preserving the host as the authority for prompts and tool calls. That separation becomes especially consequential for deployment and purchasing tools, but the portability promise remains conditional on evolving specifications and consistent host implementations.

- [Vercel MCP now supports purchases](https://feed7.dev/p/vercel-mcp-now-supports-purchases-1facboz) — Purchases demonstrate why MCP Apps keeps mutations host-mediated: an interactive control can present choices, but pricing disclosure and confirmation must remain part of the authorized tool call.
- [Vercel MCP can now deploy code](https://feed7.dev/p/vercel-mcp-can-now-deploy-code-1292qsq) — Deployment is another mutation where a focused MCP App could expose status or controls, while the host-mediated call boundary must distinguish initiation from successful completion.
- [Latest MCP spec now supported in mcp-handler](https://feed7.dev/p/latest-mcp-spec-now-supported-in-mcp-handler-1kkt3s0) — mcp-handler’s raised runtime, schema, SDK, and transport requirements show the implementation consequences of building against an evolving MCP ecosystem, narrowing MCP Apps’ portability claim.
- [ChromeDevTools/chrome-devtools-mcp](https://feed7.dev/p/chrome-devtools-mcp-0ow49x2) — Chrome DevTools MCP supplies rich visual and diagnostic evidence that could benefit from interactive views, while its sensitive browser data reinforces the need for sandboxing and host control.

## Context Map

- Layer: context
- Domains: coding
- Topics: mcp, tool-use, interface-quality

## Uncertainty

- The specification is **still evolving**: reusable view tools and interoperability with declarative or generative UI approaches remain active work. Portability also depends on each target host implementing MCP Apps and its interaction protocol consistently.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.