Zed calls them context_servers — add cleenui to ~/.config/zed/settings.json under that key.
Zed supports MCP-style servers but uses its own naming: the top-level key is context_servers (not mcpServers). The Agent Panel in Zed surfaces tools from registered context_servers in every Assistant conversation. The shape of each entry is otherwise the standard MCP command/args/env.
Hit ⌘+, (Cmd+comma) to open settings.json. The file lives at ~/.config/zed/settings.json on macOS/Linux.
Note the key name — it's context_servers, not mcpServers. Zed uses its own naming convention but the entry shape is otherwise the standard MCP command/args/env.
Prefer a UI? Open the Agent Panel → Settings → 'Add Custom Server'. Zed walks you through the same fields and writes settings.json for you.
Open the Agent Panel — Zed shows a status dot next to each registered server. Green means connected. Hover for the list of available tools.
⌘+? opens the Assistant panel. Tools from registered context_servers are part of the model's available actions — just ask.
A green status dot next to cleenui in the Agent Panel means it's connected. Other colors indicate configuration issues — click for the error message.
Zed validates JSON live — look for the red squiggle indicator and fix the offending block.
Click the failed entry in the Agent Panel — Zed surfaces the underlying error. Most often a Node version mismatch with what npx expects.
Two paths to your first component. Pick the one that fits how your team builds.
One prompt to your AI tool. The Setup skill handles dependencies, design tokens, build config, and component registration — all without leaving your editor.
The classic flow. Install the package, import the styles, drop in your first component. No agents required — same end result.