Tool reference
Generated from the server itself, so what you read here is what your agent sees. Every tool is read-only; installing goes through the shadcn CLI on your machine. Call them by name in a prompt: “use shadcnpro to …”.
Find the right block: the catalog by category, a compact list, or a ranked search.
The block catalog by category: every category with its group (application, marketing), block count, free count and page URL. Start here when you do not know what exists.
None.
list_block_categories({})Returns: 27 categories grouped under Application and Marketing pages, each with its id, name, description, block count and URL.
A compact list of blocks (id, name, category, free) for one category or the whole registry. Use search_blocks when you know what the block should do.
categorystringfreeOnlybooleanlimitintegeroffsetintegerlist_blocks({
"category": "pricing"
})Returns: The pricing blocks with id, name, free flag and a one-line description each.
Ranked search over all blocks by what they do ("pricing with a monthly yearly toggle", "sidebar with team switcher", "login with Google"). Understands synonyms: modal finds dialogs, login finds sign-in, KPI finds stats.
querystringrequiredcategorystringlimitintegersearch_blocks({
"query": "pricing section with a monthly and yearly toggle"
})Returns: The closest blocks first, each with id, name, category, free flag, description and preview URL, plus the categories the query matched.
Read a block before installing it: install command, usage, files, source and previews.
One block and what you need of it in one call: install command, usage snippet, file list, source, preview and Figma links. Pick with `include` to keep replies small; source is capped per call.
Default include is ["install", "usage", "files"]. Ask for "source" only when you must edit the block by hand; the CLI installs it either way. Use `files` to fetch the source of specific files of a multi-file block.
idstringrequiredinclude("install" | "usage" | "files" | "source" | "preview" | "figma")[]filesstring[]packageManager"npm" | "pnpm" | "yarn" | "bun"get_block({
"id": "pricing-03",
"include": [
"install",
"usage"
],
"packageManager": "pnpm"
})Returns: The block metadata, the pnpm install command with its registry and npm dependencies, and an import/usage snippet.
Turn a one-line brief into an ordered stack of blocks and a page skeleton.
Turn a brief into an ordered stack of blocks for a whole page (landing, pricing, contact, blog, sign-in, dashboard, onboarding, 404 or a custom list of sections), with one install command for all of them and an app/page.tsx skeleton.
kind"landing" | "pricing" | "contact" | "blog" | "sign-in" | "sign-up" | "dashboard" | "onboarding" | "not-found" | "custom"requiredbriefstringsectionsstring[]excludestring[]packageManager"npm" | "pnpm" | "yarn" | "bun"plan_page({
"kind": "landing",
"brief": "SaaS analytics tool for small agencies, with pricing and FAQ"
})Returns: An ordered list of sections, the chosen block per section with two alternatives, one install command for the whole stack and an app/page.tsx that imports them in order.
Exact shadcn CLI commands and the registry setup for the project at hand.
The exact shadcn CLI command for one or more blocks, for npm, pnpm, yarn or bun, with the registry dependencies the CLI will add and a note on which blocks need the license key.
idsstring[]requiredpackageManager"npm" | "pnpm" | "yarn" | "bun"get_install_command({
"ids": [
"hero-04",
"pricing-03"
],
"packageManager": "pnpm"
})Returns: `pnpm dlx shadcn@latest add @shadcnpro/hero-04 @shadcnpro/pricing-03`, the shadcn/ui components it pulls in and whether a key is required.
Everything to set a project up for Pro blocks: shadcn init when needed, the .env.local line, the exact `registries` entry for components.json, and a command to verify the key works.
packageManager"npm" | "pnpm" | "yarn" | "bun"hasShadcnbooleanframework"next" | "vite" | "react-router" | "astro" | "other"get_project_setup({
"packageManager": "pnpm",
"hasShadcn": true
})Returns: Ordered steps: add SHADCNPRO_LICENSE_KEY to .env.local, merge the @shadcnpro registry into components.json, verify with a free block.
Doctor for Pro block installs: paste the project’s components.json (and, optionally, the CLI error) and get the exact problems and fixes: missing registry, wrong URL, missing key header, alias mismatches.
componentsJsonstringrequiredenvHasKeybooleancliErrorstringcheck_setup({
"componentsJson": "{ \"registries\": { \"@shadcnpro\": { \"url\": \"https://pro.shadcn.co/api/registry/{name}\" } } }",
"envHasKey": true
})Returns: One issue: the registry has no X-License-Key header, with the corrected registries object to merge.
Ready-made shadcn/ui themes as CSS variables and shadcn preset codes.
The ready-made shadcn/ui Pro themes: 7 neutral base colors (neutral, stone, zinc, mauve, olive, mist, taupe) and 17 accent themes (blue, violet, emerald, ...) with their primary color, so you can pick one by name or mood.
None.
list_themes({})Returns: 24 themes with name, title, kind (base or accent), light primary color and the theme builder URL.
One complete theme as CSS variables for :root and .dark (paste into globals.css) or as JSON, plus a shadcn preset code that applies it with `npx shadcn@latest init`. Accent themes are merged over a base color.
namestringrequiredbaseColor"neutral" | "stone" | "zinc" | "mauve" | "olive" | "mist" | "taupe"format"css" | "json"radius"default" | "none" | "small" | "medium" | "large"get_theme({
"name": "violet",
"baseColor": "zinc"
})Returns: A `:root { ... } .dark { ... }` block with every shadcn/ui variable set (zinc grays, violet accents), plus a preset code and the init command that uses it.
Jump from a component in code to the same component in the shadcn/ui Pro Figma kit.
The shadcn/ui Pro Figma kit location of a component (button, dialog, sidebar, ...) and its documentation page, for design handoff or for the Figma MCP.
componentstringrequiredget_figma_link({
"component": "dialog"
})Returns: The Figma file URL with the node of the Dialog component, the embed URL and the /figma-library/dialog page.
Search 200k+ icons across the libraries shadcn/ui projects use and get real imports.
Icon sets you can search: the ones shadcn/ui projects use (Lucide, Tabler, Phosphor, Remix, Hugeicons, Heroicons, Radix, ...) with their npm package and import style, plus the largest of the 240+ other Iconify sets.
querystringlist_icon_libraries({})Returns: Curated sets with icon counts, npm packages and notes, then the largest other sets, and the grand total of searchable icons.
Reaches api.iconify.design.
Find icons by name or meaning across 400k+ icons. Pass several queries at once ("home", "settings", "logout") and optionally the set the project already uses; Lucide results come first by default.
queriesstring[]requiredlibrarystringlimitintegersearch_icons({
"queries": [
"home",
"settings",
"logout"
],
"library": "lucide"
})Returns: For each query, matching icon ids such as lucide:house, lucide:settings and lucide:log-out.
Reaches api.iconify.design.
The real import and JSX for icons by id (library:name), following each package’s naming (lucide-react, @tabler/icons-react, @phosphor-icons/react, ...). Sets without a React package get @iconify/react or the inline SVG.
idsstring[]requiredincludeSvgbooleanget_icon({
"ids": [
"lucide:house",
"lucide:settings",
"lucide:log-out"
]
})Returns: import { HouseIcon } from 'lucide-react' and <HouseIcon className="size-4" />, for each icon.
Reaches api.iconify.design.
Short, current playbooks for setup, pages, theming and troubleshooting.
A short playbook as Markdown: setting a project up, adding a block, building a page from blocks, theming, Figma to code, and troubleshooting the registry or this server.
topic"setup" | "add-block" | "build-page" | "theming" | "figma-to-code" | "troubleshooting"requiredget_guide({
"topic": "build-page"
})Returns: The build-a-page playbook: plan with plan_page, install once, assemble, then verify.
Who is connected, which plan, and how many requests are left this minute.
Who is connected: account email, plan, workspace, the name of the license key in use and how many requests it has left this minute. Call it to check a new setup.
None.
whoami({})Returns: email, plan, workspace, key name, requests remaining this minute and the server version.
Playbooks the server hands to the agent as ready-made messages. Clients expose them as slash commands or in a prompt picker; each pairs a task with the matching guide from get_guide.
Prepare the current project for shadcn/ui Pro blocks: shadcn init if needed, license key in .env.local, the @shadcnpro registry in components.json, then verify.
Find the best block for a described section, install it with the CLI and wire it into the page.
Plan a whole page as a stack of blocks, install them in one command and assemble the page file.
Apply one of the shadcn/ui Pro themes to the project by updating the CSS variables in the global stylesheet.
Setup for your client: all clients. Errors and fixes: troubleshooting.
16 tools, every Pro block, 24 themes and the Figma kit, in 20 AI clients. Included in every Pro plan, monthly or yearly.
Secure payment. 7-day free trial. Cancel anytime.