modelcontextprotocol/ext-apps
Watch
1
0
Fork
You've already forked ext-apps
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: use consistent text/vnd.mcp.ui+html mimeType throughout

Browse source 
Replace all occurrences of text/html with text/vnd.mcp.ui+html
in the specification and example code for consistency.

The spec already defined text/vnd.mcp.ui+html in the capability
negotiation section but used text/html in other places.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Anton Pidkuiko MacBook 2025-11-21 19:32:46 +00:00
commit bd5a34ba07
No known key found for this signature in database
2 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

4
examples/simple-server/server.ts
View file

@ -47,7 +47,7 @@ const getServer = async () => {
uri: "ui://vanilla", uri: "ui://vanilla",
title: "Vanilla UI Template", title: "Vanilla UI Template",
description: "A simple vanilla JS UI", description: "A simple vanilla JS UI",
mimeType: "text/html", mimeType: "text/vnd.mcp.ui+html",
}; };
server.registerResource( server.registerResource(
@ -89,7 +89,7 @@ const getServer = async () => {
uri: "ui://react", uri: "ui://react",
title: "React UI Template", title: "React UI Template",
description: "A React-based UI", description: "A React-based UI",
mimeType: "text/html", mimeType: "text/vnd.mcp.ui+html",
}; };
server.registerResource( server.registerResource(

16
specification/draft/apps.mdx
View file

@ -43,7 +43,7 @@ MCP Apps extends the Model Context Protocol to enable servers to deliver interac
- **Bidirectional Communication:** UI iframes communicate with hosts using standard MCP JSON-RPC protocol - **Bidirectional Communication:** UI iframes communicate with hosts using standard MCP JSON-RPC protocol
- **Security Model:** Mandatory iframe sandboxing with auditable communication - **Security Model:** Mandatory iframe sandboxing with auditable communication
This specification focuses on HTML content (`text/html`) as the initial content type, with extensibility for future formats. This specification focuses on HTML content (`text/vnd.mcp.ui+html`) as the initial content type, with extensibility for future formats.
As an extension, MCP Apps is optional and must be explicitly negotiated between clients and servers through the extension capabilities mechanism (see Capability Negotiation section). As an extension, MCP Apps is optional and must be explicitly negotiated between clients and servers through the extension capabilities mechanism (see Capability Negotiation section).
@ -56,7 +56,7 @@ interface UIResource {
uri: string; // MUST start with 'ui://' uri: string; // MUST start with 'ui://'
name: string; // Human-readable identifier name: string; // Human-readable identifier
description?: string; // Description of the UI resource description?: string; // Description of the UI resource
mimeType: string; // SHOULD be 'text/html' in MVP mimeType: string; // SHOULD be 'text/vnd.mcp.ui+html' in MVP
} }
``` ```
@ -67,7 +67,7 @@ The resource content is returned via `resources/read`:
{ {
contents: [{ contents: [{
uri: string; // Matching UI resource URI uri: string; // Matching UI resource URI
mimeType: "text/html"; // MUST be "text/html" mimeType: "text/vnd.mcp.ui+html"; // MUST be "text/vnd.mcp.ui+html"
text?: string; // HTML content as string text?: string; // HTML content as string
blob?: string; // OR base64-encoded HTML blob?: string; // OR base64-encoded HTML
_meta?: { _meta?: {
@ -85,7 +85,7 @@ The resource content is returned via `resources/read`:
#### Content Requirements: #### Content Requirements:
- URI MUST start with `ui://` scheme - URI MUST start with `ui://` scheme
- `mimeType` MUST be `text/html` (other types reserved for future extensions) - `mimeType` MUST be `text/vnd.mcp.ui+html` (other types reserved for future extensions)
- Content MUST be provided via either `text` (string) or `blob` (base64-encoded) - Content MUST be provided via either `text` (string) or `blob` (base64-encoded)
- Content MUST be valid HTML5 document - Content MUST be valid HTML5 document
@ -144,14 +144,14 @@ Example:
"uri": "ui://weather-server/dashboard-template", "uri": "ui://weather-server/dashboard-template",
"name": "weather_dashboard", "name": "weather_dashboard",
"description": "Interactive weather dashboard widget", "description": "Interactive weather dashboard widget",
"mimeType": "text/html" "mimeType": "text/vnd.mcp.ui+html"
} }
// Resource content with metadata // Resource content with metadata
{ {
"contents": [{ "contents": [{
"uri": "ui://weather-server/dashboard-template", "uri": "ui://weather-server/dashboard-template",
"mimeType": "text/html", "mimeType": "text/vnd.mcp.ui+html",
"text": "<!DOCTYPE html><html>...</html>", "text": "<!DOCTYPE html><html>...</html>",
"_meta": { "_meta": {
"ui/csp": { "ui/csp": {
@ -841,7 +841,7 @@ Servers SHOULD check client (host would-be) capabilities before registering UI-e
```typescript ```typescript
const hasUISupport = const hasUISupport =
clientCapabilities?.extensions?.["io.modelcontextprotocol/ui"]?.mimeTypes?.includes("text/html"); clientCapabilities?.extensions?.["io.modelcontextprotocol/ui"]?.mimeTypes?.includes("text/vnd.mcp.ui+html");
if (hasUISupport) { if (hasUISupport) {
// Register tools with UI templates // Register tools with UI templates
@ -925,7 +925,7 @@ This proposal synthesizes feedback from the UI CWG and MCP-UI community, host im
#### 3. Support Raw HTML Content Type #### 3. Support Raw HTML Content Type
**Decision:** MVP supports only `text/html` (rawHtml), with other types explicitly deferred. **Decision:** MVP supports only `text/vnd.mcp.ui+html` (rawHtml), with other types explicitly deferred.
**Rationale:** **Rationale:**