Skip to main content
Glama
MasterGo Magic MCP

MasterGo Magic MCP

by eDramas

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

Related MCP server: Figma MCP Server

Tutorial

Usage

Obtaining MG_MCP_TOKEN

  1. Visit https://mastergo.com

  2. Enter personal settings

  3. Click the Security Settings tab

  4. Find the personal access token

  5. Click to generate the token

Command Line Options

npx @mastergo/magic-mcp --token=YOUR_TOKEN [--url=API_URL] [--rule=RULE_NAME] [--debug]

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

  • --debug (optional): Enable debug mode for detailed error information

You can also use space-separated format for parameters:

npx @mastergo/magic-mcp --token YOUR_TOKEN --url API_URL --rule RULE_NAME --debug

cursor Usage

Cursor Mcp usage guide reference: https://docs.cursor.com/context/model-context-protocol#using-mcp-tools-in-agent

{
  "mcpServers": {
    "mastergo-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mastergo/magic-mcp",
        "--token=<MG_MCP_TOKEN>",
        "--url=https://mastergo.com"
      ],
      "env": {}
    }
  }
}

cline Usage

{
  "mcpServers": {
    "@master/mastergo-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mastergo/magic-mcp",
        "--token=<MG_MCP_TOKEN>",
        "--url=https://mastergo.com"
      ],
      "env": {}
    }
  }
}

License

ISC

Available Tools

2 tools
mcp__getDslA

"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."

Inputs: fileId (required), layerId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers