Groups
The full reference with parameters and sample calls is generated from the server itself at /mcp/tools. This page explains how the groups fit together.
Discover: list_block_categories is the catalog by category with block counts. list_blocks is a compact list for one category. search_blocks ranks every block by what it does and understands synonyms (a modal finds dialogs, a login finds sign-in, a KPI finds stats).
Inspect: get_block returns one block and only the parts you ask for with include: install (command, dependencies), usage (import and JSX), files, source (capped per call; request specific files of a multi-file block), preview and figma.
Plan: plan_page turns a brief into an ordered stack of blocks for a landing, pricing, contact, blog, sign-in, sign-up, dashboard, onboarding or 404 page, or for a custom list of sections. It returns a pick and alternatives per section, one install command and an app/page.tsx skeleton.
Install: get_install_command builds the CLI command for npm, pnpm, yarn or bun. get_project_setup returns the .env.local line, the components.json registry entry and verification commands. check_setup reads a pasted components.json and tells you what to fix.
Themes: list_themes and get_theme return the 24 Pro themes as CSS variables for :root and .dark, or as a shadcn preset code.
Figma: get_figma_link resolves a component name to its node in the Pro Figma kit and its documentation page.
Icons: list_icon_libraries, search_icons and get_icon search 200k+ icons across the sets shadcn/ui projects use (Lucide, Tabler, Phosphor, Remix, Hugeicons, Heroicons, Radix and more) and return the real import for the set your project already has.
Guides: get_guide returns a short playbook (setup, add a block, build a page, theming, Figma to code, troubleshooting). The same playbooks are exposed as prompts: setup-project, add-block, build-page, apply-theme.
Account: whoami reports who is connected, the plan, the key in use and the requests left this minute.
A typical flow
You: Add a pricing section with a monthly/yearly toggle under the hero.
Agent: search_blocks({ query: "pricing monthly yearly toggle" })
get_block({ id: "pricing-01", include: ["install", "usage"], packageManager: "pnpm" })
→ runs: pnpm dlx shadcn@latest add @shadcnpro/pricing-01
→ edits app/page.tsx: import { Pricing01 } from '@/components/blocks/pricing-01'
Two calls, a few hundred tokens each, and the block that arrives is the one on the site.
Tool replies
Data tools answer with compact JSON; guides answer with Markdown. Every reply that could lead somewhere ends with a next hint for the agent. Errors are JSON with an error and a hint ("Did you mean pricing-01, pricing-02?"), so the agent can recover without asking you.
All tools are read-only: the server never writes to your project. Installing happens through the shadcn CLI on your machine, after the agent asks you.