uminix

MCP

Let Claude, Cursor, Codex or Copilot search, read and install Luminix blocks through the shadcn MCP server.

Luminix is a shadcn registry. The shadcn CLI ships an MCP server that reads every registry listed in your components.json, so your agent can find a block, read its files and install it without leaving the chat. There is nothing extra to host or sign up for.

How it fits together

LayerWhat it isWhere it lives
AgentClaude Code, Cursor, Codex, VS Code Copilot, OpenCodeYour editor or terminal
MCP servershadcn mcp, started by the agent over stdioYour machine
Registryregistry.json index plus one {name}.json per blockhttps://ui.luminixstudio.com/r/

The agent calls MCP tools. The server turns them into plain HTTP requests against the registry and returns the JSON. Installing runs the same shadcn add you would type yourself.

1. Add the registry

Add the @luminix namespace to components.json at the root of your project. Run npx shadcn@latest init first if the file does not exist yet.

components.json
{
  "registries": {
    "@luminix": "https://ui.luminixstudio.com/r/{name}.json"
  }
}

2. Connect your agent

mcp init writes the server entry for your client. Restart the client after it runs.

npx shadcn@latest mcp init --client claude

This writes .mcp.json:

.mcp.json
{
  "mcpServers": {
    "shadcn": {
      "command": "npx",
      "args": ["shadcn@latest", "mcp"]
    }
  }
}

Run /mcp in Claude Code to confirm the server is connected.

Any other MCP client works with the same entry: command npx, arguments shadcn@latest mcp, run from your project root.

3. Ask for blocks

Name the registry in your prompt so the agent searches it:

  • “Show me the hero blocks in @luminix.”
  • “Find a login page with social sign in from @luminix.”
  • “Add hero-1 from @luminix and keep our nav.”
  • “Install dashboard-2 and footer-3 from @luminix.”

What the agent can do

ToolUse
get_project_registriesReads the registries in components.json
list_items_in_registriesLists every block, component and theme in @luminix
search_items_in_registriesFuzzy search by name or description
view_items_in_registriesReturns an item's files, dependencies and tokens
get_item_examples_from_registriesFinds demo usage for an item
get_add_command_for_itemsReturns the shadcn add @luminix/{name} command
get_audit_checklistA checklist to verify the install afterwards

Without MCP

The same registry works from the CLI:

npx shadcn@latest search @luminix -q hero
npx shadcn@latest view @luminix/hero-1
npx shadcn@latest add @luminix/hero-1

Troubleshooting

  • The agent does not see @luminix. Make sure components.json is in the folder the client starts the server from, then restart the client.
  • Search finds nothing. Check that /r/registry.json loads in your browser.
  • npx cannot be found. GUI clients sometimes start without your shell PATH. Use the absolute path from which npx as the command.

On this page