Gravity Global Figma MCP
With the Gravity Global Figma MCP server, you can:
Retrieve Design Data: Fetch design information from Figma using URLs or file IDs
Data Optimization Options:
Return full, uncompressed JSON data (
fullJson=true)Clean unnecessary properties for HTML/CSS rendering (
cleanData=true)Divide styles into categories and merge similar styles
Automatically generate CSS class names
Extract Design Tokens: Pull typography and color tokens from Figma designs with options to specify token types
Converts Figma design elements into organized CSS styles, automatically divides styles into logical groups (typography, colors, layouts), and generates meaningful class names based on properties.
Enables configuration of the MCP server using environment variables stored in a .env file, particularly for storing the Figma API token.
Retrieves and optimizes design data from Figma files, extracts design tokens (typography and colors), converts design elements to CSS, and generates CSS class names based on design properties.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gravity Global Figma MCPExtract typography and color tokens from Figma URL https://www.figma.com/file/abc123/my-design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Clone the repository:
git clone <repository-url>Install dependencies:
npm installCreate a
.envfile and add your Figma API token:
FIGMA_API_KEY=your_figma_api_token_hereRun the MCP server:
node index.jsUsage
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-456Result: 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-designResult: 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-designData 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:
Removing unnecessary properties
Dividing styles into groups (typography, colors, layout...)
Merging similar styles to reduce duplication
Automatically generating CSS class names
Token Extraction
The token extraction process:
Identifies typography and color styles used in the design
Creates standardized naming conventions for each token
Groups tokens by type (typography or colors)
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_datadirectoryComplex vector properties are not fully preserved
Complex gradients and effects may require additional processing
License
MIT License
Available Tools
1 toolfigmaDesignD
| Name | Required | Description | Default |
|---|---|---|---|
| figmaUrl | Yes | Figma URL or file ID | |
| fullJson | No | If true, returns full uncompressed JSON data | |
| cleanData | No | If true, removes unnecessary properties for HTML/CSS rendering |
TDQS
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.
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.
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.
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.
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.
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
With only one tool, there is no possibility of confusion between tools.
A single tool trivially follows a consistent naming pattern with itself.
One tool for a Figma MCP is extremely limited; a typical Figma integration would require many more operations, making this an extreme mismatch.
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
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
The Figma MCP server brings Figma design context directly into your AI workflow.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Turn any live website into brand colors, fonts, design tokens, SVGs, Lottie and paste-ready code.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that integrates Figma design files with AI coding tools like Cursor, Windsurf, and Cline, allowing AI tools to access and understand Figma design data for generating more accurate code.47430MIT
- AlicenseBqualityDmaintenanceAllows Cursor AI to communicate with Figma for reading designs and modifying them programmatically through a Model Context Protocol integration.388941MIT
- FlicenseNot gradedqualityDmaintenanceProvides secure access to Figma designs through Cursor IDE using a personal access token, enabling developers to list files, export assets, extract design tokens, and search designs without requiring individual Figma accounts.
- AlicenseNot gradedqualityDmaintenanceEnables Cursor AI to read and modify Figma designs via the Model Context Protocol, allowing programmatic control over documents, components, styles, and more.894MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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