The Neobrutalism MCP serverin Zed
Zed’s context_servers expect a local command — `mcp-remote` bridges that to our hosted URL. One settings.json entry and the Agent Panel can search the full Neobrutalism catalog, read Pro block source for your backend, and copy token-ready install commands without leaving the editor. Node 18+ is enough; npx pulls the bridge on first run.
neobrutalism · Zed
Add a hero to the homepage
ZedviaMCP
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
Zed setup
FAQ
Connect Zed agent to Neobrutalism MCP — context_servers, mcp-remote or remote URL, token, and Pro access.
Open Settings → AI → MCP Servers (or run `zed: open settings file`) and add a context server named `neobrutalism`. Use the snippet on this page: `npx -y mcp-remote` with your full registry URL (token in the query string) — that bridges Zed’s stdio context servers to our streamable-HTTP endpoint. Node 18+ required. Save, then confirm a green “Server is active” indicator.
Zed’s agent launches context servers as local stdio processes by default. mcp-remote is the standard shim that forwards stdio to a streamable-HTTP server — your token still travels in the URL. Newer Zed builds also accept a native remote server with only a url field; either form hits the same Neobrutalism endpoint. This page documents mcp-remote because it matches the snippet above.
Open Agent Panel settings and confirm `neobrutalism` is connected. Then ask: “search neobrutalism for hero blocks” — the agent should call search_items through the bridge and return real slugs. Mentioning the server by name helps the model pick its tools.
Run npx -y mcp-remote with your full registry URL in a terminal to see the real error: 401 bad token, 403 no Pro. Confirm Node 18+ and that npx is on the PATH Zed inherits (launch Zed from a terminal if needed). Check the MCP Servers indicator tooltip for status text.
Usually not for config reloads, but if tools don’t appear, restart the server from Settings → AI → MCP Servers or relaunch Zed. Zed also reloads tool lists when the server sends tools/list_changed notifications.
Yes — the Zed agent needs a Pro Neobrutalism account for Pro block tools. No token → 401; token without Pro → 403. Upgrade, keep the same URL in context_servers, and reconnect the server.
In the URL query string (Dashboard → Account for the token value), whether you use mcp-remote args or a native remote `url`. It’s the same token as Pro CLI installs.
The token is read-only for the registry and revocable. Prefer user settings over a project file checked into git; rotate from the dashboard if it leaks.
Yes with Team/Org Pro. Each person uses their own registry token in their own Zed settings — don’t share one URL in a repo.
Search the catalog, read Pro block and component source (Base UI / Radix / React Aria), open previews, and copy token-ready install commands — without leaving the Agent Panel.
Mention “neobrutalism” or the tool name in the prompt, or create a custom agent profile that enables only the MCP tools you want. Zed’s tool permissions may still ask for approval depending on your settings.
It can fetch install commands via get_install_command. Run the returned `shadcn add` line in the project (Agent terminal or your shell) to land the block and deps for your backend.
Zed-configured MCP servers are used by the native Agent and can be forwarded to external agents over ACP. Terminal threads using other CLIs need their own MCP config (e.g. Claude Code / Codex) separately.
Ask for Base UI (default), Radix UI, or React Aria. Source is flattened to that backend before return.