add-app-to-server

Add interactive MCP Apps UI to existing MCP server tools with text fallback.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mrkhachaturov/jira-mcp-plugin --skill add-app-to-server-mrkhachaturov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-app-to-server
Source: https://github.com/mrkhachaturov/jira-mcp-plugin/tree/main/.agents/skills/add-app-to-server
Command: npx skills add https://github.com/mrkhachaturov/jira-mcp-plugin --skill add-app-to-server-mrkhachaturov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you enrich an existing MCP server’s tools with interactive UI so users get a richer, in-host experience instead of plain text only.

Core Features & Use Cases

  • Paired UI + text fallback: Adds an app UI resource for supported clients while keeping the tool usable for text-only hosts.
  • Tool selection and app-only helpers: Analyzes which tools should get UI and which endpoints should be app-only helpers (UI polling/fetching) instead of model-call tools.
  • Resource registration and theming: Guides registering HTML resources and integrating host styling using the MCP Apps SDK.
  • Framework-ready templates: Uses SDK templates (vanilla/React/Vue/Svelte/etc.) and a Vite + singlefile build pipeline to bundle UI safely for iframe rendering.

Quick Start

Use the add-app-to-server skill to identify which of your existing MCP tools should be UI-enhanced and generate the steps to wire each selected tool to an MCP Apps resourceUri.

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 an existing MCP server tool?

To add interactive UI to an existing MCP server tool, you pair tool calls with sandboxed HTML resources using the @modelcontextprotocol/ext-apps SDK to link _meta.ui.resourceUri, then build the UI via Vite singlefile for iframe rendering.

Can I keep text-only fallbacks for MCP tools when adding app UI?

Yes, you can keep text-only fallbacks for MCP tools by maintaining standard text outputs for non-UI hosts while simultaneously pairing the tool with an interactive HTML app resource for supported clients.

When should I use app-only helper tools instead of model-call tools in MCP?

You should use app-only helper tools instead of model-call tools when creating endpoints specifically for UI polling and fetching data, keeping them separate from tools the model directly invokes.

Does the MCP Apps SDK support React and Svelte templates for tool UI?

Yes, the MCP Apps SDK supports framework-ready templates including vanilla, React, Vue, and Svelte, using a Vite singlefile build pipeline to safely bundle the HTML for iframe rendering.

What is the best way to register HTML resources for interactive MCP apps?

The best way to register HTML resources for interactive MCP apps is using the registerAppTool and registerAppResource functions from the @modelcontextprotocol/ext-apps SDK while following host theming and handler lifecycle conventions.

What limitations exist when pairing MCP tools with sandboxed HTML app resources?

A key limitation is that sandboxed HTML app resources require UI-capable hosts to render the iframe, meaning text-only hosts will rely entirely on the text fallback and cannot display the interactive widget.