orchestrui

OrchestrUI inspects a structured project profile, preserves compatible owners, and returns the smallest admissible UI composition with evidence for every decision.

Quick start

Requires Node.js 20+. Add the published read-only server to an MCP host:

{
  "mcpServers": {
    "orchestrui": {
      "command": "npx",
      "args": ["-y", "orchestrui@latest"]
    }
  }
}

git clone --depth 1 https://github.com/ECD5A/OrchestrUI.git
cd OrchestrUI
bash scripts/install-codex.sh

git clone --depth 1 https://github.com/ECD5A/OrchestrUI.git
Set-Location OrchestrUI
powershell -ExecutionPolicy Bypass -File scripts\install-codex.ps1

git clone https://github.com/ECD5A/OrchestrUI.git
cd OrchestrUI
npm ci && npm run check
npm run benchmark

Use them from a frontend project:

$ui-library-router plan the smallest compatible UI stack.
$ui-orchestrator implement the approved plan.
$ui-quality-audit audit the rendered result.

Related MCP server: UI Toolkit MCP Server

What it returns

{
  "input_mode": "structured-profiles",
  "selected": ["bklit-ui"],
  "owners": {
    "base-system": "host:shadcn-ui",
    "data-visualization": "bklit-ui"
  },
  "rejected": [{ "id": "daisyui", "rule": "base-system-conflict" }]
}

The committed suite passes 50/50 structured scenarios, 8/8 independently specified adversarial goldens, and three project fixtures in CI.

Skills and MCP

• ui-library-router — inspects the host and assigns role ownership.

• ui-orchestrator — integrates approved pieces into one visual contract.

• ui-quality-audit — checks coherence, accessibility, responsiveness, motion, performance, and licensing.

• Read-only MCP — list_libraries, recommend_stack, get_library_guidance, search_components, get_install_instructions, and audit_plan.

Published through npm, the official MCP Registry, and versioned GitHub Releases. Local plugin configuration is in .mcp.json; setup, architecture, security, licensing, and contribution details live in docs/, SECURITY.md, THIRD_PARTY.md, and CONTRIBUTING.md.

The MCP surface is read-only and uses public upstream metadata; implementation code and third-party assets remain in the host project.

Ecosystems

OrchestrUI is independent and is not affiliated with or endorsed by these upstream projects.

Support

If OrchestrUI helps your work, you can support its ongoing maintenance:

• TON: pointoncurve.ton

• Bitcoin (BTC): 1ECDSA1b4d5TcZHtqNpcxmY8pBH1GgHntN

• USDT (TRC20): TUF4vPdB6QkjCvZq18rBL4Qj4dK5ihCN75

Contact

For questions about OrchestrUI, integration, consulting, or collaboration: