Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clarify MCP Apps behavior with code mode

Open
#668 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

No file, test, or entry point is named. Start by reviewing the MCP Apps specification's handling of UI tools and the host-side and server-side code-mode scenarios described here. Done means the specification clearly defines how UI views and tools are discovered and exposed in both scenarios.

Written by the indexing model from the issue text.

Description

needs spec change protocol

MCP Apps doesn't directly address either host-side or server-side code mode.

This leaves room for different interpretations of how UI tools should be exposed and fetched in these scenarios.

Host-side -
Should the Apps spec define how hosts should fetch views when the UI tools are discovered dynamically?

Server-side -
Should the Apps spec define how hosts should expose UI tools? For example, should UI tools always be exposed outside the code-mode paradigm to match naive host implementations?

Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
2h 54m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/ext-apps

All issues in modelcontextprotocol/ext-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.