01orbital in your AI editor

1. Add the registry

Start with a project that has shadcn initialized. Add this registry entry to your existing components.json:

{
  "registries": {
    "@01orbital": "https://01orbital.dev/r/{name}.json"
  }
}

You can search the catalog and read free components without a token. If you need the initial project setup, see the install guide.

2. Connect your editor

Run the command for your editor from the project folder containing components.json:

• Claude Code: npx shadcn@latest mcp init --client claude
• Cursor: npx shadcn@latest mcp init --client cursor
• VS Code: npx shadcn@latest mcp init --client vscode

Enable or reconnect the shadcn MCP server in your editor. Claude Code may need a restart; its /mcp command shows the connection status. Other clients are covered in the shadcn MCP setup guide.

3. Ask for what you need

• Find pricing blocks in the 01orbital registry.
• Show the details for @01orbital/corner-bloom.
• Show a source example for @01orbital/corner-bloom.
• Get the install command for @01orbital/corner-bloom.

Once you choose an item, ask your assistant to install it using the generated shadcn command. The CLI copies the component into your project, where you can edit the source.

Paid components

Use the same ORBITAL_TOKEN and Authorization header as the Pro install setup. Put .env.local beside the project’s components.json, then reconnect the MCP server so it loads the token. No separate MCP credential is needed.

Paid items appear in search without a token. Their details, source and installation require a valid license.

Troubleshooting

01orbital is missing

Check that the MCP server starts in the folder containing your components.json. In a monorepo, this is usually the app workspace. For a pnpm workspace with shadcn installed, the launch command can be:

pnpm --dir apps/web exec shadcn mcp

Replace apps/web with your app’s path.

A paid item returns Unauthorized

Check the registry’s Authorization header and that ORBITAL_TOKEN is available to the MCP process. A token exported in your shell takes precedence over .env.local, so update or unset it there. Reconnect after changing either. You can request another copy of your token by email at /account.