Skip to main content
Glama

Figma to React Native MCP

Convert Figma designs to React Native components using Cursor's MCP. This tool extracts components from your Figma designs and generates corresponding React Native components with proper typing and styling.

Installation

For Development

Add to your eas.json:

{
  "mcpServers": {
    "figma-to-code": {
      "command": "node",
      "args": ["PATH_TO_REPO/build/index.js"],
      "env": {
        "FIGMA_TOKEN": "your_figma_token",
        "FIGMA_FILE": "your_figma_file_id",
        "PROJECT_DIR": "your_project_directory"
      }
    }
  }
}

For End Users

Install the MCP server in your Cursor IDE:

npx -y @smithery/cli@latest install @kailashg101/mcp-figma-to-code --client claude --config "{
  \"figmaToken\": \"YOUR_FIGMA_TOKEN\",
  \"figmaFile\": \"YOUR_FIGMA_FILE_ID\",
  \"projectDir\": \"YOUR_PROJECT_DIRECTORY\"
}"

Related MCP server: MCP Figma to React Converter

Usage

After installation, you can use the following prompts in Cursor:

Extract All Components

using the extract_components mcp tool get all components from figma and generate their corresponding react native components in components folder

Extract Specific Component

using the extract_components mcp tool get the [ComponentName] component from figma and generate its corresponding react native component in components folder

Configuration

The config object accepts the following parameters:

{
  "figmaToken": string,    // Your Figma access token
  "figmaFile": string,     // Your Figma file ID (from the URL)
  "projectDir": string     // Where to generate the components
}

Features

Current:

  • ✅ Extract components from Figma

  • ✅ Generate React Native components

  • ✅ Maintain component hierarchy

  • ✅ Handle component props and types

  • ✅ Support nested components

Coming Soon:

  • 🚧 GraphQL schema generation

Development

To contribute or modify:

  1. Clone the repository

  2. Install dependencies:

npm install
  1. Build:

npm run build
  1. Run locally:

npm start

Environment Variables

When running locally, you'll need these in your .env:

FIGMA_TOKEN=your_figma_token
FIGMA_FILE=your_figma_file_id
PROJECT_DIR=your_project_directory

Error Handling

Common errors and solutions:

  • "Failed to create client": Check if all environment variables are properly set

  • "Components page not found": Ensure your Figma file has a page named "Components"

  • "Failed to fetch Figma file": Verify your Figma token and file ID

License

MIT


For issues and feature requests, please open an issue on GitHub.

Available Tools

3 tools
extract-componentsB

Extract all components from Figma file and get all graphql queries and mutations

Inputs: no named parameters.

extract-latest-componentsB

Extract newly added components from Figma file

Inputs: no named parameters.

extract-one-componentC

Extract a single component from Figma file

Inputs: parameters (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are mostly distinct, focusing on different extraction scopes: all components, newly added components, and a single component. However, there is some potential overlap between 'extract-components' and 'extract-latest-components' if an agent needs to understand the difference between 'all' and 'newly added' in practice, but the descriptions clarify this well.

    Naming Consistency5/5

    All tool names follow a consistent 'extract-[adjective]-components' pattern, using snake_case uniformly. The naming is predictable and clear, making it easy for agents to infer functionality from the names alone.

    Tool Count3/5

    With only 3 tools, the set feels thin for a server that converts Figma to React Native, as it lacks tools for other operations like updating, deleting, or managing components. While the tools cover extraction well, the scope suggests more functionality might be needed for a complete workflow.

    Completeness2/5

    The toolset is severely incomplete for the implied domain of converting Figma designs to React Native code. It only provides extraction tools, with no capabilities for generating code, updating components, handling errors, or integrating with React Native projects, leaving significant gaps that will likely cause agent failures in practical use.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers