add-app-to-server

Enrich MCP server tools with interactive HTML UIs via the MCP Apps SDK.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/jbandi/mcp-apps-demo --skill add-app-to-server-jbandi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-app-to-server
Source: https://github.com/jbandi/mcp-apps-demo/tree/main/.agents/skills/add-app-to-server
Command: npx skills add https://github.com/jbandi/mcp-apps-demo --skill add-app-to-server-jbandi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enrich MCP server tools with interactive UIs, enabling richer user experiences without abandoning existing text-based workflows.

Core Features & Use Cases

  • UI-enabled tools: wrap existing MCP Server tools with interactive HTML UIs linked via _meta.ui.resourceUri.
  • Seamless fallbacks: UI is optional; text-only responses remain supported.
  • Resource-driven UI: UI resources can be hosted from a dedicated HTML asset and loaded into an iframe in the host.

Quick Start

Wrap an existing MCP tool with a UI resource and load it in the host iframe.

Frequently Asked Questions about add-app-to-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add interactive UI to MCP server tools?▼

You can add interactive UI to MCP server tools by wrapping existing tools with UI resources using the MCP Apps SDK, linking the UI via the _meta.ui.resourceUri property.

Can I keep text-based responses for MCP server tools that also have a UI?▼

Yes, MCP server tools with interactive UIs maintain seamless text fallbacks. The UI is optional, ensuring text-only clients still receive standard tool responses.

How does resource-driven UI work in the MCP Apps SDK?▼

Resource-driven UI in the MCP Apps SDK works by hosting HTML assets as dedicated UI resources, which are then loaded into an iframe within the host application environment.

Do I need to register App tools and resources to enable UI integration?▼

Yes, enabling UI integration requires using the app tooling APIs to register App tools and resources, handling the distinction between UI-capable and text-only clients.

What is the best way to convert plain MCP tools into UI-enabled experiences?▼

The best way to convert plain MCP tools into UI-enabled experiences is using the MCP Apps SDK to wrap existing tools with interactive HTML UIs linked via _meta.ui.resourceUri.