Feature Request: Support for MCP Apps Extension (UI capabilities)
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 30/100
Rechercherichtung
Lies die MCP Apps-Spezifikation unter ext-apps/specification/2026-01-26/apps.mdx, vergleiche sie mit der TypeScript-Implementierung und untersuche die Verarbeitung von Tool-Ergebnissen und Capabilities im Java SDK v0.17.2. Als abgeschlossen gilt die Aufgabe, wenn das Java SDK eine abgestimmte Implementierung zur Erkennung von Apps-Capabilities, zur Bereitstellung von UI-Ressourcendaten und zur Unterstützung aller erforderlichen Apps-Protokollnachrichten hat.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Background
The MCP Apps extension was announced on January 26, 2026, bringing
interactive UI capabilities to the Model Context Protocol. This extension allows MCP servers to return rich, interactive user
interfaces (dashboards, forms, visualizations, etc.) that render directly in client applications.
According to the official blog post, MCP Apps enable
servers to deliver UIs through sandboxed iframes with bidirectional communication via JSON-RPC over postMessage.
Current Status
Currently, MCP Apps support appears to be available only in the TypeScript/JavaScript SDK
(@modelcontextprotocol/ext-apps). The Java SDK (v0.17.2 and earlier releases) does not appear to include support for the
Apps extension.
Use Case
We are building an MCP client application (MiniClaw) in Java using Spring Boot and the official Java MCP SDK (v0.17.2). We
would like to support MCP Apps to enable our users to interact with rich UIs provided by MCP servers, such as:
- Interactive data visualizations (charts, maps, 3D models)
- Multi-step forms and workflows
- Real-time dashboards and monitoring interfaces
- Document viewers and editors
Our frontend is built with Vue.js, and we're prepared to implement the client-side AppBridge integration. However, we need
the Java SDK to:
- Detect App capabilities from server responses (when a tool returns UI metadata)
- Parse and expose App-related data structures (UI resource declarations, iframe URLs, etc.)
- Support the extended protocol for Apps-related messages if any backend changes are required
Questions
- Is MCP Apps support planned for the Java SDK? If so, is there an estimated timeline or roadmap?
- What would be required to implement this? Are there specific protocol changes, new data structures, or APIs that need
to be added? - Can we contribute? If this is not currently prioritized, would the maintainers be open to community contributions?
We'd be happy to help implement this feature. - Workarounds? In the meantime, are there any recommended approaches for Java-based MCP clients to handle Apps responses
from servers?
Additional Context
- Java SDK version in use:
v0.17.2 - Client architecture: Spring Boot 3.4.5 + Vue.js 3 frontend
- We've reviewed the TypeScript implementation and AppBridge documentation
- We understand the client-side UI rendering will be handled in our frontend, but need backend SDK support for protocol
handling
References
Thank you for maintaining this excellent SDK! We appreciate any guidance or updates on this feature request.
- Vorherrschende Sprache
- Java
- Sterne
- 3.7k
- Forks
- 1.1k
- Ø Merge
- 1 T. 15 Std.
- Gemergte PRs (30 T.)
- 9
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus modelcontextprotocol/java-sdk
-
area/transport bug P2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
modelcontextprotocol/java-sdk#1136 ·
-
area/client bug P2
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
modelcontextprotocol/java-sdk#1124 · 1 Kommentar ·
-
ServerCapabilities.logging is added unconditionally, overriding the caller's explicit capabilities Offenbug P2 ready for work
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
modelcontextprotocol/java-sdk#1086 · 1 Kommentar ·
-
enhancement good first issue P3
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
modelcontextprotocol/java-sdk#1067 ·
-
bug P2 ready for work
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
modelcontextprotocol/java-sdk#898 · 1 Kommentar ·
Alle Issues in modelcontextprotocol/java-sdk
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
elastic/gradle-plugins#157 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
cryptomator/hub#497 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
johanhaleby/occurrent#1120 ·