modelcontextprotocol / modelcontextprotocol/ext-apps
Documentation for MCP Apps does not match 2026-07-28 specification
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 387
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 6
Description
The specification and documents still refers to "initialize"
It does not describe out how to add the ui extension in the client request for capabilities _meta structure per client call for the 2026-07-28 specification
https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx
{
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {
"extensions": {
"io.modelcontextprotocol/ui": {
"mimeTypes": ["text/html;profile=mcp-app"]`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with specification/2026-01-26/apps.mdx and compare its initialize example with the 2026-07-28 specification. Check how the client request describes the UI extension and the capabilities _meta structure for each call. Done means the specification and documentation use the current terminology and show the required request structure.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100