
OpenUI MCP Studio
io.github.xiaojiou176-openPublished by GitHub account xiaojiou176-openv0.3.0Updated Oct 24, 2026
Local stdio MCP for UI briefs to React + shadcn with review, proof, and ship.
Overview
Local stdio MCP server that turns a short UI brief into a styled React + shadcn surface with screenshots, accessibility checks and proof attached.
- What you can do
- Turn a one-paragraph UI brief into a styled React + shadcn surface
- Preview, diff and export generated UI locally
- Reuse shadcn-aligned components themed for proof workflows
- Apply versioned, diffable schemas for brief, render and proof
- Run snapshot tests, accessibility checks and design-token guardrails
- When to use it
- Useful when you want an assistant to draft React + shadcn interfaces from a written brief and keep the result reviewable, with previews, diffs and accessibility checks rather than unverified output.
- Requirements
- Runs as a local stdio process on the user's machine (desktop only). Installed by cloning the repository and following the per-stack quickstart in INSTALL.md or docs; no login or package registry install is described. No environment variables or headers are declared.
Installation
In SourceWeft
- Open OpenUI MCP Studio in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ShadcnBrief
brief in, React + shadcn out, proof attached
[Stars] [Last Commit] [License]
What You Get • Install • How It Work • Ecosystem
ShadcnBrief takes a one-paragraph brief and produces a styled React + shadcn surface — with screenshots, accessibility checks, and proof attached. Open-source MCP studio, batteries included.
MCP-driven UI generator. Brief, render, diff, ship.
What You Get
[!IMPORTANT] Local-first by default. No silent telemetry. No cloud round-trip. Your data stays on your machine until you explicitly ship it somewhere.
Install
Three commands. No curl | sh. No login. Read what you run.
Install break? Open your favorite agent and say "Read AGENTS.md and bootstrap ShadcnBrief for me." Agent fix own brain. Long version: docs/.
How It Work
The repo is seven layers — exactly the seven commits in git log. New work goes in as small named PRs. No 50-file mystery commits.
git log reads like a building floor plan. Look once, know the whole shape.
Ecosystem
ShadcnBrief lives in the open family: three open platforms. local-first, source-first, builder-first.
Cross-family taste: BeamMe · BrewMe · OpenVibeCoding · proofyard.
Star This Repo
If ShadcnBrief saves you a click, an hour, or a headache — star costs zero. Fair trade. ⭐
Also by Yifeng[Terry] Yu
- OpenCampus — Canvas + Gradescope + EdStem on one calm desk
- OpenVibeCoding — AI codes overnight, you ship in the morning
- BeamMe — beam your agent config to any planet
- BrewMe — wake up, news already brewed
- proofyard — every claim ships with its receipt
License
MIT — small print, big freedom.
Source: README.md at commit 590711f
Tools
0Version history
1- v0.3.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts