Our take
Activeregular commits and releases- Activity
- 71
- Community
- 69
- Issues
- 42
- Pull requests
- 69
+140 stars in the last 30 days
- Releases more often than 84% of the projects we track
MCP Apps is an actively maintained protocol extension and SDK with a broad contributor base, but adopting it depends on a host that implements the extension.
Good fit if
- You already build on MCP and need interactive tool interfaces in compliant chat clients.
- You want TypeScript packages, framework examples and Agent Skills to help build or migrate an app.
- Your team can target Node.js 20 or newer and verify support in its chosen host.
Look elsewhere if
- You need a complete, supported host implementation from this repository rather than building or selecting one separately.
- Your target chat client does not support MCP Apps, or you only need ordinary text and structured tool output.
All health signals
| Last commit | 2026-10-27 (today) |
|---|---|
| Commits, last 90 days | 48 |
| Releases, last 12 months | 40 (latest v2.0.4, 2026-10-27) |
| Contributors | 47 (top contributor: 45% of commits) |
| Issues closed, last 90 days | 4 (typically closed in 33 days) |
| Pull requests merged, last 90 days | 26 (typically merged in 0 days) |
| Project age | 11 months |
Checked on 2026-10-28 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
3,108Forks
438Change since Nov 16, 2026: +4 stars·+3 forks
Overview
MCP Apps is an extension to the Model Context Protocol (MCP), with a TypeScript SDK for building interactive interfaces served by MCP servers. It addresses the limits of text-and-data tool responses by letting an MCP tool provide a UI that renders inline in compliant chat clients, including Claude and ChatGPT.
The project is for app developers, MCP server authors and chat-client developers. Its SDK covers building Views, registering tools and resources, and embedding Views in a host. The repository includes examples and a basic reference host, but does not provide a supported production host implementation.
Key Features
- Define HTML interfaces as
ui://resources associated with MCP tools. - Render tool interfaces in a sandboxed iframe in a compliant host.
- Pass tool data to the UI through host notifications and let the UI call tools through the host.
- Build Views with the core SDK or its React hooks package.
- Embed Views in chat clients with the app-bridge package.
- Register UI-enabled tools and resources with the server helpers.
- Explore example apps and starter templates for React, Vue, Svelte, Preact, Solid and vanilla JavaScript.
- Use Agent Skills to scaffold apps, migrate OpenAI Apps, add UIs to servers or adapt web apps.
Use Cases
- MCP server authors can add interactive forms or dashboards when a text response is not enough.
- Developers building data tools can present maps, charts, heatmaps or scenario models inline for users to explore.
- Chat-client developers can embed MCP-provided interfaces using the app-bridge APIs.
- Teams with existing web apps can use the migration and conversion skills to add MCP App support.
What you need
Detected in the repository
- Node.js >=20 (from package.json)
- A test suite and automated checks on GitHub Actions
Getting Started
Node.js 20 or newer is required. Install the SDK and MCP client package:
npm install -S @modelcontextprotocol/ext-apps @modelcontextprotocol/client@^2.0.0 zod@^4.2.0
For server setup and a first app, follow the Quickstart and README.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- mcp-ui: mcp-ui provides SDKs for attaching and rendering interactive web interfaces in MCP hosts, while ext-apps implements the MCP Apps specification and SDK.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| ext-apps | TypeScript | – | 3k | Active |
| mcp-ui | TypeScript | Apache-2.0 | 5.2k | Quiet |
Considerations
- Host support is not uniform: MCP Apps is an MCP extension, and the repository notes that host support varies. Confirm that each target client supports it.
- The included basic host is an example, not a supported host implementation. Teams embedding Views may need to implement and maintain their own host integration.
- The project is active, with regular commits and releases and contributions from many contributors. Issue handling is slower than PR merging in the measured period, so do not assume reported issues will be resolved quickly.
- Views run in a sandboxed iframe and communicate through the host; app behavior therefore depends on the host’s implementation of the protocol.
Found this useful?
Share it with someone who would like ext-apps.