What problem does it solve?
Building an MCP App (a tool plus an interactive UI resource) is hard to get right because you must correctly wire tool output to a bundled, host-renderable HTML resource and follow the SDK’s lifecycle and security constraints.
Core Features & Use Cases
- Tool + Resource pairing: Guides you to link a tool’s
_meta.ui.resourceUri to a registered UI resource so hosts can render rich interactive content.
- Framework-aware scaffolding: Shows how to structure implementations for React (via
useApp) and common vanilla or framework-based alternatives.
- Correct lifecycle and host integration: Explains handler registration order, app lifecycle events, host context/style handling, and UI behavior patterns for robust, host-compatible apps.
- Practical patterns and testing: Covers advanced App patterns (visibility, streaming input, view state, fullscreen mode, error handling) and how to test locally using a basic MCP Apps host.
Quick Start
Ask the AI to create an MCP App for my existing MCP tool, using the MCP Apps SDK, register the UI resource, and provide a React or vanilla template with the required lifecycle handlers and CSP configuration.