Skip to content

docs(community): add MCP Apps Working Group charter - #3131

Draft
liady wants to merge 2 commits into
modelcontextprotocol:mainfrom
liady:mcp-apps-charter
Draft

docs(community): add MCP Apps Working Group charter#3131
liady wants to merge 2 commits into
modelcontextprotocol:mainfrom
liady:mcp-apps-charter

Conversation

@liady

@liady liady commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Charters the MCP Apps Working Group, sponsored by Lead Maintainer @dsp-ant, which owns the MCP Apps extension (SEP-1865, Final) along with its specification and SDK in modelcontextprotocol/ext-apps. The group has met tri-weekly since 2025-12-17 under Ido Salomon and Liad Yosef.

The charter follows the SEP-2149 template and the structure of the existing Registry and SDK charters: mission, scope, leadership, the standard authority table, membership, tri-weekly cadence, and the extension's active issues as deliverables. Out-of-scope items (host design systems, client implementation mandates, agent orchestration, core protocol changes) match the boundaries the group has held in practice.

Adds the page to the Working Group Charters nav group in docs.json. The mcp-apps-wg GitHub team and Discord role already exist in modelcontextprotocol/access, so no companion PR is needed there.

liady and others added 2 commits July 26, 2026 02:05
Adds the charter for the MCP Apps Working Group following the group
charter template, and registers it in the docs navigation.

The WG owns the MCP Apps extension (SEP-1865, Final), which defines
predeclared UI resources under the ui:// scheme, tool-to-UI association
via metadata, and bi-directional host/UI messaging over MCP's JSON-RPC
base protocol. The specification and SDK live in the ext-apps repository.

Scope, work items, and membership are grounded in the extension's live
issues and the group's public rolling agenda, which has recorded
tri-weekly meetings since 2025-12-17.
@dsp-ant

dsp-ant commented Jul 28, 2026

Copy link
Copy Markdown
Member

let me know when you ant this to be reviewed @liady

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants