Skip to content

Add pinned shadcn MCP as the v1.2.0 UI registry hub - #3

Merged
kuker24 merged 2 commits into
mainfrom
v1.2.0-ui-hub
Aug 16, 2026
Merged

Add pinned shadcn MCP as the v1.2.0 UI registry hub#3
kuker24 merged 2 commits into
mainfrom
v1.2.0-ui-hub

Conversation

@kuker24

@kuker24 kuker24 commented Aug 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • Ship GrokBestFriend v1.2.0 with one enabled UI MCP: pinned npx -y shadcn@4.18.0 mcp.
  • Route component discovery through Impeccable (reference/ui-hub.md): search → inspect → pick one → install. Registries (@shadcn, @animate-ui, @aceternity, @react-bits, @kibo-ui, @magicui) stay behind that hub.
  • Keep 21st.dev, Magic UI MCP, Kibo MCP, and community UI servers out of policy. Require components.json before init/install.

Test plan

  • python3 tests/test-mcp-state.py
  • bash tests/test-source-integrity.sh
  • python3 tests/test-routing-eval.py
  • bash tests/test-doctor-dry-run.sh
  • bash tests/test-no-secrets.sh
  • bash scripts/ci-gitleaks.sh
  • Live grok mcp doctor shadcn healthy
  • CI test check on this PR

One enabled stdio server (shadcn@4.18.0) searches and installs from shadcn-compatible registries. Routing requires search-then-inspect, visual restraint, and a components.json gate. 21st.dev and extra UI MCPs stay out of policy.
Make the MCP config rewrite section-aware so startup_timeout_sec
is upserted once and stays idempotent across reinstalls.

Fail preflight and doctor unless Node is >=20.18.1 and npx exists,
matching shadcn 4.18.0 engines.

Treat a missing policy command as MCP_COMMAND_MISSING.

Require inspect of file targets and collisions before install,
and document that registry search may write components.json.
@kuker24
kuker24 merged commit 2990b0a into main Aug 16, 2026
1 check passed
@kuker24
kuker24 deleted the v1.2.0-ui-hub branch August 16, 2026 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant