# OpenUI MCP Studio

> OneClickUI.ai is the front door for OpenUI MCP Studio: Turn UI/UX briefs into React + shadcn delivery with proof, review, acceptance, and next-step guidance.

frontdoor_label: OneClickUI.ai
technical_product: OpenUI MCP Studio
canonical_runtime: local stdio MCP
summary: Turn UI/UX briefs into React + shadcn delivery with proof, review, acceptance, and next-step guidance.
positioning: A stronger UI/UX execution, proof, and review companion for Codex and Claude Code workflows, without pretending to be a generic coding agent or hosted builder platform.
language: en-US
public_surface_language: en-US
default_locale: en-US
supported_locales: en-US, zh-CN
locale_cookie: openui_locale
ui_switch_scope: apps/web frontdoor routes and shared shell
bilingual_coverage_stage: frontdoor routes plus the proof desk, workbench shell, next-action guidance, pause guidance, dialog, success/error, and key state copy
category: spec-driven UI/UX delivery workbench
primary_bindings: MCP, Codex, Claude Code
secondary_comparisons: OpenHands, OpenCode
not_the_main_category: generic AI assistant, generic coding agent, hosted app builder
i18n_policy: English-first public pages and machine-readable routes; product UI can switch between en-US and zh-CN through centralized locale messages.

## Start here
- Front door: https://xiaojiou176-open.github.io/openui-mcp-studio/
  - role: front door
  - audience: first-time evaluators, builder traffic, and product-positioning readers
  - best_for: understanding the product sentence, the integration entry order, and where to route next without guessing
  - not_for: deep proof semantics, interactive operator work, or claiming hosted-deployment truth
  - boundary: Acts as the orientation surface only. It does not replace the proof desk, operator desk, or runtime protocol entrypoint.
- 30-second proof: https://xiaojiou176-open.github.io/openui-mcp-studio/proof
  - role: proof desk
  - audience: evaluators, reviewers, and first-time builders checking trust
  - best_for: sorting what the repo already proves, what still needs human judgment, and which route to open next
  - not_for: claiming Git landing, remote deployment, or final design sign-off already happened
  - boundary: Shows repo-owned proof tiers and next-step routing only; remote, live, and final release truth stay outside this desk.
- Alternatives and compare: https://xiaojiou176-open.github.io/openui-mcp-studio/compare
  - role: decision surface
  - audience: teams comparing OpenUI against hosted builders and broader coding-agent traffic
  - best_for: deciding whether repo-aware UI delivery with proof and review is the right job to optimize for
  - not_for: pretending all builder products belong in one category or benchmark matrix
  - boundary: Explains category fit only; it does not replace the proof desk or operator desk.
- First-minute walkthrough: https://xiaojiou176-open.github.io/openui-mcp-studio/walkthrough
  - role: guided route
  - audience: newcomers who want a short guided order before reading deeper docs
  - best_for: moving from front door to proof, workbench, and one real repo-owned command in a deliberate sequence
  - not_for: acting like a full tutorial center or a separate launch page
  - boundary: Keeps onboarding lightweight and route-aware; long-form explanation still belongs in docs.
- Open the operator desk: https://xiaojiou176-open.github.io/openui-mcp-studio/workbench
  - role: operator desk
  - audience: operators, maintainers, and active reviewers working the next repo-local packet
  - best_for: repo-local packet decisions, pause rules, and next-step guidance when proof still needs to stay attached
  - not_for: a live ops console, remote mutation surface, or source of deployed production truth
  - boundary: This is a repo-local simulated operator surface. It helps route decisions and evidence, but it is not a live operations console.
- README: https://github.com/xiaojiou176-open/openui-mcp-studio#readme
- Discovery guide: /docs#discovery-chain
- Docs index: /docs#docs-index
- Proof FAQ: /docs#proof-faq
- Walkthrough doc: /docs#first-minute-walkthrough
- Ecosystem contract: https://github.com/xiaojiou176-open/openui-mcp-studio/blob/main/docs/contracts/openui-ecosystem-productization.json

## Discovery chain
- Step 1. README storefront: https://github.com/xiaojiou176-open/openui-mcp-studio#readme
  - role: first GitHub impression
  - best_for: Explain what the product is, who it is for, and where to go next without dropping visitors into source files.
- Step 2. Front door: https://xiaojiou176-open.github.io/openui-mcp-studio/
  - role: orientation surface
  - best_for: Introduce the product sentence, guided paths, builder order, and the shortest trust ladder.
- Step 3. First-minute walkthrough: https://xiaojiou176-open.github.io/openui-mcp-studio/walkthrough
  - role: guided route
  - best_for: Give newcomers the shortest recommended route from front door to proof, workbench, and one real repo-owned command.
- Step 4. Proof desk: https://xiaojiou176-open.github.io/openui-mcp-studio/proof
  - role: trust surface
  - best_for: Show what the repo already proves, what still needs human judgment, and which next route makes sense.
- Step 5. Operator desk: https://xiaojiou176-open.github.io/openui-mcp-studio/workbench
  - role: repo-local operator surface
  - best_for: Help an operator decide the next move once the proof meaning is already clear, without pretending to be a live control plane.
