MCP-WIP: Is it possible to converge?

[asterd]

Hi everyone,

A colleague and I have developed a small extension to the MCP protocol designed to orchestrate UI components within a chat environment.

The main idea is to enable an agent to select the most appropriate widget for a user's request, if needed, from a pool of strictly-formatted declarative widget UI manifests. This allows the frontend to instantiate the chosen widget from its manifest, along with any optional parameters. The manifests are defined as MCP resources, serving as a unique source of truth. The widgets themselves are technology-agnostic, with specific frontend framework implementations (React, Flutter, etc.) bridged via dedicated SDKs.

Each widget can be seen as a part of a traditional application. Our client manages switching between widgets, context management, MCP connection, tool calls, and LLM invocation. The frontend SDK handles injecting user interactions and intents from the widget into the context (and the reverse path will be supported as well), in a manner similar to your state management approach.

From our understanding of this protocol, neither a dynamic widget selection mechanism nor cross-framework UI component standardization (outside of React) are natively supported.

Do you see potential points of convergence between our work and yours in the future?
Here is the link to our project: https://github.com/Andurilx64/mcp-wip