Skip to directory

About Magic UI MCP

Magic UI's official MCP server searches and retrieves components from the live Magic UI registry, including installation instructions, source, related items, and examples.

What you can use it for

  • Find UI components by keyword or registry type
  • Inspect a component's source, examples, related items, and installation instructions
  • Add Magic UI components and patterns to a project
Connection and setup
Hosting
Local
Transport
Local stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
No authentication or account is required for the local registry MCP server.

Requirements

  • Node.js and npm (npx must be available).
  • An MCP client that supports local stdio servers.

Setup steps

  1. For clients with a publisher installer, run `npx @magicuidesign/cli@latest install <client>`. The publisher currently lists Cursor, Windsurf, Claude, Cline, and Roo Code.
  2. For manual setup, add an MCP server named `magicuidesign-mcp` with command `npx` and arguments `-y`, `@magicuidesign/mcp@latest`. This works for compatible stdio clients such as Codex CLI; no OAuth login or API key is required.
  3. The publisher's installer list describes its automated installer support, not the complete list of clients that can manually run this stdio server.
Tools 3

The official maintainer README documents exactly three MCP tools: listRegistryItems, searchRegistryItems, and getRegistryItem. Registry content is returned dynamically by these tools.

  • listRegistryItems
    01
  • searchRegistryItems
    02
  • getRegistryItem
    03
Limitations and notes
  • Some clients limit the number of tools they can call; server keeps a small generic tool set.
  • Concepts such as widgets, media, and devices are not modeled as first-class registry categories.
  • The retrieved registry item's framework/dependencies must be checked against the project before installation.
Original sources
  • official tool reference

    The current maintainer README documents exactly three generic registry tools; registry items are fetched dynamically rather than exposed as separate MCP tools.

  • official documentation

    The current maintainer README documents exactly three generic registry tools; registry items are fetched dynamically rather than exposed as separate MCP tools.

Documentation checked 2026-10-28T12:48:00.000Z. Connection has not been runtime tested.