Shadcn MCP for Rovo Dev CLI
Connect Atlassian Rovo Dev CLI into the shadcn.io registry with one MCP URL — access every block, icon, and example in the catalog.
One MCP URL gives Atlassian's Rovo Dev CLI live tools to search, preview, and install every block, component, and icon on shadcn.io — no hallucinated props, no broken installs.
Install
Open Rovo Dev's MCP config with the CLI:
acli rovodev mcpThis opens your editor on the Rovo Dev MCP config file. Add the shadcnio server:
Save the file once signed in with an active shadcn.io Pro subscription — the config carries your personal token, so treat the full URL like an API key. Pro starts at $19/mo and includes MCP access across every editor plus 6,000+ production-ready blocks. Not Pro yet? See what you unlock →
Rovo Dev's schema is Cursor-compatible — mcpServers + url + optional headers. The CLI reloads config on save, so new servers are available to the agent on the next prompt.
Using a header instead
If you'd rather keep the token out of the URL:
{
"mcpServers": {
"shadcnio": {
"url": "https://www.shadcn.io/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}A Team or Organization plan gives every workspace member their own Pro entitlement.
Install your first block
use shadcnio to install hero-announcement into my projectWhat Rovo Dev actually does, in order:
search_items({ query: "hero-announcement" })to confirm the slug resolves.get_item({ name: "hero-announcement" })for a cheap metadata peek.get_install_command({ name: "hero-announcement" })— returns ashadcn add https://www.shadcn.io/r/hero-announcement.json?token=…URL with your token already in the query string.- Runs it through the CLI's shell tool. Files land under
components/ui/.
Name the server explicitly ("use shadcnio…") when multiple MCPs are configured.
The example above uses hero-announcement, a Pro block — the install runs once you're signed in with an active subscription.
Manage the connection
Re-run acli rovodev mcp any time to edit or remove servers. The CLI also exposes acli rovodev mcp list (or similar) for quick status checks depending on your Rovo Dev version — consult acli rovodev --help for the exact subcommands.
If your Pro subscription lapses, the next tool call returns 403. Resubscribing restores access immediately — the token stays valid across subscription gaps.
FAQ
Was this page helpful?
Sign in to leave feedback.