- Step 6. Docs discovery route: https://xiaojiou176-open.github.io/openui-mcp-studio/docs
  - role: human-readable docs hub
  - best_for: Keep README, proof FAQ, evaluator guidance, release shelf, and ecosystem ledgers inside one in-app discovery route instead of dumping visitors into GitHub blob pages.
- Step 7. Compare: https://xiaojiou176-open.github.io/openui-mcp-studio/compare
  - role: decision surface
  - best_for: Explain why OpenUI fits repo-aware UI shipping better than hosted builders or generic coding-agent traffic when category fit is still the open question.
- Step 8. Machine-readable discovery: https://xiaojiou176-open.github.io/openui-mcp-studio/llms.txt
  - role: short LLM summary
  - best_for: Expose the shortest English-first route, builder, and boundary summary for LLM, search, and tooling consumers.
- Step 9. Frontdoor JSON: https://xiaojiou176-open.github.io/openui-mcp-studio/api/frontdoor
  - role: structured discovery contract
  - best_for: Expose routes, bindings, builder order, public bundle pointers, and operator-only follow-through in one JSON surface.
- Step 10. Manifest and crawl metadata: https://xiaojiou176-open.github.io/openui-mcp-studio/manifest.webmanifest
  - role: browser and crawler metadata
  - best_for: Expose install metadata plus manifest, sitemap, and robots hints for browsers and crawler-adjacent tooling.

## Builder-facing surfaces
- 1. stdio MCP server: Current primary integration surface for Codex, Claude Code, and other MCP clients.
  - audience: Codex, Claude Code, and other MCP-native builder clients
  - best_for: the primary prompt-to-workspace integration path when the team wants real React UI delivery with proof and review still attached
  - read_when: Read this first when you need the canonical execution path for Codex, Claude Code, or another MCP client.
  - not_for: people looking for a hosted builder, SDK, plugin runtime, or remote write-capable control plane
- 2. compatibility OpenAPI: Current builder-facing bridge surface for review, contract checks, and compatibility consumers; not a hosted API promise.
  - audience: bridge consumers, contract reviewers, and builder teams auditing shape
  - best_for: reviewing route contracts and compatibility semantics without treating the repo like a hosted API product
  - read_when: Read this second when the MCP entry order is already clear and you need a schema-oriented compatibility view.
  - not_for: claiming the repo already exposes a public hosted API or a write-anywhere runtime
- 3. repo-local workflow CLI: Current maintainer-facing product surface for read-only workflow packets and release-readiness summaries.
  - audience: maintainers and reviewers reading repo-local readiness packets
  - best_for: operator-facing readiness summaries and repo-local workflow evidence that stays read-only by default
  - read_when: Read this third when the question becomes readiness, handoff, or check-review state instead of raw execution.
  - not_for: pretending the repo will mutate remote state, land a PR, or replace GitHub operations by itself
- compatibility OpenAPI URL: https://github.com/xiaojiou176-open/openui-mcp-studio/blob/main/docs/contracts/openui-mcp.openapi.json

## Later lanes, not current promises
- official catalog or marketplace listing
- registry publication for supporting package surfaces
- managed hosted deployment
- remote write-capable MCP

## Machine-readable discovery
- llms.txt: https://xiaojiou176-open.github.io/openui-mcp-studio/llms.txt
  - audience: LLM clients, search/index systems, and builders needing the shortest truth layer
  - best_for: the English-first snapshot of route roles, builder order, and current boundaries
  - read_when: Open this when an agent or search/index system needs the shortest product and route summary before reading deeper docs.
  - not_for: interactive proof, operator work, or long-form command semantics
- frontdoor JSON: https://xiaojiou176-open.github.io/openui-mcp-studio/api/frontdoor
  - audience: builder tooling, agents, and contract-aware integrators
  - best_for: routes, bindings, audience fit, i18n posture, and boundary metadata in one machine-readable payload
  - read_when: Open this after the product sentence is clear and you need a structured discovery contract for tooling or integration work.
  - not_for: inventing a new runtime or claiming the repo already exposes a hosted builder control plane
- manifest.webmanifest: https://xiaojiou176-open.github.io/openui-mcp-studio/manifest.webmanifest
  - audience: browsers, install surfaces, and crawler-adjacent discovery consumers
  - best_for: front-door route shortcuts and install/discovery metadata that point to the same honest product roles
  - read_when: Open this when you need browser-facing install metadata and route shortcuts, not the full builder or proof explanation.
  - not_for: turning the app into a deployed canonical hosted truth or replacing the proof desk
- sitemap.xml: https://xiaojiou176-open.github.io/openui-mcp-studio/sitemap.xml
  - audience: crawlers and maintainers checking canonical route exposure
  - best_for: the canonical crawl map for the public front-door routes when NEXT_PUBLIC_SITE_URL is configured
  - read_when: Open this when you need the crawl map and canonical route exposure, not the longer product narrative.
  - not_for: expressing product boundaries in detail or replacing route-role metadata
