io.github.xiaojiou176-open/openui-mcp-studio

MCPcommunity
v0.3.0io.github.xiaojiou176-openUnknownUpdated 5mo agoGitHub

Local stdio MCP for UI briefs to React + shadcn with review, proof, and ship.

brief in, React + shadcn out, proof attached 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. | Brief → preview → diff → export. All local. | | Reusable shadcn-aligned components, themed for proof…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
5mo agoLast update
Package
Authorio.github.xiaojiou176-open
LicenseUnknown
Version0.3.0
Sourcemcp-registry
GitHubxiaojiou176-open/openui-mcp-studio
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface24 tools · 1 privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

24 tools · 1 privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

shadcn_brief_build_acceptance_packNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_apply_filesNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_observe_screenNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_execute_ui_actionprivilegedNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_computer_use_loopNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_convert_react_shadcnNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_make_react_pageNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_detect_shadcn_pathsNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_embed_contentNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_generate_uiNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_list_modelsNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_plan_changeNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_quality_gateNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_rag_upsertNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_rag_searchNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_refine_uiNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_repo_workflow_summaryNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_build_review_bundleNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_ship_feature_flowNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_ship_react_pageNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_next_smokeNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_review_uiuxNo description published

This tool published no description. Forge does not invent one.

shadcn_brief_scan_workspace_profileNo description published

This tool published no description. Forge does not invent one.

lookup_weatherNo description published

This tool published no description. Forge does not invent one.

0 of 24 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

brief in, React + shadcn out, proof attached 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. | Brief → preview → diff → export. All local. | | Reusable shadcn-aligned components, themed for proof workflows. | | Hand a brief to any agent through an MCP server. | | Schemas for brief, render, and proof —…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

24 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.