220 pages for render.

MCP Apps Model Context Protocol · in the page extensions/apps/overview # MCP Apps > Interactive UI applications that render inside MCP hosts like Claude Desktop > [!TIP] > > For comprehensive API documentation, advanced patterns, and the full specification, visit the [… Extension Support Matrix Model Context Protocol · in the page extensions/client-matrix …view.md) | `io.modelcontextprotocol/ui` | Interactive HTML interfaces rendered inline in the conversation | | [OAuth Client Credentials](/extensions/auth/oauth-client-credentials.md) | `io.modelcontex… MCP Registry Supported Package Types Model Context Protocol · in the page registry/package-types …of an `mcp-name: $SERVER_NAME` string in the package README (which is rendered to HTML and served by crates.io's static CDN). The `$SERVER_NAME` portion **MUST** match the server name from `server.jso… SEP-1036: URL Mode Elicitation for secure out-of-band interactions Model Context Protocol · in the page seps/1036-url-mode-elicitation-for-secure-out-of-band-intera …tructured, in-band requests (most commonly imagined as the MCP client rendering a form to collect data from the end-user). However, several critical use cases require interactions that must not pass t… SEP-1865: MCP Apps - Interactive User Interfaces for MCP Model Context Protocol · in the page seps/1865-mcp-apps-interactive-user-interfaces-for-mcp …ons * **Predeclared templates**: Hosts can review HTML content before rendering * **Auditable messages**: All UI-to-host communication goes through loggable JSON-RPC * **User consent**: Hosts can requ… SEP-2484: Require Conformance Tests for Standards Track SEPs to Reach Final Status Model Context Protocol · in the page seps/2484-conformance-tests-required-for-final-seps …thub.com/modelcontextprotocol/conformance/issues/N - text: "MUST be rendered in a monospace font" excluded: "Client rendering; not observable at the protocol level" ``` Structured data lets too… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …er` | Yes | Verbatim copy of the skill's `SKILL.md` YAML frontmatter, rendered as JSON. See [Frontmatter](#frontmatter). | | `skills[].uri` | Yes | Resource URI of the skill's `SKILL.md`. See [Skill U… SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts Model Context Protocol · in the page seps/973-expose-additional-metadata-for-implementations-res …o an icon URL or a base64-encoded data URI * * Clients that support rendering icons MUST support at least the following MIME types: * - image/png - PNG images (safe, universal compatibility) * - i… Schema Reference Model Context Protocol · in the page specification/2025-06-18/schema …prompt or tool call result.</p> <p>It is up to the client how best to render embedded resources for the benefit of the LLM and/or the user.</p> </div> <section class="tsd-panel tsd-member"> <div cla… Overview Model Context Protocol · in the page specification/2025-11-25/basic/index …con background **Required MIME type support:** Clients that support rendering icons **MUST** support at least the following MIME types: * `image/png` - PNG images (safe, universal compatibility) *… Elicitation Model Context Protocol · in the page specification/2025-11-25/client/elicitation …iguous/suspicious URIs (i.e., containing Punycode). 7. **SHOULD NOT** render URLs as clickable in any field of an elicitation request, except for the `url` field in a URL elicitation request (with the… Schema Reference Model Context Protocol · in the page specification/2025-11-25/schema …prompt or tool call result.</p> <p>It is up to the client how best to render embedded resources for the benefit of the LLM and/or the user.</p> </div> <section class="tsd-panel tsd-member"> <div cla… Overview Model Context Protocol · in the page specification/2026-07-28/basic/index …con background **Required MIME type support:** Clients that support rendering icons **MUST** support at least the following MIME types: * `image/png` - PNG images (safe, universal compatibility) *… Elicitation Model Context Protocol · in the page specification/2026-07-28/client/elicitation …iguous/suspicious URIs (i.e., containing Punycode). 7. **SHOULD NOT** render URLs as clickable in any field of an elicitation request, except for the `url` field in a URL elicitation request (with the… Specification Model Context Protocol · in the page specification/2026-07-28/index …rview.md)**: Interactive UI elements (charts, forms, video players) rendered inline within conversations ## Security and Trust & Safety The Model Context Protocol enables powerful capabilities thr… Schema Reference Model Context Protocol · in the page specification/2026-07-28/schema …prompt or tool call result.</p> <p>It is up to the client how best to render embedded resources for the benefit of the LLM and/or the user.</p> </div> <div class="tsd-comment tsd-typography"> <detai… Overview Model Context Protocol · in the page specification/draft/basic/index …con background **Required MIME type support:** Clients that support rendering icons **MUST** support at least the following MIME types: * `image/png` - PNG images (safe, universal compatibility) *… Elicitation Model Context Protocol · in the page specification/draft/client/elicitation …iguous/suspicious URIs (i.e., containing Punycode). 7. **SHOULD NOT** render URLs as clickable in any field of an elicitation request, except for the `url` field in a URL elicitation request (with the… Specification Model Context Protocol · in the page specification/draft/index …rview.md)**: Interactive UI elements (charts, forms, video players) rendered inline within conversations ## Security and Trust & Safety The Model Context Protocol enables powerful capabilities thr… Schema Reference Model Context Protocol · in the page specification/draft/schema …prompt or tool call result.</p> <p>It is up to the client how best to render embedded resources for the benefit of the LLM and/or the user.</p> </div> <div class="tsd-comment tsd-typography"> <detai…