modelcontextprotocol / modelcontextprotocol/java-sdk
Feature Request: Support for MCP Apps Extension (UI capabilities)
Personne n'a encore pris cette issue.
- Langage dominant
- Java
- Étoiles
- 3.7k
- Forks
- 1.1k
- Merge moyen
- 1 j 15 h
- PR mergées (30 j)
- 9
Description
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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Lisez la spécification MCP Apps dans ext-apps/specification/2026-01-26/apps.mdx, comparez-la avec l'implémentation TypeScript et examinez la gestion des résultats d'outils et des capabilities dans Java SDK v0.17.2. Le travail est considéré comme terminé lorsque Java SDK dispose d'une implémentation validée pour détecter les capabilities d'Apps, exposer les données des ressources UI et prendre en charge tous les messages de protocole Apps requis.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- api, backend
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100