# MasterGo MCP > MasterGo connects your AI client to a professional UI/UX design platform, letting your agent navigate complex project files, layers, and style libraries via natural conversation. You can list all assets, audit typography, check version history, or pull team comments without ever touching the visual workspace. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** ui-ux-design, design-collaboration, prototyping, design-systems, workflow-automation, asset-management ## Description MasterGo hooks your AI agent directly into a professional UI/UX design platform. You don't gotta click through dozens of nested files and layers; you just tell your agent what you need to know about the project, and it spits out clean data right in the chat window. This server lets your agent manage complex design file navigation and coordination as if it were an actual teammate sitting next to you. When you're deep in a massive file, you can map out its exact internal architecture. The `list_nodes` tool returns every single node, frame, and layer that makes up the file’s structure, letting you see exactly how things are nested without opening the visual workspace. You can also get detailed metadata on any specific design file using `get_file`, giving you a full overview of its properties. To manage your entire project scope, you've got several tools at your disposal. Start by listing all high-level team projects available in your MasterGo account with `list_projects`. If you need to see every single design file and project that’s accessible across the whole workspace, run `list_files`. You can also get a clean view of which functional teams are set up using `list_teams`, or find out who's working on a specific job by pulling all design files related to a team project via `get_project_files`. When it comes to people, you don’t gotta hunt through company directories. Use `get_org_members` and you'll get a list of every individual belonging to your MasterGo organization. That’s quick personnel checking right there in the chat. Design consistency is everything, so knowing what styles you're using is key. The `list_styles` tool returns an exhaustive list of all defined design styles—you can check color palettes, typography variables, and other reusable elements used across every file. You’ll also find a way to see the version history for any given file; running `get_file_versions` pulls a complete timeline that shows you every major change and milestone in the file's life. Collaboration tracking is simple. If you need team feedback, use `get_comments` to retrieve all comments left on a specific design file. You can also check out who’s involved by listing all members of your organization using `get_org_members`. All this data—the history, the styles, the people, and the structure—is pulled into plain text for you to work with immediately. ## Tools ### get_comments Retrieves all comments left on a specific design file, showing team feedback. ### get_file Fetches the detailed metadata for any specified MasterGo design file. ### get_file_versions Lists the version history of a file, tracking every major change and milestone. ### get_org_members Pulls a list of all individuals who belong to your MasterGo organization. ### get_project_files Retrieves all the design files associated with a specific team project. ### list_files Lists every single accessible design file and project within your MasterGo workspace. ### list_nodes Returns the internal nodes, frames, and layers that make up a given design file's structure. ### list_projects Lists all high-level team projects available in your MasterGo account. ### list_styles Returns a list of defined design styles, including colors and typography variables, used across files. ### list_teams Displays the names and IDs of all functional teams set up in MasterGo. ## Prompt Examples **Prompt:** ``` List all design files in my MasterGo workspace. ``` **Response:** ``` I've retrieved your MasterGo design files. You have 4 active files, including 'Landing Page V2' and 'Mobile Design System'. Which one would you like to explore? ``` **Prompt:** ``` Show me the comments for file 'design-8821'. ``` **Response:** ``` I've listed the comments for 'design-8821'. There are 5 recent threads, including feedback on the header color and mobile navigation. Would you like a detailed summary? ``` **Prompt:** ``` Retrieve the style library for file 'core-ui-library'. ``` **Response:** ``` I've retrieved the styles for 'core-ui-library'. It includes 12 color variables and 8 typography styles. Would you like me to list them all for you? ``` ## Capabilities ### List Project Assets The agent pulls lists of all available design projects and files in the MasterGo workspace. ### Retrieve File Structure You can map out a file's internal architecture by listing its nodes, layers, and frames. ### Audit Design Styles The tool lists all defined design styles—like color palettes or font pairings—used across your files. ### Track Collaboration History Retrieve file comments and track changes to monitor team feedback directly in the chat interface. ### Check Version Timeline The agent pulls a complete history of design files, allowing you to see past versions and milestones. ### Identify Team Members List all users who are members of the organization or team for quick personnel checks. ### Manage Teams Browse available teams within your MasterGo workspace structure. ## Use Cases ### The Design System Audit A Design Ops specialist needs to ensure that every instance of the primary brand color (e.g., #FF00AA) is defined consistently across three separate projects. Instead of opening three different file structures, they prompt the agent: 'What are all the styles for my brand colors?' The agent runs `list_styles` and returns a comprehensive list, flagging any missing or incorrectly named variables. ### Understanding a Legacy Feature A Product Manager joins a project mid-development. They need to know the component breakdown of an old landing page design. They prompt: 'Show me the structure for the V1 header.' The agent runs `list_nodes` and provides a detailed hierarchy (header -> logo, hero section, CTA block), letting them understand the asset grouping instantly. ### Tracking Design Drift A developer notices that a button component looks different in one file compared to another. They ask the agent: 'Compare the V2 and V3 versions of the primary button.' The agent runs `get_file_versions` and then uses `list_nodes` on both versions, showing exactly which nodes changed between milestones. ### Quick Team Status Check A PM needs to know who left feedback on the main dashboard design before a meeting. They prompt: 'Show me all comments for the Dashboard V4 file.' The agent runs `get_comments` and provides a list of users, along with snippets of their recent feedback, saving them from manual inbox checking. ## Benefits - Check team comments using `get_comments`. Instead of clicking into a file and scrolling through comment threads, you just ask the agent for feedback on 'design-8821', getting a summary immediately. - Audit entire style libraries with `list_styles`. You don't have to manually check dozens of files to verify if your primary brand color is used correctly; the tool lists every defined variable instantly. - Track file evolution using `get_file_versions`. Need to know when a specific component was introduced or changed? The agent gives you the full version timeline, so you never lose track of milestones. - Map out complex structures with `list_nodes`. You can pull the entire internal map of a screen by listing all nodes and layers in a file, giving you a complete structural overview without opening any tabs. - Keep everyone aligned by checking team structure using `get_org_members` or `list_teams`. Quickly confirm who owns which design system component across different teams. - Streamline project setup with `get_project_files`. Instead of navigating the file tree, you ask for 'all files related to the checkout flow' and get a targeted list immediately. ## How It Works The bottom line is: you use conversational prompts to execute complex data retrieval tasks that normally require clicking through multiple UI sections. 1. First, subscribe to the MasterGo MCP server and input your API Token (X-MG-Authentication). 2. Next, connect this server to your preferred AI client (Claude, Cursor, etc.). 3. You then prompt your agent with natural language requests—for example, 'List all files in the mobile design system'—and get structured data back. ## Frequently Asked Questions **How do I obtain a MasterGo API Token?** Log in to MasterGo, go to the [Developer Center](https://mastergo.com/developers), and create a new application or generate a personal access token under your account settings. **Can I read specific layer information through this server?** Yes. Use the `list_nodes` tool with the file key and optional node IDs. This allows your agent to retrieve detailed data about frames, layers, and their properties. **What is a 'fileKey' in MasterGo?** The `fileKey` is the unique identifier found in the URL of your MasterGo design file. It typically appears after `/file/` in the browser address bar. **If I run `get_file` and the design file doesn't exist, what does MasterGo tell my agent?** The tool returns a structured error message indicating 'File Not Found.' This prevents your AI client from crashing; it just gives you clean data to handle the exception in your workflow. **When using `list_styles`, can my agent filter design styles by type, like only colors or only typography?** The tool retrieves a comprehensive list of all defined styles across the file. You'll need to process that full data structure within your client to narrow down results (e.g., checking for hex codes vs. font names). **Are there usage limits or rate limits when calling `list_files`?** Vinkius manages throttling based on your subscription tier. We recommend batching multiple requests rather than running continuous, rapid-fire calls to maintain smooth agent performance. **How does the `get_file_versions` tool limit the amount of historical data it retrieves?** It pulls the most recent 50 version records by default. To keep your prompts concise, you should specify a date range in your agent’s prompt to focus only on relevant milestones. **Using `get_org_members`, how can my agent determine if an account has editing rights?** This tool lists all organization members and their roles. The data structure includes role information, which you must check against your project's required permissions to confirm edit access.