M
modelcontextprotocol/ext-apps
Spec and SDK for MCP apps embedded in a chat
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"modelcontextprotocol-ext-apps": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-", "--stdio"]
}
}
}Parsed from the README we fetched on 2026-11-04; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"modelcontextprotocol-ext-apps": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-", "--stdio"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio modelcontextprotocol-ext-apps -- npx -y @modelcontextprotocol/server- --stdio
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx -y @modelcontextprotocol/server- --stdio
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y @modelcontextprotocol/server- --stdio. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
MCP Apps
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Build interactive UIs for MCP tools — charts, forms, dashboards — that render inline in Claude, ChatGPT and any other compliant chat client.
Why
Quickstart
API Docs
Spec
Contributing
Excalidraw built with MCP Apps, running in Claude
## Table of Contents
Build with Agent Skills
Supported Clients
Why MCP Apps?
How It Works
Getting Started
Using the SDK
Examples
Specification
Resources
Contributing
## 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
> [!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
Requires Node.js 20+. The base MCP SDK packages are ^2.0.0 peers of
ext-apps (@modelcontextprotocol/core is a required peer that client already depends on, so npm installs it for you).
For a View or host:
bash
npm install -S @modelcontextprotocol/ext-apps \
@modelcontextprotocol/client@^2.0.0 \
zod@^4.2.0
For an MCP server, add the server package (and, for HTTP transports, the Node
and Express adapters):
bash
npm install -S @modelcontextprotocol/ext-apps \
@modelcontextprotocol/client@^2.0.0 \
@modelcontextprotocol/server@^2.0.0 \
@modelcontextprotocol/node@^2.0.0 \
@modelcontextprotocol/express@^2.0.0 \
Why
Quickstart
API Docs
Spec
Contributing
Excalidraw built with MCP Apps, running in Claude
## Table of Contents
Build with Agent Skills
Supported Clients
Why MCP Apps?
How It Works
Getting Started
Using the SDK
Examples
Specification
Resources
Contributing
## 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
> [!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
Requires Node.js 20+. The base MCP SDK packages are ^2.0.0 peers of
ext-apps (@modelcontextprotocol/core is a required peer that client already depends on, so npm installs it for you).
For a View or host:
bash
npm install -S @modelcontextprotocol/ext-apps \
@modelcontextprotocol/client@^2.0.0 \
zod@^4.2.0
For an MCP server, add the server package (and, for HTTP transports, the Node
and Express adapters):
bash
npm install -S @modelcontextprotocol/ext-apps \
@modelcontextprotocol/client@^2.0.0 \
@modelcontextprotocol/server@^2.0.0 \
@modelcontextprotocol/node@^2.0.0 \
@modelcontextprotocol/express@^2.0.0 \
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/modelcontextprotocol-ext-apps/)
- Source
- awesome · https://github.com/modelcontextprotocol/ext-apps
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.