Build dashboardsout of MCP Apps
Every MCP App is a widget. Pick the ones your team relies on — budgets, pipeline, incidents, anything with an MCP server — arrange them on a dashboard, and share it with the whole organization.
Ops overview
Live apps from your team's MCP servers.
Budget Allocator
MCP AppSales Pipeline
MCP AppIncidents
MCP AppToggle apps on the left to add or remove widgets — that's the whole flow.
Widgets from any MCP server
If an MCP server ships an app, it's a widget. Connect it once and it's ready to drop onto a dashboard.
Live and interactive
Widgets are real UI, not screenshots. Filter, drill in, approve, adjust — right on the dashboard.
One dashboard, the whole org
Compose it once in the admin panel and toggle it on for everyone. It appears in each member's OpenWork.
Connect. Compose. Share.
Connect an MCP server
Add any MCP server that ships an app under Connectors. OpenWork detects the app automatically.
Compose a dashboard
Create a dashboard, add the widgets you want, arrange them.
Share it
Toggle it on for the organization or specific teams. Members see it the next time they open OpenWork.
Widgets are just MCP Apps.
MCP that returns UI
MCP Apps extend the Model Context Protocol: a tool returns an interactive interface, and the host renders it. That interface is your widget.
Open standard
Build to the spec once and it runs in OpenWork and in every other host that implements MCP Apps. Apps built elsewhere work here too.
Private interactions
What happens inside a widget doesn't pass through the model. Enter credentials, approve a purchase, view sensitive data — safely.
Build your own
Follow the MCP Apps spec or point your agent at the reference repo. Next up: creating MCP Apps directly inside OpenWork.
Put your team's widgets on one screen
Compose your first dashboard in OpenWork Cloud, or build an MCP App and use it anywhere.