Is io.github.xiaojiou176-open/openui-mcp-studio safe to use?

io.github.xiaojiou176-open/openui-mcp-studio has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.xiaojiou176-open/openui-mcp-studio?

io.github.xiaojiou176-open/openui-mcp-studio can be installed by cloning its GitHub repository and following the setup instructions in the README.

Is io.github.xiaojiou176-open/openui-mcp-studio actively maintained?

io.github.xiaojiou176-open/openui-mcp-studio is actively maintained — last commit was 2 days ago. It has 1 GitHub stars.

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

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

ActiveNot tested

Other

★ 1GitHub

28DNo CVEsactive

Quick Install

{
  "mcpServers": {
    "io-github-xiaojiou176-open-openui-mcp-studio": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Setup guide

No install config available. Check the server's README for setup instructions.

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-xiaojiou176-open-openui-mcp-studio)](https://mcppedia.org/s/io-github-xiaojiou176-open-openui-mcp-studio)

Should you use this server?

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

✓

Is it safe?

No package registry to scan.

No authentication — any process on your machine can connect.

License not specified.

✓

Is it maintained?

Last commit 2 days ago. 1 stars.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

OpenUI MCP Studio

Turn one UI or UI/UX brief into React + shadcn files, then keep proof, review, and acceptance visible before you ship them.

OpenUI MCP Studio is the repo-first front door for teams using Codex, Claude Code, OpenCode, OpenClaw, and other MCP-first clients when they want one practical brief -> files -> proof -> review -> ship workflow instead of a generic coding-agent platform.

One-Screen Answer

If you only read one screen, keep these four answers in view:

Question	Current truthful answer
What is this?	A repo-first UI delivery workflow that turns a brief into React + shadcn files, then keeps proof, review, and acceptance visible before ship.
Where should I start?	Pages Front Door -> Proof Desk -> `npm run demo:ship`
Why trust it?	The repo keeps one visible proof path, one real demo command, and explicit quality gates instead of stopping at a screenshot or raw text blob.
What is it not claiming?	Not a generic coding-agent platform, not a managed hosted UI SaaS, and not an Official MCP Registry listing today.

Start Here In 60 Seconds

Keep the first pass single-threaded:

Open the Pages Front Door to get the product sentence and guided route.
Open the Proof Desk to see what the repo actually proves today.
Run npm run demo:ship when you want one repo-local brief-to-ship payload.
Only after those three make sense, branch into distribution, integrations, manifests, and install bundles.

Why This Reads Faster Now

The product sentence comes first: one brief becomes a reviewable React + shadcn delivery path.
The first route comes second: front door -> proof desk -> one runnable demo.
The first visible proof comes third: a repo-owned workflow visual plus a real demo:ship lane.
The second ring stays second ring: packaging, descriptors, bundles, and host shelves stay available without taking over the storefront.

Naming And Boundary Truth

OneClickUI.ai is the shorter front-door label.
OpenUI MCP Studio remains the technical product, runtime, and release name.
Primary runtime: local stdio MCP through services/mcp-server/src/main.ts.
Primary distribution artifact: this public GitHub repo, plus repo-owned install bundles and proof surfaces.
English is the canonical source of truth for repository governance and maintenance.

OpenUI MCP Studio is the public repo for MCP-native UI delivery and review across Codex, Claude Code, OpenCode, OpenClaw, and other MCP-first clients.

Second-Ring Questions

After the canonical first route is clear, use the matching second-ring shelf:

If your question is...	Start here
"What does the repo do in one screen?"	`README.md` and the Pages Front Door
"How do I install, submit, or package this truthfully?"	[`D

... View full README on GitHub

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Score Breakdown

MCPpedia Score

Click each category to see evidence

28D

Last scored 8h ago

How we score →

Security

3/30

No known vulnerabilities.

○

Known CVEs — No package registry to scan

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

✓

Tool stability — Tool definitions stable

○

Dependency health — No package to analyze

✗

License — No license specified

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.xiaojiou176-open/openui-mcp-studio safe to use?: io.github.xiaojiou176-open/openui-mcp-studio has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.xiaojiou176-open/openui-mcp-studio?: io.github.xiaojiou176-open/openui-mcp-studio can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.xiaojiou176-open/openui-mcp-studio?: io.github.xiaojiou176-open/openui-mcp-studio is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.
Is io.github.xiaojiou176-open/openui-mcp-studio actively maintained?: io.github.xiaojiou176-open/openui-mcp-studio is actively maintained — last commit was 2 days ago. It has 1 GitHub stars.

Similar servers

View all →

Memory MCP Server

Official

No CVEs98A

Persistent memory using a knowledge graph

5 toolsstdio83.8k93.5k/wk1d ago

Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.

No CVEs95A

Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.

5 toolsremote398685.9k/wk11h ago

Context Mode

No CVEs95A

Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.

6 toolsremote7.3k10.0k/wk23h ago

Browser Tools Mcp

No CVEs94A

Monitor browser logs directly from Cursor and other MCP compatible IDEs.

7 toolsremote7.2k2.9k/wk28d ago

MCP Security Weekly

Get CVE alerts and security updates for io.github.xiaojiou176-open/openui-mcp-studio and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?