- robots.txt: https://xiaojiou176-open.github.io/openui-mcp-studio/robots.txt
  - audience: crawlers and maintainers checking whether indexing should be enabled
  - best_for: the explicit crawl policy that pairs with sitemap exposure and canonical site gating
  - read_when: Open this when you need to confirm whether the front door is currently indexable, not when you need the longer product narrative.
  - not_for: explaining route roles, builder order, or replacing the proof and docs surfaces

## Ecosystem productization
- Public Skills starter kit: current-packaging
  - audience: maintainers and builders drafting future skill-shaped integrations
  - best_for: installable starter contracts, manifests, and examples that stay honest about the current builder surface
  - read_when: Open this after the main MCP, OpenAPI, and workflow surfaces are clear and you need a formal public starter contract.
  - not_for: claiming a marketplace listing, hosted Skills runtime, or vendor-approved plugin catalog
- Codex and Claude plugin-grade public package: official-surface-ready
  - audience: Codex and Claude Code users who install local MCP servers
  - best_for: configuration snippets, starter bundles, proof loop, and discovery metadata that make local MCP installation feel productized
  - read_when: Open this when the next question is how to add OpenUI to Codex or Claude Code without inventing an official plugin marketplace story.
  - not_for: claiming a Codex marketplace item or a published Claude Code plugin before those artifacts exist
- OpenClaw public-ready bundle: clawhub-ready
  - audience: OpenClaw-side builders and operators who need a discoverable repo-owned install and proof path
  - best_for: starter config, proof loop, and machine-readable discovery artifacts while the live ClawHub page stays visible but still under moderation warning
  - read_when: Open this when the next question is how to present OpenUI honestly to OpenClaw-side users without pretending the listed-live page is trust-cleared approval.
  - not_for: claiming an official OpenClaw runtime, trust-cleared ClawHub approval, or vendor approval
- Hosted client SDK: supporting-parked
  - audience: developers evaluating future thin-client or package surfaces
  - best_for: installing a thin HTTP client for the self-hosted OpenUI Hosted API with explicit auth and boundary semantics
  - read_when: Open this when the question becomes how to call the self-hosted HTTP surface from code.
  - not_for: claiming registry publication, front-door primary status, or replacing the local stdio MCP runtime
- Self-hosted OpenUI Hosted API: supporting-parked
  - audience: adapter authors and future hosted-surface planners
  - best_for: running an authenticated HTTP surface with discovery, workflow, and tool endpoints around the current repo-owned runtime
  - read_when: Open this after the compatibility bridge semantics are clear and you need a real self-hosted service/runtime surface.
  - not_for: claiming a managed SaaS deployment, front-door primary status, control plane, or remote write surface

## Public bundle
- Visual proof assets:
  - openui-mcp-studio-demo.gif
  - openui-mcp-studio-workbench.png
  - openui-mcp-studio-comparison.png
  - openui-mcp-studio-trust-stack.png
  - openui-mcp-studio-use-cases.png
  - openui-mcp-studio-visitor-paths.png
  - openui-mcp-studio-social-preview.png
- Narrative docs:
  - README.md
  - docs/discovery-surfaces.md
  - docs/proof-and-faq.md
  - docs/evaluator-checklist.md
  - docs/public-surface-guide.md
  - docs/release-template.md
  - examples/public-distribution/README.md
- Plugin-grade bundles:
  - .claude-plugin/marketplace.json
  - examples/codex/marketplace.sample.json
  - plugins/openui-workspace-delivery/.claude-plugin/plugin.json
  - plugins/openui-codex-delivery/.codex-plugin/plugin.json
- Machine-readable discovery:
  - /llms.txt
  - /api/frontdoor
  - /manifest.webmanifest
  - /sitemap.xml
  - /robots.txt

## Operator-only public surfaces
- GitHub Homepage
  - reason: Attach a real landing page or docs site only when that URL is verified live. Leaving Homepage blank is more honest than pointing at an unverified or misleading site.
- GitHub Social Preview
  - reason: Uploading or selecting the social preview image remains a GitHub settings action. Repo assets can prepare the image, but they cannot prove the setting is live by themselves.
- Published release proof bundle
  - reason: Draft releases and local assets can prepare the bundle, but publishing the release and refreshing attached assets is still a remote mutation step.
- Discussion seeding and curation
  - reason: Enabling Discussions is only the start. Keeping starter threads visible and current remains a GitHub/operator task.
- Domain, DNS, and TLS for OneClickUI.ai
  - reason: The repo can prepare the front-door story, but a real domain cutover still depends on external deployment, DNS, and certificate ownership.

## Honest boundaries
- not a hosted SaaS-first builder
- not a generic autonomous coding agent
- write-capable remote MCP is not the current promise
- Codex and Claude now have a repo-owned plugin-grade public package, and OpenClaw now has a repo-owned public-ready bundle
- the Skills starter pack remains current while @openui/sdk and the self-hosted Hosted API stay supporting or parked
- official listing, registry publication, and managed deployment remain later/operator-owned