The Neobrutalism MCP serverin Claude Code
One command wires Claude Code to the Neobrutalism MCP server. From the terminal you can search the live catalog, preview real source, and install every open-source component and Pro block — with your registry token already in the install URL. No local process. No JSON file to babysit.
neobrutalism · Claude Code
Add a hero to the homepage
Claude CodeviaMCP
Used Neobrutalism MCP to find a hero that fits the product.
Run your team
in one place
Plans, docs, and deadlines — shared with everyone who needs them.
Get StartedGet All Access
1 promptHero shipped
- MCP server
- Built for AI agents
- 12 tools
- 150+ Pro blocks
- 50+ components
- 3 backends
- Claude Code
- Cursor
- VS Code
- Any MCP client
- One URL, one token
- Prompt → shipped
Claude Code setup
FAQ
Connect Claude Code to Neobrutalism MCP — install command, registry token, Pro access, and what the agent can search and install.
Copy your registry token from Dashboard → Account, then run `claude mcp add --transport http neobrutalism "https://neobrutalism.com/api/mcp?token=YOUR_TOKEN"` (or the pre-filled command on your dashboard MCP tab). Start a new Claude Code session and run /mcp — `neobrutalism` should list 12 tools.
Per-user (the default) — the catalog is the same in every project, and your token stays out of the repo. Use `--scope project` only when you want a shared `.mcp.json` for a team; then pass the token via an environment variable instead of hardcoding it in git.
In a new session run /mcp and confirm `neobrutalism` is connected with 12 tools. Then ask: “search the neobrutalism registry for pricing blocks” — Claude should call search_items and return real slugs from the live catalog.
Rerun `claude mcp add` with the corrected URL (same server name neobrutalism) to overwrite the existing entry. To drop it, run `claude mcp remove neobrutalism` (or delete the entry from your user MCP config) and start a new session so Claude Code reloads the list.
401: the token in the URL is missing or wrong — re-copy it from Dashboard → Account and rerun `claude mcp add` (it overwrites the old entry). 403: the account isn’t Pro yet — upgrade, then retry with the same token; no new token is required after you go Pro.
Yes. The MCP server serves the paid block library, so access matches block downloads: no token → 401; valid token without Pro → 403 with an upgrade link. Free accounts still get a token; it unlocks the full tool surface once you’re Pro.
Dashboard → Account. It’s the same personal registry token used for Pro block installs via the shadcn CLI — one secret for both the CLI and Claude Code MCP.
The token is personal, revocable, and scoped to registry reads — it can’t change billing, account settings, or workspaces. Prefer the global (per-user) Claude Code MCP config so it never lands in a shared repo; rotate it from the dashboard if it leaks.
Team and Org seats include Pro. Each member has their own registry token, so every teammate runs `claude mcp add` with their own credentials instead of sharing one secret.
Search the full component and Pro block catalog, open real source (flattened to Base UI, Radix, or React Aria), open preview URLs, and get ready-to-run `shadcn add` commands with your token already in the URL — the same registry this site and the CLI use.
The free shadcn MCP runs locally and only resolves free public-registry components. Neobrutalism MCP is hosted (no local process), needs your Pro token, and adds Pro blocks with installable source, rich metadata, previews, stats, and token-embedded install commands.
Yes. Ask for a block (or let Claude pick one after a search); it calls get_install_command and returns a `shadcn add` line with your token baked in. Claude Code can run that in the project terminal (with your approval) so the block and its component deps land for your chosen backend.
Your choice per request. Default is Base UI; you can ask for Radix UI or React Aria. Block source is flattened to that backend before it returns, so it matches a normal shadcn install for that stack.
Anywhere Claude Code runs with your user MCP config — terminal CLI and editor integrations that share the same Claude Code MCP setup. Add the server once per-user and it applies to every project session.