@magicuidesign/mcp

Created By
beaubhpa year ago
Official MCP server for Magic UI.
Overview

What is MagicUI MCP?

MagicUI MCP is the official ModelContextProtocol server for Magic UI, enabling AI assistants to access information about Magic UI components, including their implementation details and available features.

How to use MagicUI MCP?

To use MagicUI MCP, install the Cursor IDE, configure the MCP server in the Cursor settings, and restart Cursor to access Magic UI tools.

Key features of MagicUI MCP?

  • Provides a comprehensive list of all available Magic UI components.
  • Retrieves implementation details and code examples for specific components across various categories such as Core, Special Effects, and Animations.

Use cases of MagicUI MCP?

  1. Accessing a list of Magic UI components for development.
  2. Retrieving code examples for specific UI components.
  3. Integrating Magic UI features into applications using AI assistants.

FAQ from MagicUI MCP?

  • How do I install MagicUI MCP?

You can install it via npm using the command npm install @magicuidesign/mcp.

  • What is the purpose of the MCP server?

The MCP server allows AI tools to interact with and retrieve information about Magic UI components.

  • Can I run MagicUI MCP locally?

Yes, you can run it locally by following the setup instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
beaubhp
Star
1
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago