{{ message }}
docs(apps): list mcp-elements as a host-side framework option - #3341
Open
mayurrawte wants to merge 1 commit into
Open
docs(apps): list mcp-elements as a host-side framework option#3341mayurrawte wants to merge 1 commit into
mayurrawte wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Client support" section of the MCP Apps overview currently names one framework option for host builders (
@mcp-ui/client). This adds a one-line mention of mcp-elements, whoseMcpAppFrameis an independent host-side implementation of the SEP-1865 protocol (sandboxed iframe, CSP,ui/initializehandshake, JSON-RPC tool-call proxying) shipped as copy-paste source for React, Vue and Angular.Disclosure: I maintain mcp-elements. Happy to reword, shorten, or move it to the client matrix if that fits better.