Docs

Open any component and press Copy prompt. You get one block of text containing the source, the demo, and the instructions needed to land both in your codebase.

There is no tool picker. The same prompt works in Claude Code, Cursor, Codex, Antigravity, Lovable, v0, Bolt and Windsurf — paste it and the tool writes the files, then adapts the colours and spacing to the theme you already have.

Every component is also served in registry-item.json format, so the shadcn CLI can install it directly:

npx shadcn@latest add "https://nuxus.dev/r/nova/shimmer-button?token=YOUR_TOKEN"

The registry returns source, so it is gated like everything else. Without a token it answers 401; with a token on the free plan, 402. Create one under Settings.

The MCP server lets an agent search Nuxus and install a component without you copying anything across. Point your client at https://nuxus.dev/api/mcp:

{
  "mcpServers": {
    "nuxus": {
      "type": "http",
      "url": "https://nuxus.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer nxs_YOUR_TOKEN"
      }
    }
  }
}

It exposes three tools:

• search_components — search all 178 components by keyword or category. Returns names and descriptions, never source.
• get_component — the full source, demo and install notes for one component. Requires a plan.
• list_categories — every category with a component count.
• check_component — send the current contents of a component file and find out whether it still matches the registry. Free.
• diff_component — the same comparison as a unified diff, ready to apply. Requires a plan.
• search_ecosystem — search every public shadcn registry, not just ours. Free, because none of it is ours to sell.

Searching works without a token, so an agent can explore the catalogue and tell you what it found before you pay for anything.

Staying current. Copy-paste normally means forking forever: when a component is fixed upstream, nothing tells you. Because your agent already has the file, it can send the contents to check_component and find out — no version history needed, so this works for anything you copied at any time. Your file is compared and discarded; we never store it.

A browser carries a session cookie; a terminal does not. Tokens are the machine equivalent, and they resolve to the same plan your account has — so a token cannot be used to get around the paywall, and a cancelled plan stops working immediately.

Create one under Settings. It is shown once, because we store a hash rather than the token itself. If you lose it, revoke it and make another. Treat it like a password: anyone holding it can install components as you.

Team plans are billed per seat. Invite the rest of your team from the team page — you get a link to send each person, and accepting it gives their account your plan.

Access is derived from the subscription, so removing a member, letting the plan lapse or cancelling it cuts off every seat at the same moment, in the browser and over the CLI and MCP alike. Invite links expire after 14 days and work once.

Publish your own components from the publish page. Paste the component and a demo that renders it, pick categories, and it appears on your profile at /@yourhandle and in the registry.

Published components are served through the same registry and MCP endpoints as everything else, so they install the same way.