Mastergomcp

Created By
mastergo-design5 months ago
获取 MG_MCP_TOKEN 1. 访问 https://mastergo.com 2. 进入个人设置 3. 点击安全设置选项卡 4. 找到个人访问令牌 5. 点击生成令牌 设计文件必须放在有权限的团队项目中(团队版及团队版以上权限) 草稿箱中的文件无法通过 MCP 工具访问
Overview

what is MasterGo Magic MCP?

MasterGo Magic MCP is a standalone Model Context Protocol (MCP) service that connects MasterGo design tools with AI models, allowing for the retrieval of DSL data from MasterGo design files.

how to use MasterGo Magic MCP?

To use MasterGo Magic MCP, you need to obtain an MG_MCP_TOKEN from the MasterGo website and run the service using Node.js with the command line options provided in the documentation.

key features of MasterGo Magic MCP?

  • Retrieves DSL data from MasterGo design files.
  • Runs directly with npx, requiring only a Node.js environment.
  • No external dependencies needed.

use cases of MasterGo Magic MCP?

  1. Integrating AI models with design tools for enhanced functionality.
  2. Automating the retrieval of design specifications from MasterGo files.
  3. Facilitating collaboration in design projects through AI assistance.

FAQ from MasterGo Magic MCP?

  • What is the requirement for using MCP tools?

You need a Team Edition or higher MasterGo account, as personal free editions do not support MCP tool access.

  • Can I access files in the draft box?

No, design files must be placed in Team Projects to be accessed via MCP tools.

  • How do I install the service?

You can install it via the Smithery Marketplace or by using command line arguments with npx.

Server Config

{
  "mcpServers": {
    "mastergo-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mastergo/magic-mcp",
        "--token=your-token",
        "--url=https://mastergo.com/"
      ],
      "env": {
        "NPM_CONFIG_REGISTRY": "https://registry.npmjs.org/"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
mastergo-design
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago