by mastergo-design
Extract design file metadata from MasterGo for analysis or code with ease. Great for web page design programs or convert
β 216
GitHub stars
Extracts design file metadata and DSL data from MasterGo design files using a personal access token. Enables AI models to analyze design elements and generate code from MasterGo projects.
MasterGo Design is an official MCP server published by mastergo-design that provides AI assistants with tools and capabilities via the Model Context Protocol. Extract design file metadata from MasterGo for analysis or code with ease. Great for web page design programs or convert It is categorized under developer tools, design.
You can install MasterGo Design in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
MasterGo Design is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research β Summarize β Create document β Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Strong directory entry: MasterGo Design surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired MasterGo Design into a staging workspace; the listingβs GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: MasterGo Design surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired MasterGo Design into a staging workspace; the listingβs GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: MasterGo Design is the kind of server we cite when onboarding engineers to host + tool permissions.
MasterGo Design reduced integration guesswork β categories and install configs on the listing matched the upstream repo.
We evaluated MasterGo Design against two servers with overlapping tools; this profile had the clearer scope statement.
MasterGo Design is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: MasterGo Design surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend MasterGo Design for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 25
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.
Important: If the tool is connected but returns a "no permission" error, please check the following conditions:
Account Version Requirement:
File Location Requirement:
npx @mastergo/magic-mcp --token=YOUR_TOKEN [--url=API_URL] [--rule=RULE_NAME] [--debug] [--no-rule]
--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--debug (optional): Enable debug mode for detailed error information--no-rule (optional): Disable default rulesYou can also use space-separated format for parameters:
npx @mastergo/magic-mcp --token YOUR_TOKEN --url API_URL --rule RULE_NAME --debug
Alternatively, you can use environment variables instead of command line arguments:
MG_MCP_TOKEN or MASTERGO_API_TOKEN: MasterGo API tokenAPI_BASE_URL: API base URLRULES: JSON array of rules (e.g., '["rule1", "rule2"]')Smithery is an MCP server marketplace that makes it easy to install and manage MCP services.
Search for LINGMA in the VSCode extension marketplace and install it.
<img src="https://github.com/mastergo-design/mastergo-magic-mcp/blob/main/images/image-20250507174245589.png" alt="image-20250507174245589" style="zoom:25%;" />After logging in, click on [MCP tools] in the chat box.
<img src="https://github.com/mastergo-design/mastergo-magic-mcp/blob/main/images/image-20250507174511910.png" alt="image-20250507174511910" style="zoom:25%;" />Click on [MCP Square] at the top to enter the MCP marketplace, find the MasterGo design collaboration tool and install it.
<img src="https://github.com/mastergo-design/mastergo-magic-mcp/blob/main/images/image-20250507174840456.png" alt="image-20250507174840456" style="zoom:25%;" />After installation, go back to [MCP Servers], and edit our MCP service to replace it with your own MasterGo token.
<img src="https://github.com/mastergo-design/mastergo-magic-mcp/blob/main/images/image-20250507175005364.png" alt="image-20250507175005364" style="zoom:25%;" />Finally, switch the chat mode to agent mode in the chat interface.
<img src="https://github.com/mastergo-design/mastergo-magic-mcp/blob/main/images/image-20250507175107044.png" alt="image-20250507175107044" style="zoom:25%;" />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=<MG_MCP_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 1: Using command line arguments
{
"mcpServers": {
"@master/mastergo-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@mastergo/magic-mcp",
"--token=<MG_MCP_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"
}
}
}
}
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 projectContains 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 specificationsContains markdown files with additional documentation:
meta.md: Documentation about metadata structure and usagecomponent-workflow.md: Component development workflow documentation guiding structured component development processyarn and yarn build to install dependencies and build the codedist/index.js"mastergo-mcp-local": {
"command": "node",
"args": [
"absolute/path/to/dist/index.js",
"--token=mg_xxxxxx",
"--url=https://mastergo.com",
"--debug"
],
"env": {}
},
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.
ISC
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
β Do
β Don't
π‘ Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
β Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
β Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.