You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With MCPGATEWAY_MCP_APPS_ENABLED=true, ContextForge rejects the UI resource of a federated MCP server that follows the MCP Apps spec, so the app can't be rendered through the gateway. validate_ui_resource requires a non-empty sandbox list in _meta.ui, but sandbox is not a field of McpUiResourceMeta in the spec, so compliant servers never send it.
Versions
ContextForge v1.0.8 (same code on main at 7d6d7e2 / v1.1.1)
Upstream server: jgraph/drawio-mcp App Server 1.5.0 (ui://drawio/mcp-app.html)
MCP Apps spec (modelcontextprotocol/ext-apps, specification/2026-01-26 and draft/apps.mdx):
McpUiResourceMeta defines csp, permissions, domain and prefersBorder. There is no sandbox field. Iframe sandbox flags are the host's responsibility ("Rendering the MCP App": the host's iframe MUST have allow-scripts, allow-same-origin).
_meta.ui may be on the resources/list entry or on the resources/read content item: "Hosts MUST check both locations, preferring the content item and falling back to the listing entry". The server guidance prefers the content item.
drawio-mcp 1.5.0 follows the spec: resources/list has only mimeType: text/html;profile=mcp-app, and resources/read returns _meta.ui.csp (resourceDomains, connectDomains) with no sandbox. When the gateway syncs it, validation fails on both checks above. If the listing entry has no _meta.ui, it fails with "require MCP Apps metadata" before the read-time CSP is ever seen.
Steps to reproduce
Set MCPGATEWAY_MCP_APPS_ENABLED=true.
Register jgraph/drawio-mcp:1.5.0 (Streamable HTTP, /mcp) as a gateway and add its tools to a virtual server.
The ui://drawio/mcp-app.html resource is rejected, so MCP Apps-capable clients (e.g. Cursor, VS Code Copilot Chat) get only the tool's text and link, not the app.
Activity