zed -shadcn

This MCP server integrates with the Zed editor as a Shadcn UI extension. It exposes capabilities to browse and search shadcn/ui components from multiple registries and namespaces, and to install components using natural-language prompts within Zed's Agent Panel. You can query for components, filter by registry or namespace, and request installations like “show all shadcn buttons in the public registry” or “install the button, dialog, and card components.” The server supports multi-registry access and private registries, with authentication handled via environment variables. When installed, you’ll access these features through Zed’s MCP interface, allowing seamless discovery and installation of UI components directly in your project workflow.

• Prerequisites:

  • Node.js v18 or newer
  • npm or pnpm
  • Zed editor installed
  • A project using shadcn/ui components (components.json created via npx shadcn@latest init)

• From the Zed Extensions workflow:

  1. Open Zed
  2. Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
  3. Type "extensions" and select Extensions: Install Extensions
  4. Search for "shadcn/ui MCP" and Install

• For development / dev extension:

  1. Clone this repository
  2. Open Zed
  3. Press Cmd+Shift+P and select Extensions: Install Dev Extension
  4. Select the extension directory to load the dev extension

• Optional build (for WASI-based development environments):

  • Ensure Rust toolchain is installed
  • Build the extension for WASI: cargo build --release --target wasm32-wasip1
  • Load the built extension into Zed as a dev extension and verify logs via Zed’s log viewer

• Environment setup for private registries (if applicable):

  • Set environment variables to authorize access to private registries (see Additional Notes for details)

• Verification:

  • Open Zed and navigate to the MCP/Agent Panel to confirm the shadcn/ui MCP server is available
  • Try a sample prompt such as: “Show me all available components in the shadcn registry”

• Environment-based authentication: Private registry access may require environment variables or tokens. Configure these in your shell or run configuration before starting Zed.
• Multi-registry support: The MCP server can query public, private, and third-party registries. Ensure your registries are properly registered and accessible.
• Component installation: Use natural language prompts to install components. Ensure your project contains a valid shadcn setup (components.json) to integrate installed components correctly.
• Troubleshooting: If the MCP server does not appear in the Agent Panel, verify that the extension loads correctly (check Zed logs). For build issues in dev mode, ensure the WASM target and toolchain are correctly installed (Rust, wasm32-wasi).
• Compatibility: Confirm you are using a Shadcn-compatible registry and that your environment variables for authentication are present when connecting to private registries.