Repository navigation
[FEATURE]: Add Support for MCP Apps in the desktop app #10884
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
With the Model Context Protocol (MCP) specification reaching stability for Apps (v2026-01-26), I suggest that OpenCode implements support for hosting and rendering MCP Apps.
While OpenCode is already a powerful terminal and Desktop APP, adding "MCP Apps" capabilities would allow it to launch and manage rich, interactive GUI applications. Instead of relying solely on text or Markdown, the agent could render a full React-based interface directly on the user's desktop app.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jan 27, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if this doesn't address your specific case.
JReinhold commentedon Jan 31, 2026
The announcement of the stabel release of the MCP Apps spec lists other clients' support, and it would be great to see Opencode in this list.
https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/
JairajSustained commentedon Feb 13, 2026
If this gets implemented, we could use excelidraw mcp server visually.
MarcSkovMadsen commentedon Mar 2, 2026
I would like to visialize anything using pyodide and python ecosystem provided by https://panel-extensions.github.io/panel-live/tutorials/getting-started-mcp/
tristan-stahnke-GPS commentedon Mar 4, 2026
@MarcSkovMadsen @JairajSustained : Can you see if my PR works for your use case?
vvcb commentedon Mar 31, 2026
Prefect are working on Prefab (https://prefab.prefect.io/docs/welcome) which looks fabulous and is worth investigating for integration here.
ilyes-i-ben commentedon May 7, 2026
+1
takeseem commentedon Jun 3, 2026
玩呢，还没支持 mcp
MaxiWeissenbacher commentedon Jun 10, 2026
+1
amirsaam commentedon Jun 25, 2026
+1
adrian-pattz commentedon Aug 4, 2026
+1, this is a big missing feature
iwiznia commentedon Aug 24, 2026
+1, this is a complete deal breaker for the desktop app.
sofianbll commentedon Oct 20, 2026
Hi @adamdotdevin (cc @jlongster for #53514) — following up on this issue and on @thdxr's request in #15926 to port MCP Apps to V2.
Before opening anything, I'd like design feedback on a small engine-only first increment. I built it as a throwaway local proof against
dev(6bac3b9) so the discussion has something concrete behind it:Proposed engine contract (no iframe/UI code in the engine)
state.metadata.mcp(toolMeta,resultMeta,structuredContent, andui: { resourceUri, mimeType, html, meta }). Model lowering readsstate.content, so the UI payload never reaches the model; embeddedui://HTML is removed from model-visible content.ui://URIs withtext/html;profile=mcp-app, via the same server connection, behind the existingopencode_read_mcp_resourcepermission.POST /api/session/:sessionID/mcp/call({ server, tool, arguments, messageID }) that reusespermission.assertwith the originating message's agent — no rawMcp.Service.callToolbypass; denial → 403, never a silent call.What the local proof shows (patches + reproducible CI): a model tool call renders an MCP App (an OpenUI counter) in a patched OpenChamber client, a click calls the server back through (3), a visible permission prompt can deny (no MCP call reaches the server) or approve, and the host CSP blocks undeclared network access — on web (Playwright CI) and once on macOS Electron.
Proof, patches and full proposal: https://github.com/sofianbll/opencode-standards-proof (see
PROOF.mdandproposals/opencode-mcp-apps-v2.md).Not claimed: this is not a released API, not full MCP Apps conformance, callback results are not persisted to history yet, and app-only tool visibility is not handled.
Questions
Happy to adapt or drop this — I won't open a PR without a go-ahead per CONTRIBUTING.