fix: use profile parameter for MIME type instead of suffix (#75)

Change MIME type from `text/html+mcp` to `text/html;profile=mcp-app`
to follow RFC 6838 recommendations for custom media types.

The `+suffix` format (like `text/html+mcp`) is intended for structured
syntax suffixes (e.g., `+json`, `+xml`) that describe the underlying
format. Since MCP Apps doesn't define a new syntax but rather a profile
of HTML, using a profile parameter is more semantically correct.

Fixes #59

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

Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Anton Pidkuiko 2025-12-04 18:28:58 +00:00 • committed by GitHub
commit 0af15322af
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -68,7 +68,7 @@ const getServer = async () => {
uri: "ui://raw",
title: "Raw UI Template",
description: "A simple raw HTML UI",
mimeType: "text/html+mcp",
mimeType: "text/html;profile=mcp-app",
},
rawHtml,
);
@ -99,7 +99,7 @@ const getServer = async () => {
uri: "ui://vanilla",
title: "Vanilla UI Template",
description: "A simple vanilla JS UI",
mimeType: "text/html+mcp",
mimeType: "text/html;profile=mcp-app",
},
vanillaHtml,
);
@ -130,7 +130,7 @@ const getServer = async () => {
uri: "ui://react",
title: "React UI Template",
description: "A React-based UI",
mimeType: "text/html+mcp",
mimeType: "text/html;profile=mcp-app",
},
reactHtml,
);