MasterGo Magic MCP

Finalize generated design code: replace ALL placeholders (SVG icons + long text) with real high-precision data from the design cache, then write the final file directly to disk.

WHAT it does:

1. Replaces every @@SVG:{svgShortKey}@@ placeholder with the real high-precision <svg> markup from the SVG cache (character-for-character exact, no rounding).
2. Replaces every T{sectionIndex}|{nodeId} text placeholder with the real long text from the text cache.
3. Detects fabricated (hand-written) <path d="..."> that were NOT injected via placeholders — reports them as errors.
4. Writes the finalized code directly to {outDir}/{outputFileName} on disk.

CRITICAL — outDir is MANDATORY: Always provide outDir so the finalized code is written directly to disk. This ensures the server-injected data reaches the file WITHOUT any LLM re-processing. Do NOT copy the code back into your response and re-output it — that causes precision loss. The file written by this tool IS the final deliverable.

PLACEHOLDER FORMATS:

• SVG icons: @@SVG:{svgShortKey}@@ — svgShortKey comes from the PATH node's svgShortKey field in the section DSL. Example: <span class="icon">@@SVG:S0#0@@</span>
• Long text: T{sectionIndex}|{nodeId} — appears in TEXT nodes whose text was too long for inline DSL. Example: <p>T3|1:1234:5678</p>

The server escapes the injected data according to the targetLang parameter:

• html (default, also for Vue templates): place the placeholder in element content (<span>@@SVG:S0#0@@</span>, <p>T3|1:2</p>). SVG is inserted as-is; long text is HTML-escaped (& < >).
• dart (Flutter): place the placeholder inside a single-quoted string literal (SvgPicture.string('@@SVG:S0#0@@'), Text('T3|1:2')). SVG/text are escaped for that string (\ ' newline). Pass targetLang: "dart".

Pick targetLang to match the code you generated, and place placeholders in that language's standard position shown above.

You can provide either:

1. fileId and layerId directly, or
2. a short link (like https://{domain}/goto/LhGgBAK)

IMPORTANT: Call this tool with the COMPLETE code string. After the tool writes the file, you are DONE — do NOT output or edit the code further.

Sends a local HTML file to MasterGo so the code is synced back into the design file. Addressed by file ID or by a short link, with an optional layer ID taken only from a layer_id URL parameter.

Extract SVG data from MasterGo design files. This tool retrieves the DSL from a design layer, finds all PATH nodes (typically inside INSTANCE/icon components), resolves their color references, and generates SVG markup strings. You can provide either:

1. fileId and layerId directly, or
2. a short link (like https://{domain}/goto/LhGgBAK)

Pagination: When there are many icons, use the first call without "page" to get totalCount. Then call again with page=0, page=1, etc. (page starts at 0, pageSize defaults to 20, max 100). If hasMore is false, you've fetched all pages.

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.

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.

Fetches design-to-code data from MasterGo and writes it to disk: the returned code as HTML, and SVG and image resources under their resource path. Returns a summary rather than the assets themselves.

Returns the sections of a design file with their id, name, type, node count, text preview and page-absolute bounding box, plus the total section and node counts. Pass a section index to get that section's contents instead of the overview.

[FALLBACK] Use only when mcp__getDesignSections is unavailable or returns an error. This returns the FULL DSL in one response — may be large and exceed context limits for complex designs. Prefer mcp__getDesignSections as the primary tool for all designs. You can provide either:

1. fileId and layerId directly, or
2. a short link (like https://{domain}/goto/LhGgBAK)

This tool returns the raw DSL data that you can then parse and analyze. Use the optional 'format' parameter (json/yaml/tree, defaults to json) to control the serialization. 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.

Users need to actively call this tool to get the Flutter component development workflow. When Flutter Generator or Flutter Component is mentioned, please actively call this tool. This tool provides a structured workflow for Flutter component development following best practices. It includes MasterGo DSL to Flutter Widget mapping rules, screen adaptation with flutter_screenutil, and feature-based architecture guidance. It also downloads all image resources from the design file to local disk, rewrites CSS and DSL references to point at Flutter asset paths, and generates an asset manifest. You must provide an absolute rootPath of workspace to save workflow files.

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.

the current version is 0.2.7