Skip to main content
Book a demo

shadcn/ui

Search shadcn/ui registries for components and get the command to add them.

Book a demo View documentation

Tools

7 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

7 tools found.

  • Get project registries

    Tool name: get_project_registries

    Get configured registry names from components.json - Returns error if no components.json exists (use init_project to create one)

  • List items in registries

    Tool name: list_items_in_registries

    List items from registries (requires components.json - use init_project if missing)

  • Search items in registries

    Tool name: search_items_in_registries

    Search for components in registries using fuzzy matching (requires components.json).

  • View items in registries

    Tool name: view_items_in_registries

    View detailed information about specific registry items including the name, description, type and files content.

  • Get item examples from registries

    Tool name: get_item_examples_from_registries

    Find usage examples and demos with their complete code.

  • Get add command for items

    Tool name: get_add_command_for_items

    Get the shadcn CLI add command for specific items in a registry.

  • Get audit checklist

    Tool name: get_audit_checklist

    Make sure to run the tool after all required steps have been completed.

Compatibility

Connect shadcn/ui to the clients your teams already use

19 AI clients can connect to shadcn/ui through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaude CodeWindsurfGooseCodexHermesRaycastWarpGitHub CopilotGitHub Copilot CLIGemini CLIZedCline CLIAntigravityOpenCodeCrushECAOh My Pi

Why Runlayer

Why connect shadcn/ui through Runlayer?

One approved path

Approve shadcn/ui once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions