mup-mcp-server
Enables LLM chat interfaces to load and interact with interactive UI components (MUPs) such as slides, PDF readers, and sound pads, allowing both users and the LLM to operate them through function calls.
README
MUP — Model UI Protocol
Bring interactive UI into LLM chat — so anyone can experience agentic AI, not just developers.
Current version: 0.2.11 | Protocol: mup/2026-03-17
Demos
Slides — AI builds a presentation live
Claude creates a full slide deck with charts, tables, and themes — all through function calls.
PDF to Presentation — AI reads a paper and presents it
Claude reads the AlexNet paper from a PDF, takes Markdown notes, captures figures with human-AI collaboration, builds a 19-slide presentation with charts and tables, then presents it slide by slide in the new in-panel reading mode — all narrated live.
Sound Pad — AI composes a track from scratch
16 browser-synthesized instruments, zero samples. Claude composes an electro swing track layer by layer, with event-driven narration synced to each section transition.
What is MUP?
A MUP is an interactive UI component that lives inside an LLM chat interface.
It bundles a visual interface with callable functions. The user operates it by clicking buttons; the LLM operates it through function calls. Both sides see each other's actions in real time.
The simplest MUP is a single .html file — no build step, no framework, no SDK.
Why?
Agentic AI is powerful, but today it's trapped behind text commands and developer tools. Most people never get to experience it.
MUP changes this. It puts clickable, visual UI right inside the chat — so anyone can use agentic capabilities without writing a single prompt.
| Traditional Chat | With MUP | |
|---|---|---|
| User interaction | Type text commands | Click buttons, drag sliders, see live visuals |
| Tool results | Hidden from user, only the LLM sees them | Visible and interactive for both sides |
| Who can use it | Power users who know the right prompts | Anyone |
Key Ideas
- Shared functions. A function can be called by the LLM (as a tool) or triggered by the user (via UI). Both sides operate on the same state through the same code.
- LLM as orchestrator. MUPs don't talk to each other. The LLM reads outputs and decides what to do next.
- Just HTML. Write a manifest, register your functions, done. Ship a single file.
Available MUPs
- Chat — Built-in, always available
- Slides — Presentation editor with charts, tables, themes, reading mode, and export (demo)
- PDF Reader — PDF viewer with page text extraction and region selection/capture
- Markdown — Markdown workspace with annotations and document management
- Sound Pad — 16-pad synthesizer with sequencer, per-track volume, and event system (demo)
- Chord Pad — Music theory keyboard with 5 synth voices, chord progressions, and melody playback
- Diagram — Auto-layouted node-and-edge diagrams (flowcharts, mind maps, architectures) with multiple layout algorithms
- Star Map — Location-based interactive star map with constellations, ecliptic, and Milky Way
- Voice — Speech synthesis and recognition (Jarvis mode)
- Notes — Sticky-note workspace with groups, styles, and export
- Pixel Art — Pixel canvas with shapes, ASCII patterns, fills, and PNG export
- Timer — Countdown timer / stopwatch with event-driven completion
- Progress — Task progress tracking
- More examples in
archive/examples/(games, productivity, etc.)
Focused Development
For iteratively building a single MUP with Claude (edit .html → Chrome hot reloads → user interacts → channel pushes back to Claude → repeat), see mup-mini-mcp-server — a scaffolding-style sibling that loads exactly one MUP and provides only the plumbing: hot reload, WebSocket bridge, and channel push. No catalog, no grid, no extras.
Docs
- Spec — Protocol definition: manifest, functions, lifecycle, error handling
- Design Philosophy — Why MUP is designed this way, and what we intentionally left out
- Examples — Example MUPs with walkthroughs
Install
npm (recommended)
npm install -g mup-mcp-server
Or run directly:
npx mup-mcp-server --mups-dir ./my-mups
Also available on the MCP Server Registry.
From source
git clone https://github.com/Ricky610329/mup.git
cd mup/mup-mcp-server
npm install && npm run build
Getting Started
With Claude Code (recommended)
claude mcp add --transport stdio --scope user mup -- npx mup-mcp-server
Restart Claude Code. A browser window opens at http://localhost:3200. Use the MUPs panel to load a folder of MUP .html files, or start with the built-in Chat widget.
Real-time channel mode
MUPs can push interactions directly into Claude's conversation via channel notifications. To enable:
claude --dangerously-load-development-channels server:mup
This lets MUPs deliver user actions to Claude in real time. Without this flag, all MUP features still work — interactions are just delivered via polling instead of push.
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"mup": {
"command": "npx",
"args": ["mup-mcp-server"]
}
}
}
Quick Example
<script type="application/mup-manifest">
{
"name": "Counter",
"description": "A counter. User clicks +/-, LLM can set or read the value.",
"functions": [
{
"name": "setCount",
"description": "Set the counter to a specific value",
"inputSchema": {
"type": "object",
"properties": { "value": { "type": "number" } },
"required": ["value"]
}
},
{
"name": "getCount",
"description": "Get the current counter value",
"inputSchema": { "type": "object", "properties": {} }
}
]
}
</script>
Drop this into a MUP-compatible host, and it works.
Architecture
┌──────────────────────────────────────────┐
│ MUP (.html file) │
│ manifest + UI + functions │
└──────────────────┬───────────────────────┘
│ loaded by
▼
┌──────────────┐
│ MCP Server │
│ (Claude Code │
│ / Desktop) │
└──────┬───────┘
│ WebSocket
▼
┌─────────────────────────────┐
│ Browser Panel │
│ (MUP grid + Chat widget │
│ + workspace manager) │
└─────────────────────────────┘
Star History
License
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.


