Figma MCP Toolkit MCP Server

MCP server for converting Figma designs to React Native components

Local serverstdioTypeScript

What is the Figma MCP Toolkit MCP server?

Figma mcp toolkit mcp server connects Figma MCP Toolkit to AI assistants that speak the Model Context Protocol. MCP server for converting Figma designs to React Native components.

What Figma MCP Toolkit does

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.

Key capabilities

  • ✅ Extract components from Figma
  • ✅ Generate React Native components
  • ✅ Maintain component hierarchy
  • ✅ Handle component props and types
  • ✅ Support nested components
  • 🚧 GraphQL schema generation

Installing the figma mcp toolkit mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 5 environment variables: FIGMA_TOKEN, FIGMA_FILE, PROJECT_DIR, YOUR_FIGMA_TOKEN, YOUR_FIGMA_FILE_ID. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Figma MCP Toolkit sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by kailashAppDev, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the figma mcp toolkit mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

How to install the Figma MCP Toolkit MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
FIGMA_TOKENCredential the server authenticates with.Yes
FIGMA_FILEConfiguration value read at startup.Optional
PROJECT_DIRFilesystem location the server is allowed to use.Optional
YOUR_FIGMA_TOKENCredential the server authenticates with.Yes
YOUR_FIGMA_FILE_IDConfiguration value read at startup.Optional

Frequently asked questions

It connects Figma MCP Toolkit to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Figma MCP Toolkit directly.