Skip to main content
Glama

Gravity Global Figma MCP

Gravity Global Figma MCP is a tool that integrates Figma with Cursor through the Model Context Protocol (MCP), allowing you to retrieve and optimize design data from Figma for code conversion.

Key Features

  • Figma Data Retrieval: Get design information from Figma files using URLs or file IDs

  • Data Optimization: Reduce JSON size by removing unnecessary properties

  • CSS Conversion: Automatically divide and organize styles into groups (typography, colors, layouts...)

  • CSS Class Name Generation: Automatically create meaningful class names based on properties

  • Design Tokens Extraction: Extract typography and color tokens from Figma designs

Related MCP server: Talk to Figma MCP

Installation

  1. Clone the repository:

git clone <repository-url>
  1. Install dependencies:

npm install
  1. Create a .env file and add your Figma API token:

FIGMA_API_KEY=your_figma_api_token_here
  1. Run the MCP server:

node index.js

Usage

In Cursor Chat

You can use the following tools through Cursor Chat:

1. Retrieve Data from Figma

Get data from Figma URL https://www.figma.com/file/abc123/my-design?node-id=123-456

Result: The MCP will return optimized Figma data.

2. Extract Design Tokens

Extract typography and color tokens from Figma URL https://www.figma.com/file/abc123/my-design

Result: The MCP will return a JSON object containing typography and color tokens extracted from the Figma design.

Example response:

{
  "typography": {
    "opensans-600-32": {
      "fontFamily": "Open Sans",
      "fontSize": "32px",
      "fontWeight": 600,
      "lineHeight": "48px"
    },
    "avenirnext-400-16": {
      "fontFamily": "Avenir Next",
      "fontSize": "16px",
      "fontWeight": 400,
      "lineHeight": "24px"
    }
  },
  "colors": {
    "bg-ffffff": "#ffffff",
    "text-030e12": "#030e12"
  }
}

3. Options

  • figmaDesign tool:

    • fullJson=true: Returns full uncompressed JSON data

    • cleanData=true: Removes unnecessary properties for HTML/CSS rendering

  • figmaTokens tool:

    • tokenTypes=["typography"]: Only extract typography tokens

    • tokenTypes=["colors"]: Only extract color tokens

    • tokenTypes=["typography", "colors"]: Extract both (default)

Example:

Extract only color tokens from Figma URL https://www.figma.com/file/abc123/my-design

Data Structure

The converted Figma data has the following structure:

{
  "nodes": {
    "nodeId": {
      "id": "nodeId",
      "name": "Node Name",
      "type": "FRAME",
      "fillStyleId": "style123",
      "layoutStyleId": "style456",
      "children": [...]
    }
  },
  "styles": {
    "style123": {
      "backgroundColor": "#ffffff",
      "opacity": 1,
      "categories": { "colors": "color1" }
    }
  },
  "optimizedStyles": {
    "typography": {...},
    "colors": {...},
    "layout": {...},
    "spacing": {...},
    "sizing": {...}
  },
  "classNames": {
    "style123": "bg-1",
    "style456": "flex-row-1"
  }
}

Technical Details

Figma Data Retrieval

The tool uses the Figma REST API to fetch design data. It supports URLs from both regular files and new design URLs. You can specify a particular node using node-id.

Data Optimization

The optimization process includes these steps:

  1. Removing unnecessary properties

  2. Dividing styles into groups (typography, colors, layout...)

  3. Merging similar styles to reduce duplication

  4. Automatically generating CSS class names

Token Extraction

The token extraction process:

  1. Identifies typography and color styles used in the design

  2. Creates standardized naming conventions for each token

  3. Groups tokens by type (typography or colors)

  4. Removes duplicates and organizes them for easy integration with design systems

Limitations

  • MCP has limitations on the size of returned data; large files will be saved to the figma_data directory

  • Complex vector properties are not fully preserved

  • Complex gradients and effects may require additional processing

License

MIT License

Available Tools

1 tool
figmaDesignD
ParametersJSON Schema
NameRequiredDescriptionDefault
figmaUrlYesFigma URL or file ID
fullJsonNoIf true, returns full uncompressed JSON data
cleanDataNoIf true, removes unnecessary properties for HTML/CSS rendering

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

D1.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools.

Naming Consistency5/5

A single tool trivially follows a consistent naming pattern with itself.

Tool Count1/5

One tool for a Figma MCP is extremely limited; a typical Figma integration would require many more operations, making this an extreme mismatch.

Completeness1/5

The tool has no description, and a single tool cannot cover the expected domain of Figma operations (e.g., fetching designs, components, etc.), indicating severe incompleteness.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nguyenlegravityglobal/figma-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server