The block half of the catalogue browses, searches and installs with nothing extra. The page half carries the same note on getPageInstall and on listInstalledPages — all pages are PRO, check components.json for a valid license key first — so a page workflow can stall at the last step for a reason no earlier call reveals. The other thing worth knowing is that this server never writes to the project: the install tools return the official command and something else runs it, which is why get_audit_checklist insists on going first, since it is what settles the package manager that command should use.
A catalogue server for Shadcn Space blocks and pages, with 10 tools covering listing, keyword search, install commands and what is already installed in the project.
- A workflow contract the agent is told to read before anything else: get_audit_checklist returns the rules for handling free versus PRO components, package managers and installation flows, and its description marks it as required before any other tool in this server.
- Block discovery in browse and search form: listBlocks returns the complete set of blocks available to a project, searchBlocks matches keywords or tags when the requirement is already known.
- Page discovery in the same shape: listPages returns every page type, searchPages matches keywords or tags against them.
- Install commands rather than file writes: getBlockInstall returns the official installation command for a named block, getPageInstall returns it for a named page.
- Project state before customisation: listInstalledBlocks and listInstalledPages report what is already in the project and take a names filter to narrow the answer.
No credentials for the block tools. Pages are PRO components, so a valid license key has to be recorded in the project's components.json before one can be installed.
One command — npx -y shadcnspace-mcp@latest