Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here
mcp-apps logo

mcp-apps

claude-plugins-official

developmentClaude Codeby Anthropic / Model Context Protocol

Summary

Skills for creating MCP Apps with the MCP Apps SDK

Install to Claude Code

/plugin install mcp-apps@claude-plugins-official

Run in Claude Code. Add the marketplace first with /plugin marketplace add anthropics/claude-plugins-official if you haven't already.

README.md

<!-- LOGO --> <div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="media/mcp-white.svg"> <source media="(prefers-color-scheme: light)" srcset="media/mcp.svg"> <img src="media/mcp.svg" alt="MCP Apps" width="128"> </picture> <h1>MCP Apps</h1> <p> Build interactive UIs for MCP tools — charts, forms, dashboards — that render inline in Claude, ChatGPT and any other compliant chat client. <br /><br /> <a href="#why-mcp-apps">Why</a> · <a href="https://apps.extensions.modelcontextprotocol.io/api/documents/Quickstart.html">Quickstart</a> · <a href="https://apps.extensions.modelcontextprotocol.io/api/">API Docs</a> · <a href="https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx">Spec</a> · <a href="CONTRIBUTING.md">Contributing</a> </p> </div>

<p align="center"> <a href="https://github.com/modelcontextprotocol/ext-apps/actions/workflows/ci.yml"><img src="https://github.com/modelcontextprotocol/ext-apps/actions/workflows/ci.yml/badge.svg" alt="CI"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue" alt="License: Apache 2.0"></a> <a href="https://www.npmjs.com/package/@modelcontextprotocol/ext-apps"><img src="https://img.shields.io/npm/v/@modelcontextprotocol/ext-apps.svg" alt="npm version"></a> <a href="https://www.npmjs.com/package/@modelcontextprotocol/ext-apps"><img src="https://img.shields.io/npm/dm/@modelcontextprotocol/ext-apps.svg" alt="npm downloads"></a> <a href="https://github.com/modelcontextprotocol/ext-apps"><img src="https://img.shields.io/github/stars/modelcontextprotocol/ext-apps" alt="GitHub stars"></a> <a href="https://apps.extensions.modelcontextprotocol.io/api/"><img src="https://img.shields.io/badge/docs-API%20Reference-blue" alt="API Documentation"></a> </p>

<p align="center"> <img src="media/excalidraw.gif" alt="MCP Apps demo" width="600"> <br><em>Excalidraw built with MCP Apps, running in Claude</em> </p>

Table of Contents

Build with Agent Skills

The fastest way to build an MCP App is to let your AI coding agent do it. This repo ships four Agent Skills — install them once, then just ask:

| Skill | What it does | Try it | | --------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------- | | create-mcp-app | Scaffolds a new MCP App with an interactive UI from scratch | _"Create an MCP App"_ | | migrate-oai-app | Converts an existing OpenAI App to use MCP Apps | _"Migrate from OpenAI Apps SDK"_ | | add-app-to-server | Adds interactive UI to an existing MCP server's tools | _"Add UI to my MCP server"_ | | convert-web-app | Turns an existing web app into a hybrid web + MCP App | _"Add MCP App support to my web app"_ |

Install the Skills

Claude Code — install via the plugin marketplace:

/plugin marketplace add modelcontextprotocol/ext-apps
/plugin install mcp-apps@modelcontextprotocol-ext-apps

Other agents — any AI coding agent that supports Agent Skills can use these skills. See the agent skills guide for manual installation instructions.

Once installed, verify by asking your agent _"What skills do you have?"_ — you should see create-mcp-app, migrate-oai-app, add-app-to-server, and

convert-web-app in the list. Then just ask it to create or migrate an app and it will guide you through the rest.

Supported Clients

<p align="center"> <a href="https://developers.openai.com/apps-sdk/mcp-apps-in-chatgpt/"><img src="https://img.shields.io/badge/ChatGPT-docs-74aa9c?logo=openai&logoColor=white" alt="ChatGPT"></a> <a href="https://claude.com/docs/connectors/building/mcp-apps/getting-started"><img src="https://img.shields.io/badge/Claude-docs-d97706?logo=claude&logoColor=white" alt="Claude"></a> <a href="https://code.visualstudio.com/blogs/2026/01/26/mcp-apps-support"><img src="https://img.shields.io/badge/VS_Code-docs-007ACC?logo=visualstudiocode&logoColor=white" alt="VS Code"></a> <a href="https://block.github.io/goose/docs/tutorials/building-mcp-apps/"><img src="https://img.shields.io/badge/Goose-docs-000000?logo=goose&logoColor=white" alt="Goose"></a> <a href="https://learning.postman.com/docs/postman-ai/mcp-requests/interact"><img src="https://img.shields.io/badge/Postman-docs-FF6C37?logo=postman&logoColor=white" alt="Postman"></a> <a href="https://www.mcpjam.com/blog/mcp-apps-example"><img src="https://img.shields.io/badge/MCPJam-docs-8B5CF6" alt="MCPJam"></a> <a href="https://manufact.com/inspector"><img src="https://img.shields.io/badge/mcp--use-inspector-E5F3FD" alt="mcp-use"></a> </p>

