Board
Columns of cards with labels, dates and people. Like a Trello board.
Pick a template, tune it in a preview that is a real MCP Apps host, and export it with a few lines of code. Or publish it and connect it to your agent in a minute.
How is the beta launch going?
Used show_kanban
Your widgets work in any MCP Apps host
From template to conversation without touching the protocol: Widgetry takes care of the server, the view and the security.
Board, KPIs, charts, a table, a countdown or a 3D globe, each with sample data so you see something from the first second.
Change the data, the design and the text. Want more? The markup, styles, script and schema are one click away.
The preview speaks the same MCP Apps protocol as the chats, in light and dark: what you see is what your agent will see.
Twenty built-in designs, fourteen of them inspired by well-known brands, plus a designer to make your own. Any widget type wears any design.
Link it from your MCP server so it gets every change you publish, download it as HTML and a manifest, or serve it from the Widgetry endpoint.
Connect your agent to the Widgetry MCP with edit access and just ask: it creates the widget from a template, tunes it, publishes it and can even make you a design.
Your server links to the widget published on Widgetry: one function registers the tool and its ui:// resource, and whatever you publish later reaches it with no redeploy. If you'd rather not depend on anyone, download it as HTML and a manifest. Tested with the official TypeScript SDK.
// Reads the widget published on Widgetry with a read key
import { registerKanban } from './kanban'
await registerKanban(server) // show_kanban and its ui:// resourceEvery type works with every design, and every organization can create its own. What you see here is the real widget with its sample data.
Type
Design: The house design: black outline, butter yellow and a marker swipe under the title.
Columns of cards with labels, dates and people. Like a Trello board.
A featured announcement with a headline, a figure and a button, dressed differently by each design.
A WebGL globe with three.js that spins on its own and can be dragged, with a dot per place.
Uses three
The weather for a place with animated SVG icons and the coming hours; each design paints its own sky.
Goals as SVG rings that fill up as they appear, with their percentage.
A series over time as an SVG curve with a gradient fill that draws itself in.
Cards on a ring that spins in 3D with CSS perspective. Pauses on hover.
Days, hours, minutes and seconds to an event, ticking live with a little jump.
Figures that count up from zero and cascade in, animated with GSAP.
Uses gsap
Parts of a whole with Chart.js: animates in and responds to the mouse.
Uses chartjs
A row of key figures with their change against the previous period.
Horizontal bars with their values, in the order they arrive.
Rows and columns with a sticky header; the caller decides the columns.
The widgets you publish are served from a single MCP endpoint, for the organization you choose.
url: https://…/mcp
header: Authorization: Bearer wgt_…An interactive interface that an agent draws inside the conversation when it calls a tool on an MCP server: in ChatGPT, Claude, VS Code, Goose and the other hosts of the open MCP Apps standard. Widgetry gives you the widget ready-made.
Not to get started: you pick a template, change the data and see the result. The markup, styles, script and data schema are there for anyone who wants to go further.
Yes. The usual way is to link it: your MCP server reads the widget published on Widgetry with a read key and gets every change you publish. If you'd rather not depend on Widgetry, download it as an HTML document and a manifest and register it with a few lines of the official SDK.
Yes. Connect your agent to the Widgetry MCP with edit access, through OAuth or with a write key, and it gets tools to create widgets from a template, change their markup, styles and data, publish them and create designs. You see them and polish them in the editor.
Publish the widget and connect the Widgetry MCP endpoint to your agent: clients that use OAuth sign in with your account, and the rest with an API key.
The model provides it: it gathers the data from other tools or from the conversation and calls the widget's tool with it. The data schema tells it what to send.
Yes, if you declare their domains in the widget. The chat host blocks any origin the widget doesn't declare, and the editor preview blocks the same ones.