Avara UI
Avara UI

MCP Server

Connect your AI assistant to the Avara UI registry. With the shadcn MCP server it can browse, search and install components from plain-language prompts — no copy-pasting commands.
The server is part of the shadcn CLI. It is free, needs no API key, and works with Avara UI because our components are published as a standard shadcn registry.

Quick start

Step 1: Register Avara UI

Run once per project, so the server knows where to find our components:
npx shadcn@latest registry add @avara-ui=https://avaraui.com/r/{name}.json
This adds the registry to components.json, which you can also write by hand:

Step 2: Add the MCP server

Pick your client and run the command in your project. Prefer to do it by hand? See Configuration.
Run the following command in your project:
npx shadcn@latest mcp init --client claude
Restart Claude Code and run /mcp to check the connection.

Step 3: Try it

Ask your assistant:
  • "Show me all components in the @avara-ui registry"
  • "Add the hero and navbar from @avara-ui to my project"
  • "Build a pricing page using components from @avara-ui"

Name the registry. Include @avara-ui in your prompt. Without it the assistant may search only the default shadcn/ui registry.

Configuration

Add the server to your client's MCP config. The command is the same everywhere — only the file differs.
Add to .mcp.json, then run /mcp to check the connection:

Example prompts

Browse and search
  • "List the components in @avara-ui"
  • "Find a pricing section in @avara-ui"
Install
  • "Add @avara-ui/hero to my project"
  • "Install the navbar and footer from @avara-ui"
Build
  • "Create a landing page with a hero, features and FAQ from @avara-ui"

Troubleshooting

The assistant can't find Avara UI components

Check that components.json has the @avara-ui entry from Step 1, and mention @avara-ui in your prompt.

The server doesn't respond

Check the config file for typos, restart your client, and make sure you can reach https://avaraui.com.

"No tools" message

Clear the npx cache with npx clear-npx-cache, re-enable the server, and read your client's MCP output log.

Installs fail

Make sure components.json exists (run init) and you have write access to the project folders.

Next steps

For the full server reference, see the shadcn MCP docs.