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.
1,928 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.121,928 npm285ISC
- 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,772 npm1ISC
- AlicenseAqualityCmaintenanceProvides 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
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with access to Figma design data through the Figma API. Enables accurate one-shot implementation of designs in any framework by translating Figma files into simplified layout and styling information.4 npm1MIT
Figma MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceProvides Figma design context to AI agents, enabling code generation, design system integration, and canvas manipulation through MCP.2,002-
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