MCP Magic UI

Name: MCP Magic UI
Author: idcdev

@idcdev

代码仓库

关于 MCP Magic UI

An MCP (Model Context Protocol) server for accessing and searching Magic UI components

基本信息

分类

其他

运行时

node

传输方式

stdio

发布者

idcdev

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-magic-ui": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector",
        "mcp-magic-ui"
      ]
    }
  }
}

工具

Get a list of all available Magic UI components with their metadata

Get the source code of a specific component by its file path

概览

What is MCP Magic UI?

MCP Magic UI is a Model Context Protocol server that provides access to Magic UI components from the magicuidesign/magicui GitHub repository. It categorizes components and makes them discoverable through MCP tools for AI assistants and other MCP clients.

How to use MCP Magic UI?

Clone the repository, install dependencies with npm install, build with npm build, then start the server using npm start for stdio transport or TRANSPORT_TYPE=http npm start for HTTP transport. Optionally configure a GitHub personal access token in a .env file to avoid API rate limits. Connect using any MCP client, such as the MCP Inspector.

Key features of MCP Magic UI

Fetches and categorizes all Magic UI components
Local caching reduces GitHub API calls and allows offline use
Supports both stdio and HTTP transport methods
Includes fallback mock data when GitHub API is unavailable
Exposes tools to list components and retrieve source code

Use cases of MCP Magic UI

AI assistants discover and use Magic UI components on demand
Developers programmatically fetch component metadata or source code
Teams cache component data for offline reference or faster access
Integration with MCP-compatible editors or developer workflows

FAQ from MCP Magic UI

What is the purpose of MCP Magic UI?

It allows AI assistants and other MCP clients to easily discover and use Magic UI components by exposing them through MCP tools.

What runtime dependencies are required?

It requires Node.js and npm, as installation uses npm commands. No other runtime dependencies are mentioned.

How does the server handle GitHub API rate limits?

The server caches component data locally and allows an optional GitHub personal access token via a .env file to increase rate limits. Mock data is provided as a fallback when the API is unavailable.