MCP server
by magicuidesign
Explore Magic UI, a React UI library offering structured component access, code suggestions, and installation guides for
Provides code implementation details and installation instructions for Magic UI's component library through an MCP server. Access dozens of pre-built React components including animations, buttons, backgrounds, and device mockups.
Magic UI is an official MCP server published by magicuidesign that provides AI assistants with tools and capabilities via the Model Context Protocol. Explore Magic UI, a React UI library offering structured component access, code suggestions, and installation guides for It is categorized under developer tools, design. This server exposes 8 tools that AI clients can invoke during conversations and coding sessions.
You can install Magic UI in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.
MIT
Magic UI is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Magic UI is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Magic UI is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Magic UI is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Magic UI against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Magic UI surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: Magic UI surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Magic UI for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Magic UI against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Magic UI into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Magic UI is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 49
Official ModelContextProtocol (MCP) server for Magic UI.
<div align="center"> <img src="https://github.com/magicuidesign/mcp/blob/main/public/mcp.png" alt="MCP" /> </div>npx @magicuidesign/cli@latest install <client>
Add to your IDE's MCP config:
{
"mcpServers": {
"magicuidesign-mcp": {
"command": "npx",
"args": ["-y", "@magicuidesign/mcp@latest"]
}
}
}
Once configured, you can questions like:
"Make a marquee of logos"
"Add a blur fade text animation"
"Add a grid background"
The server provides the following tools callable via MCP:
| Tool Name | Description |
|---|---|
getUIComponents | Provides a comprehensive list of all Magic UI components. |
listRegistryItems | Lists Magic UI registry items with optional filters like kind, query, and limit. |
searchRegistryItems | Searches Magic UI registry items by keyword or use case and returns ranked matches. |
getRegistryItem | Returns details for a single registry item, including install instructions and optional source, related items, and examples. |
getLayout | Provides implementation details for bento-grid, dock, file-tree, grid-pattern, interactive-grid-pattern, dot-pattern components. |
getMedia | Provides implementation details for hero-video-dialog, terminal, marquee, script-copy-btn, code-comparison components. |
getMotion | Provides implementation details for blur-fade, scroll-progress, scroll-based-velocity, orbiting-circles, animated-circular-progress-bar components. |
getTextReveal | Provides implementation details for text-animate, line-shadow-text, aurora-text, animated-shiny-text, animated-gradient-text, text-reveal, typing-animation, box-reveal, number-ticker components. |
getTextEffects | Provides implementation details for word-rotate, flip-text, hyper-text, morphing-text, spinning-text, sparkles-text components. |
getButtons | Provides implementation details for rainbow-button, shimmer-button, shiny-button, interactive-hover-button, animated-subscribe-button, pulsating-button, ripple-button components. |
getEffects | Provides implementation details for animated-beam, border-beam, shine-border, magic-card, meteors, neon-gradient-card, confetti, particles, cool-mode, scratch-to-reveal components. |
getWidgets | Provides implementation details for animated-list, tweet-card, client-tweet-card, lens, pointer, avatar-circles, icon-cloud, globe components. |
getBackgrounds | Provides implementation details for warp-background, flickering-grid, animated-grid-pattern, retro-grid, ripple components. |
getDevices | Provides implementation details for safari, iphone-15-pro, android components. |
Some clients have a limit on the number of tools they can call. This is why we opted to group the tools into categories. Note: For more specific context on each component, run the MCP locally and modify the logic that groups the components.
Big thanks to @beaubhp for creating the MCP server 🙏
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.