A
licenseNot graded
qualityD
maintenanceConnects AI models to MasterGo design tools, enabling retrieval of DSL data, component documentation, and metadata from MasterGo design files for structured component development workflows.
14,307 npm
ISC
MasterGo Magic MCP
by eDramas
Related Servers
Alternatives to MasterGo Magic MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA standalone Model Context Protocol service that connects MasterGo design tools with AI models, enabling AI models to directly retrieve DSL data from MasterGo design files.1214,307 npm287ISC
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to query, transform, and create design data in design files through a plugin connection, supporting design-to-design, code-to-design, and design-to-code workflows.5,390 npm1Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Figma designs using natural language commands, supporting file analysis, component extraction, asset export, comment management, and design system queries through the Figma API.1,217 npm1ISC
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to access Figma design data, including file, frame, and group metadata, so they can implement designs accurately in code. It simplifies and translates Figma API responses into relevant layout and styling information.159,735 npmMIT
- AlicenseAqualityBmaintenanceProvides AI coding agents with structured access to Lanhu design data, enabling direct inspection of artboards, extraction of pixel-perfect layer styles and CSS attributes, and downloading of design assets without vision token overhead.9MIT
TDQS
A3.9/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one retrieves the overall DSL data and code generation rules, the other retrieves component documentation from links found in the DSL. No overlap or ambiguity.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern with the 'mcp__' prefix (getDsl, getComponentLink), maintaining naming uniformity.
Tool Count2/5
With only 2 tools, the server feels undersized for a design-to-code workflow. Typically, a design tool MCP would require 3-15 tools to cover essential operations like listing files, managing components, or triggering generation.
Completeness3/5
The tools cover data retrieval (DSL and component documentation) but lack operations for actually generating code, managing files, or updating designs. Notable gaps exist for a complete code generation pipeline.
Maintenance
ActivityInactive
ResponsivenessNo issues