Connect MasterGo Designs to AI Models
An MCP server connecting MasterGo design files to AI models - retrieves DSL data to restore designs into working HTML or component code.
Maintainer of this project? Claim this page to edit the listing.
0.2.1Add to Favorites
Why it matters
Integrate your MasterGo design files with AI models to directly retrieve and process design data. This connector enables seamless data extraction for further analysis or AI-driven design processes.
Outcomes
What it gets done
Retrieve DSL data from MasterGo design files.
Access component documentation and metadata.
Facilitate structured component development workflows.
Configure and run the connector via command line or environment variables.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-mastergo | bash Capabilities
Tools your agent gets
Retrieves DSL (Domain Specific Language) data from MasterGo design files
Retrieves component documentation via links
Retrieves metadata
Provides structured component development workflow for Vue and React
Overview
MasterGo MCP Server
An MCP server retrieving DSL data from MasterGo design files so an AI can restore a design into working HTML or a structured Vue/React component. Use when a MasterGo design (in a Team Project, on a Team Edition account) needs converting into real code instead of being manually rebuilt.
What it does
Connects MasterGo design tools with AI models by retrieving DSL (Domain Specific Language) data directly from MasterGo design files, letting an AI turn a design link into real code rather than a static image. Runs via npx with no external dependencies beyond Node.js. Named tools cover retrieving DSL data from a design, pulling component documentation from a link, fetching file metadata, and a structured component-development workflow generator for Vue and React that produces workflow files and component specifications. Example prompts drive it directly by pasting a MasterGo file URL: extract an SVG and preview it in HTML, restore a design straight into code, or restore a design and save it as an HTML file - all working equally with a file's full URL or a MasterGo short link.
When to use - and when NOT to
Use it when a MasterGo design needs converting into real code - HTML, or a structured Vue/React component - rather than manually rebuilding it from a screenshot. Access requires a personal access token generated from MasterGo's own Security Settings, and two permission requirements often trip people up: the account must be Team Edition or higher, since the personal free edition does not support MCP access at all, and the design file itself must live inside a Team Project rather than a personal draft, since draft-box files are not reachable through MCP tools. Configuration works via command-line flags (--token, --url, --rule for design rules, --proxy, --debug, --no-rule) or the equivalent environment variables (MG_MCP_TOKEN/MASTERGO_API_TOKEN, API_BASE_URL, RULES, HTTPS_PROXY), and can also run entirely server-side over SSE with no local install at all, authenticated via an x-mg-useraccesstoken header.
Capabilities
DSL extraction from MasterGo design files, component documentation lookup, file metadata retrieval, and a structured Vue/React component-development workflow generator, covering design-to-code restoration end to end rather than just static asset export.
How to install
Run via npx with a token:
{
"mcpServers": {
"mastergo-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@mastergo/magic-mcp",
"--token=<YOUR_TOKEN>",
"--url=https://mastergo.com"
],
"env": {}
}
}
}
install through the Smithery marketplace for a guided setup, or connect remotely via SSE with no local install at all; Cursor, Cline, LINGMA, and Open Code each have their own equivalent config block documented for the same underlying server.
Who it's for
Designers and developers on a Team Edition MasterGo account who want an AI assistant to turn a design file directly into working HTML or component code, rather than manually translating designs by hand. The project is ISC-licensed.
Source README
MasterGo Magic MCP
MasterGo Magic MCP is a standalone MCP (Model Context Protocol) service designed to connect MasterGo design tools with AI models. It enables AI models to directly retrieve DSL data from MasterGo design files.
Key Features
- Retrieves DSL data from MasterGo design files
- Runs directly with npx
- No external dependencies required, only Node.js environment needed
Tutorial
Example Prompts
Once the MCP server is connected, you can use the following prompts in your AI chat:
Extract SVG and preview in HTML:
Extract SVG and preview in HTML: https://{domain}/file/{fileId}?layer_id={layerId}
Restore a design to code:
Restore design: https://{domain}/file/{fileId}?layer_id={layerId}
Replace {domain}, {fileId}, and {layerId} with your actual values. You can also use short links:
Restore design: https://{domain}/goto/{shortLink}
Restore a design and save as an HTML file:
Restore design, save as HTML file: https://{domain}/file/{fileId}?layer_id={layerId}
You can also use short links:
Restore design, save as HTML file: https://{domain}/goto/{shortLink}
Usage
Obtaining MG_MCP_TOKEN
- Visit https://mastergo.com
- Enter personal settings
- Click the Security Settings tab
- Find the personal access token
- Click to generate the token
Permission Requirements
Important: If the tool is connected but returns a "no permission" error, please check the following conditions:
Account Version Requirement:
- Requires Team Edition or higher MasterGo account
- Personal free edition does not support MCP tool access
File Location Requirement:
- Design files must be placed in Team Projects
- Files in draft box cannot be accessed via MCP tools
Command Line Options
npx @mastergo/magic-mcp --token=YOUR_TOKEN [--url=API_URL] [--rule=RULE_NAME] [--proxy=PROXY_URL] [--debug] [--no-rule]
Parameters:
--token=YOUR_TOKEN(required): MasterGo API token for authentication--url=API_URL(optional): API base URL, defaults to http://localhost:3000--rule=RULE_NAME(optional): Add design rules to apply, can be used multiple times--proxy=PROXY_URL(optional): HTTP/HTTPS proxy URL (e.g.,http://127.0.0.1:7890), also supportsHTTPS_PROXY/HTTP_PROXYenvironment variables--debug(optional): Enable debug mode for detailed error information--no-rule(optional): Disable default rules
You can also use space-separated format for parameters:
npx @mastergo/magic-mcp --token YOUR_TOKEN --url API_URL --rule RULE_NAME --proxy PROXY_URL --debug
Environment Variables
Alternatively, you can use environment variables instead of command line arguments:
MG_MCP_TOKENorMASTERGO_API_TOKEN: MasterGo API tokenAPI_BASE_URL: API base URLRULES: JSON array of rules (e.g.,'["rule1", "rule2"]')HTTPS_PROXY/https_proxy/HTTP_PROXY/http_proxy: HTTP(S) proxy URL (the--proxyargument takes priority)
Installing via Smithery Marketplace
Smithery is an MCP server marketplace that makes it easy to install and manage MCP services.
Method 1: Install via Smithery Website
- Visit Smithery Marketplace
- Click the "Connect" or "Install" button
- Select your MCP client (e.g., Claude Desktop, Cursor, etc.)
- Follow the prompts to complete installation and configuration
LINGMA Usage
Search for LINGMA in the VSCode extension marketplace and install it.
After logging in, click on [MCP tools] in the chat box.
Click on [MCP Square] at the top to enter the MCP marketplace, find the MasterGo design collaboration tool and install it.
After installation, go back to [MCP Servers], and edit our MCP service to replace it with your own MasterGo token.
Finally, switch the chat mode to agent mode in the chat interface.
cursor Usage
Cursor Mcp usage guide reference: https://docs.cursor.com/context/model-context-protocol#using-mcp-tools-in-agent
You can configure the MCP server using either command line arguments or environment variables:
Option 1: Using command line arguments
{
"mcpServers": {
"mastergo-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@mastergo/magic-mcp",
"--token=<YOUR_TOKEN>",
"--url=https://mastergo.com"
],
"env": {}
}
}
}
Option 2: Using environment variables
{
"mcpServers": {
"mastergo-magic-mcp": {
"command": "npx",
"args": ["-y", "@mastergo/magic-mcp"],
"env": {
"MG_MCP_TOKEN": "<YOUR_TOKEN>",
"API_BASE_URL": "https://mastergo.com"
}
}
}
}
Option 3: Using SSE (Streamable HTTP)
No local installation required. The MCP server runs remotely and is accessed via SSE:
{
"mcpServers": {
"mastergo-magic-mcp": {
"type": "http",
"url": "https://mastergo.com/mcp/xf/sse",
"headers": {
"x-mg-useraccesstoken": "<YOUR_TOKEN>"
}
}
}
}
cline Usage
Option 1: Using command line arguments
{
"mcpServers": {
"@master/mastergo-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@mastergo/magic-mcp",
"--token=<YOUR_TOKEN>",
"--url=https://mastergo.com"
],
"env": {}
}
}
}
Option 2: Using environment variables
{
"mcpServers": {
"@master/mastergo-magic-mcp": {
"command": "npx",
"args": ["-y", "@mastergo/magic-mcp"],
"env": {
"MG_MCP_TOKEN": "<YOUR_TOKEN>",
"API_BASE_URL": "https://mastergo.com"
}
}
}
}
Open Code Usage
Open Code uses a mcp configuration block with type: "local" and command array:
{
"mcp": {
"mastergo-magic-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@mastergo/magic-mcp",
"--token=<YOUR_TOKEN>",
"--url=https://mastergo.com"
],
"environment": {
"NPM_CONFIG_REGISTRY": "https://registry.npmjs.org/"
},
"enabled": true
}
}
}
Project Structure
src Directory
The src directory contains the core implementation of the MasterGo Magic MCP service:
index.ts: Entry point of the application that initializes the MCP server and registers all toolshttp-util.ts: Utility for handling HTTP requests to the MasterGo APItypes.d.ts: TypeScript type definitions for the project
src/tools
Contains implementations of MCP tools:
base-tool.ts: Base class for all MCP toolsget-dsl.ts: Tool for retrieving DSL (Domain Specific Language) data from MasterGo design filesget-component-link.ts: Tool for retrieving component documentation from linksget-meta.ts: Tool for retrieving metadata informationget-component-workflow.ts: Tool providing structured component development workflow for Vue and React components, generating workflow files and component specifications
src/markdown
Contains markdown files with additional documentation:
meta.md: Documentation about metadata structure and usagecomponent-workflow.md: Component development workflow documentation guiding structured component development process
Local Development
- Run
yarnandyarn buildto install dependencies and build the code - Find the absolute path of
dist/index.js - Add local MCP configuration with your token
"mastergo-mcp-local": {
"command": "node",
"args": [
"absolute/path/to/dist/index.js",
"--token=mg_xxxxxx",
"--url=https://mastergo.com",
"--debug"
],
"env": {}
},
- Restart your editor to ensure the local MCP is enabled
After successful execution, you can debug based on the local running results. You can build your own MCP service based on your modifications.
We welcome your code contributions and look forward to building MasterGo's MCP service together.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.