Muiscan MCP Server
Converts Figma designs into production-ready MUI Design System web components by exporting layouts via the Muiscan Figma Plugin and transforming them into code
Translates design layouts into MUI (Michael UI) Design System web components, supporting comprehensive component sets including inputs, content, layout, feedback, actions, and navigation components
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Muiscan MCP Server convert this Figma button design to an MUI web component"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Muiscan MCP Server
Translate Figma files to MUI Design System components via the Model Context Protocol (MCP).
What is Muiscan?
Muiscan converts Figma designs into production-ready MUI (Michael UI) web components via the Model Context Protocol.
Related MCP server: MCP Figma to Code
Getting Started with MUI Design System
Before using Muiscan, set up your MUI project:
Create Mui App
Get started quickly with the official MUI starter template:
A lightweight starter template for building accessible, fast-loading interfaces using Mui Web Components.
# Clone the starter template
git clone https://github.com/michaeltrilford/create-mui-app.git
cd create-mui-app
npm install
npm startOnce you have your MUI project set up, you can use Muiscan to convert Figma designs directly into MUI components.
Installation
Clone or download this repository
git clone https://github.com/yourusername/muiscan-mcp.git cd muiscan-mcpInstall dependencies
npm installConfigure Claude Desktop Add the Muiscan server to your Claude Desktop configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Windows:%APPDATA%\Claude\claude_desktop_config.jsonAdd this configuration (update the path to match your installation):
{ "mcpServers": { "muiscan": { "command": "node", "args": ["/Users/AddYourPath/muiscan-mcp/server.js"] } } }Restart Claude Desktop After saving the configuration, restart Claude Desktop for the changes to take effect.
Usage
Once installed, Muiscan provides:
Tools
translate_muiscan: Transform muiscan JSON to web components
Prompts
mui-component-guide: Guide for converting UI to MUI web components
In Claude Desktop
Open Claude Desktop
Go to Settings → Tools and MCP
Verify that "Muiscan" appears in your MCP servers list
Export from Figma:
Open your design in Figma
Select the frame/component you want to convert
Run the Muiscan Figma Plugin to copy the layout
Convert in Cursor or play.muibook.com:
Paste the scanned layout into your prompt
Ask the model/prompt to convert it to MUI web components
The MCP will use the component guide to generate the code
Complete Workflow
Figma Design
↓
Muiscan Figma Plugin (Export)
↓
MUISON JSON (Copy to clipboard)
↓
Paste into Cursor or play.muibook.com
↓
Muiscan MCP (Transform)
↓
MUI Web ComponentsSupported Components
Muiscan supports a comprehensive set of MUI components including:
Inputs: field, checkbox, input, select, switch, file-upload, progress
Content: accordion, heading, body, code, dialog, drawer, quote, slat, smart-card, table, image, list
Layout: card, container, responsive, rule, v-stack, h-stack, grid
Feedback: alert, badge, message, loader
Actions: button, button-group, chip, dropdown, link
Navigation: carousel-controller, stepper, tab-controller, tab-bar
Project Structure
muiscan-mcp/
├── server.js # Main MCP server
├── mui-prompts.js # Component guide and examples
├── transform.js # JSON transformation logic
├── mcp.json # Server configuration
├── package.json # Node.js dependencies
└── README.md # This fileDevelopment
To test the server locally:
npm startTroubleshooting
Server not appearing in Claude Desktop
Check that the path in
claude_desktop_config.jsonis correctVerify Node.js is installed:
node --versionRestart Claude Desktop completely
Check Claude Desktop logs for errors
Changes not taking effect
Save all configuration files
Fully quit and restart Claude Desktop (not just close the window)
Clear any cached MCP connections
License
MIT
Contributing
Contributions welcome! Please open an issue or submit a pull request.
Available Tools
1 tooltranslate_muiscanC
Transform muiscan JSON to web components
Inputs: json (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a distinct and clear purpose, making it impossible for an agent to misselect between multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'translate_muiscan' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency or deviation.
A single tool is too few for most server purposes, as it severely limits functionality and scope. While it might be appropriate for a highly specialized task, it feels thin and incomplete for general use, indicating a potential mismatch with typical MCP server expectations.
The tool surface is severely incomplete, as it only offers one transformation function without any related operations. There are obvious gaps, such as no ability to create, update, delete, or retrieve muiscan data, making it impossible for agents to perform a full workflow or lifecycle in this domain.
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
Deterministic Figma to Elementor, Gutenberg, Oxygen, Etch and HTML layouts for AI assistants.
Edit and publish your FramerToNextJS sites (converted Framer or AI-built) from Claude, Cursor or Codex. 19 tools: read pages, rewrite copy, restyle elements, add sections and pages, design Studio sites, manage CMS collections and items, then publish to your own host. OAuth with a read-only option, and MCP runs no model on FNJ's side. Requires an FNJ plan (Lifetime or any AI builder plan).
Design canvas for agents: create, edit, render and export Figma-shaped designs over MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceConverts Figma designs into production-ready React components with design token extraction, widget registry integration, and micro-frontend module generation.351 npm1MIT
- AlicenseNot gradedqualityDmaintenanceTransform Figma designs into pixel-perfect React + Tailwind components using the Model Context Protocol.5MIT
- AlicenseAqualityDmaintenanceConverts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.111 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read and write Figma designs through a local WebSocket relay, turning Figma selections into framework-aware code and building/editing designs directly on the canvas. Provides 112 MCP tools for bidirectional design-code workflows with support for any MCP client.MIT