mastergo-design/mastergo-magic-mcp
If you are the rightful owner of mastergo-magic-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
MasterGo Magic MCP is a standalone service that connects MasterGo design tools with AI models, allowing for direct retrieval of DSL data from design files.
Tools
Functions exposed to the LLM to take actions
version_0.0.4-beta.11
the current version is 0.0.4-beta.11
mcp__getDsl
"Use this tool to retrieve the DSL (Domain Specific Language) data from MasterGo design files and the rules you must follow when generating code. This tool is useful when you need to analyze the structure of a design, understand component hierarchy, or extract design properties. You must provide a fileId and layerId to identify the specific design element. This tool returns the raw DSL data in JSON format that you can then parse and analyze. This tool also returns the rules you must follow when generating code. The DSL data can also be used to transform and generate code for different frameworks."
mcp__getComponentLink
When the data returned by mcp__getDsl contains a non-empty componentDocumentLinks array, this tool is used to sequentially retrieve URLs from the componentDocumentLinks array and then obtain component documentation data. The returned document data is used for you to generate frontend code based on components.
mcp__getMeta
Use this tool when the user intends to build a complete website or needs to obtain high-level site configuration information. You must provide a fileld and layerld to identify the specific design element. This tool returns the rules and results of the site and page. The rules is a markdown file, you must follow the rules and use the results to analyze the site and page.
mcp__getComponentGenerator
Users need to actively call this tool to get the component development workflow. When Generator is mentioned, please actively call this tool. This tool provides a structured workflow for component development following best practices. You must provide an absolute rootPath of workspace to save workflow files.
Prompts
Interactive templates invoked by user choice
No prompts
Resources
Contextual data attached and managed by the client