> [!NOTE] > MCP Apps is an extension to the > core MCP specification. Host > support varies — see the > clients page for the full list.

Why MCP Apps?

MCP tools return text and structured data. That works for many cases, but not when you need an interactive UI, like a chart, form, design canvas or video player.

MCP Apps provide a standardized way to deliver interactive UIs from MCP servers. Your UI renders inline in the conversation, in context, in any compliant host.

How It Works

MCP Apps extend the Model Context Protocol by letting tools declare UI resources:

1. Tool definition — Your tool declares a ui:// resource containing its HTML interface 2. Tool call — The LLM calls the tool on your server 3. Host renders — The host fetches the resource and displays it in a sandboxed iframe 4. Bidirectional communication — The host passes tool data to the UI via notifications, and the UI can call other tools through the host

Getting Started

npm install -S @modelcontextprotocol/ext-apps

New here? Start with the Quickstart Guide to build your first MCP App.

Using the SDK

The SDK serves three roles: app developers building interactive Views, host developers embedding those Views, and MCP server authors registering tools with UI metadata.

| Package | Purpose | Docs | | ------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | @modelcontextprotocol/ext-apps | Build interactive Views (App class, PostMessageTransport) | API Docs → | | @modelcontextprotocol/ext-apps/react | React hooks for Views (useApp, useHostStyles, etc.) | API Docs → | | @modelcontextprotocol/ext-apps/app-bridge | Embed and communicate with Views in your chat client | API Docs → | | @modelcontextprotocol/ext-apps/server | Register tools and resources on your MCP server | API Docs → |

There's no _supported_ host implementation in this repo (beyond the examples/basic-host example).

The MCP-UI client SDK offers a fully-featured MCP Apps framework used by a few hosts. Clients may choose to use it or roll their own implementation.

Examples

The examples/ directory contains demo apps showcasing real-world use cases.

<!-- prettier-ignore-start --> | | | | |:---:|:---:|:---:| | ![Map](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/map-server) | ![Three.js](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/threejs-server) | ![ShaderToy](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/shadertoy-server) | | Map | Three.js | ShaderToy | | ![Sheet Music](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/sheet-music-server) | ![Wiki Explorer](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/wiki-explorer-server) | ![Cohort Heatmap](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/cohort-heatmap-server) | | Sheet Music | Wiki Explorer | Cohort Heatmap | | ![Scenario Modeler](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/scenario-modeler-server) | ![Budget Allocator](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/budget-allocator-server) | ![Customer Segmentation](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/customer-segmentation-server) | | Scenario Modeler | Budget Allocator | Customer Segmentation | | ![System Monitor](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/system-monitor-server) | ![Transcript](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/transcript-server) | ![Video Resource](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/video-resource-server) | | System Monitor | Transcript | Video Resource | | ![PDF Server](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/pdf-server) | ![QR Code](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/qr-server) | ![Say Demo](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/say-server) | | PDF Server | QR Code (Python) | Say Demo |

Starter Templates

| | | |:---:|:---| | ![Basic](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/basic-server-react) | The same app built with different frameworks — pick your favorite!<br><br>React · Vue · Svelte · Preact · Solid · Vanilla JS | <!-- prettier-ignore-end -->

Running the Examples

With basic-host

To run all examples locally using basic-host (the reference host implementation included in this repo):

git clone https://github.com/modelcontextprotocol/ext-apps.git
cd ext-apps
npm install
npm start

Then open http://localhost:8080/.

With MCP Clients

Every Node.js example is published as @modelcontextprotocol/server-<name>. To add one to an MCP client that supports stdio (Claude Desktop, VS Code, etc.), use this pattern:

{
  "mcpServers": {
    "<name>": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-<name>", "--stdio"]
    }
  }
}

For example, to add the map server: @modelcontextprotocol/server-map. The Python examples (qr-server, say-server) use uv run instead — see their READMEs for details.

Local Development

To test local modifications with an MCP client, clone the repo, install, then point your client at a local build:

{
  "mcpServers": {
    "<name>": {
      "command": "bash",
      "args": [
        "-c",
        "cd ~/code/ext-apps/examples/<name>-server && npm run build >&2 && node dist/index.js --stdio"
      ]
    }
  }
}

Specification

<div align="center">

| Version | Status | Link | | -------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------- | | 2026-01-26 | Stable | specification/2026-01-26/apps.mdx | | draft | Development | specification/draft/apps.mdx |

</div>

Resources

(Draft)

Contributing

Contributions are welcome! Please read CONTRIBUTING.md for guidelines on how to get started, submit pull requests, and report issues.

Related plugins

Browse all →