widget-studio
MCP server that lets agents create, display, and export rich UI widgets (cards, dashboards, charts, forms) inline in conversations, with interactive iframe support in MCP Apps hosts and PNG image fallback for other clients.
README
widget-studio
An agent capability for creating and displaying rich UI widgets (cards, dashboards, task lists, charts, forms, tables) inline in conversations — packaged as a Claude Code plugin, an Agent Skill, standalone CLI scripts, and an MCP server with MCP Apps support. Widgets use the ChatKit widget JSON format, generated by prompting Widget Studio's hosted generator; the JSON is edited directly only for small tweaks.
Architecture
The MCP server is optional — the skills + CLI deliver the full generate→render loop on their own. The server is the layer that adds interactive inline widgets in MCP Apps hosts. Each host gets the richest rendering it supports:
| Layer | What it provides | Who uses it |
|---|---|---|
| Skills (skills/) | /widget-studio:make — how to prompt the generator well; :tweak — instant JSON edits + re-display; :preview — render saved JSON to PNG/HTML; :doctor — install/render/API health checks |
Any skills-capable agent |
| Reference (skills/make/references/chatkit-widgets.md) | ChatKit component schema for reading and making small edits to generated widgets before re-display | The model, on demand |
| Scripts (scripts/, bin/) | widget-generate (prompt → widget via hosted API), widget-render (JSON → PNG / standalone HTML), widget-export (→ .widget file for the Widget Studio editor) — self-locating, on PATH in plugin sessions |
The full capability, no MCP needed |
| MCP server (src/) | generate_widget, display_widget, and export_widget (.widget files) tools; interactive MCP Apps iframe with a copy/export action bar in capable hosts, automatic PNG fallback elsewhere |
MCP Apps hosts (interactive) + any other MCP client (PNG) |
| Evals (evals/) | Deterministic golden-render suite (npm run eval) + skill-creator-format LLM eval cases (skills/make/evals/evals.json) |
CI / skill iteration |
Rendering paths
- MCP Apps hosts (Claude Desktop, claude.ai, ChatGPT): interactive iframe via the
standard
_meta.ui.resourceUri→ui://widget-studio/widget.html, a fully self-contained HTML renderer (CSP-safe, light/dark, actions post back to chat). Legacyopenai/outputTemplatealias included for older ChatGPT builds. - Non-UI MCP clients (Claude Code CLI, others): the server detects the missing
MCP Apps capability at initialize and attaches a PNG image of the widget to the
tool result instead (see PNG rendering). Override with
WIDGET_STUDIO_IMAGE=auto|always|never. - No MCP at all:
widget-render(scripts/render-widget.mjs) produces the same PNG or a self-contained HTML preview from a widget JSON file.
Install
Note: the
npxforms and one-click badges below go live with the first npm release ofwidget-studio-mcp. Until then, use the from-source form — everything else is identical.
As a Claude Code plugin (recommended for Claude)
/plugin marketplace add ericlewis/widget-studio-mcp
/plugin install widget-studio@widget-studio
The plugin registers the MCP server, puts widget-generate/widget-render/widget-export
on PATH, and installs the skill family (/widget-studio:make, :tweak, :preview,
:doctor). dist/ ships self-contained bundles — no npm install needed.
MCP server, per host
<details><summary><b>Claude Code</b></summary>
claude mcp add widget-studio -- npx -y widget-studio-mcp@latest
</details>
<details><summary><b>Claude Desktop</b></summary>
claude_desktop_config.json (Settings → Developer → Edit Config):
{ "mcpServers": { "widget-studio": { "command": "npx", "args": ["-y", "widget-studio-mcp@latest"] } } }
</details>
<details><summary><b>Cursor</b></summary>
Use the install badge above, or .cursor/mcp.json:
{ "mcpServers": { "widget-studio": { "command": "npx", "args": ["-y", "widget-studio-mcp@latest"] } } }
</details>
<details><summary><b>VS Code</b></summary>
code --add-mcp '{"name":"widget-studio","command":"npx","args":["-y","widget-studio-mcp@latest"]}'
</details>
<details><summary><b>Codex CLI</b></summary>
codex mcp add widget-studio -- npx -y widget-studio-mcp@latest
Or ~/.codex/config.toml:
[mcp_servers.widget-studio]
command = "npx"
args = ["-y", "widget-studio-mcp@latest"]
</details>
<details><summary><b>Gemini CLI</b></summary>
As an extension (bundles the MCP server and skills):
gemini extensions install https://github.com/ericlewis/widget-studio-mcp
</details>
<details><summary><b>Windsurf</b></summary>
~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "widget-studio": { "command": "npx", "args": ["-y", "widget-studio-mcp@latest"] } } }
</details>
<details><summary><b>Goose</b></summary>
goose session --with-extension "npx -y widget-studio-mcp@latest"
</details>
<details><summary><b>Amp</b></summary>
amp mcp add widget-studio -- npx -y widget-studio-mcp@latest
</details>
<details><summary><b>ChatGPT (and other remote-only hosts)</b></summary>
ChatGPT connects to remote MCP servers only. Run the HTTP transport behind a tunnel or deploy, then add the URL under Settings → Connectors (developer mode):
npx -y widget-studio-mcp@latest --http 3400 # stateless streamable HTTP, POST /mcp
ChatGPT implements the MCP Apps standard natively, so widgets render
interactively; in --http mode the server also always attaches the PNG.
Bridge for stdio-only hosts hitting a remote:
npx -y mcp-remote https://your-host/mcp.
</details>
<details><summary><b>From source</b></summary><a name="from-source"></a>
git clone https://github.com/ericlewis/widget-studio-mcp && cd widget-studio-mcp
npm install && npm run build
claude mcp add widget-studio -- node "$(pwd)/dist/index.js" # or the equivalent for your host
</details>
PNG rendering
Built in — pure JS/WASM (satori + resvg with bundled Inter fonts). No browser, no playwright/puppeteer, no native dependencies, nothing to install.
Develop
npm run build # typecheck + bundle the iframe app and self-contained server into dist/
npm test # protocol smoke test (incl. one real API generation)
npm run eval # render golden fixtures to PNG + offline protocol checks
Manual preview of any widget JSON:
node scripts/render-widget.mjs --in evals/golden/sales-dashboard.json --png dashboard.png
node scripts/render-widget.mjs --in evals/golden/sales-dashboard.json --html dashboard.html
dist/ is committed on purpose: plugin installs copy the repo as-is, so the
bundles must ship prebuilt. Rebuild before committing changes under src/.
Notes
- The Widget Studio API is the unauthenticated hosted service behind the public
editor; requests carry a stable random user ID (
WIDGET_STUDIO_USER_IDto pin). - The renderer covers the full ChatKit component set; unknown components degrade to rendering their children. External images are blocked by host CSP in interactive mode (placeholder shown) but fine in PNG/HTML output.
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.
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.
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.
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.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
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.