Magic UI MCP Server: Registry Search for Agents

What is the Magic UI MCP server?

The repository calls it the official Model Context Protocol server for Magic UI. It runs locally over stdio and reads from the live Magic UI registry, so your AI coding agent sees the components that are published now rather than a stale copy in its memory.

It is deliberately small. The README says the server keeps a small generic tool surface, which matters because some clients cap how many tools they can call.

What changes in your agent's output

• The agent searches the registry for a match instead of writing an animation from scratch.
• Install instructions come from the registry item itself, so the add step is not guessed.
• Related items and examples can be returned with a single item lookup, when the agent asks for them.
• Prompts in plain language work. The README's own examples are a marquee of logos, a blur fade text animation and a grid background.

How the setup works

1. Run the Magic UI installer for your client, or paste the server entry into your MCP config by hand.
2. Restart the client so it starts the stdio server through npx.
3. Ask for a component by name or by effect and let the agent call the registry tools.

Who the Magic UI MCP server is for

Best for

• Front ends that want ready-made motion and background components rather than hand-rolled ones.
• Teams that already use a registry workflow and want the shadcn MCP server style discovery for one library.
• Anyone comparing component sources, next to Magic MCP or the animated set in UI Beats.

Not for

• Broad semantic browsing. The README says concepts such as widgets, media or devices are not modeled as first-class categories.
• Design-token work or Figma handoff. This server only reads a component registry.
• Pages where heavy motion hurts, since animation choices still need review, for example with the animation vocabulary skill.

Use it with UiChemy

Registry components are React code for a front end you host yourself. If the destination is a WordPress site, UiChemy builds there: AI to WordPress imports an existing AI build, and Composer edits it inside Elementor or Gutenberg. Click Get Started on uichemy.com.

Connect Magic UI MCP Server: Registry Search for Agents to your AI client

npx @magicuidesign/cli@latest install cursor

1. Use the installer

   Run npx @magicuidesign/cli@latest install <client>. The README lists cursor, windsurf, claude, cline and roo-cline as supported clients.

2. Or add the entry manually

   Paste the magicuidesign-mcp entry shown above into your client's MCP configuration file. It starts the server with npx -y @magicuidesign/mcp@latest.

3. Restart the client

   Reload your editor or agent so it launches the server, then check that the three registry tools appear.

4. Try a prompt

   Ask for a marquee of logos, a blur fade text animation or a grid background, as in the README examples.

Client configuration

{
  "mcpServers": {
    "magicuidesign-mcp": {
      "command": "npx",
      "args": ["-y", "@magicuidesign/mcp@latest"]
    }
  }
}

Endpoints and ports

What you can do with it

• Live registry readsThe server reads the current Magic UI registry directly, not a hardcoded list of categories.
• Three focused toolsList, search and get cover the whole loop, which keeps the tool count low for clients with limits.
• Install instructions includedEach item lookup returns how to add the component, so the agent does not invent the command.
• Pagination built inLimit and offset on list and search let an agent walk a long registry in small steps.
• Five clients supportedThe installer covers five named clients, so most editors and agents need no manual JSON editing.
• Open sourceThe repository is MIT licensed and credits its original author in the README.

Tools it exposes

Frequently asked questions