get-block-meta-content says it is for the create flow and not the inspire flow; get-inspiration-block-content says the reverse; get-component-meta-content and get-component-content say they are for refine only. That is a strong signal about how the server expects to be driven — read the instruction tool for the chosen workflow first, then stay inside the tools that workflow names, because the catalogue tools return different shapes for different purposes. Everything ends in a command rather than a file write: the collect tools accumulate a selection and the add-command tools emit what to run, which keeps the install step visible instead of implicit.
A Shadcn Studio block and component server with 15 tools organised around named workflows — create, inspire, refine and Figma-to-code — each with its own instruction tool, catalogue reads, a selection buffer and a command generator.
- An instruction tool per workflow: get-create-instructions for generating a new component from existing blocks, get-inspire-instructions for building one by taking inspiration from them, get-refine-instructions for refining a component already in the project, and get-ftc-instructions for the Figma-to-code flow, each tied to a slash command and each telling the agent to follow the steps in order.
- Catalogue reads scoped to a workflow: get-blocks-metadata returns block names, descriptions and categories for the create and inspire flows, get-block-meta-content fetches detail for a category in the create flow, get-inspiration-block-content fetches a block's code for inspiration and analysis only, and get-component-meta-content then get-component-content search and fetch a component for the refine flow.
- A selection buffer before the command: collect_selected_blocks and collect_selected_components accumulate what has been chosen, and get_add_command_for_items and get_add_command_for_components emit the shadcn CLI add command covering everything collected.
- The Figma bridge: parse-figma-blocks converts Figma component instance names into Shadcn Studio block references so they can be installed.
- Theming with the package manager detected: install-theme installs a public theme by name or a private theme in UUID form, detecting whether the project uses npm, pnpm, yarn or bun and generating the matching command.
A project the generated shadcn CLI commands will be run in — the tools return commands rather than writing files, and install-theme detects the project's package manager to build the right one. No credentials are configured on the server.
One command — npx -y shadcn-studio-mcp