figmaMCP_server

This MCP server provides a Figma REST API surface that analyzes Figma designs and suggests HTML/CSS/JS code structures. It exposes a set of tools you can invoke via the MCP client (e.g., Claude Desktop or Cursor) to inspect the entire Figma file, list components, retrieve design tokens, analyze node styles, and export assets like images. The server reads the FIGMA_ACCESS_TOKEN from the environment to authenticate with the Figma API, enabling operations such as get_figma_file, get_figma_components, get_figma_styles, get_figma_nodes, extract_text_content, get_node_styles, and export_figma_images. To use it, start the server (see installation section) and configure your MCP client to point at the generated dist/server.js entry, providing the access token in env so the client can perform authenticated requests.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a Figma Personal Access Token

Installation steps:

1. Clone the repository and install dependencies

git clone <your-repo-url>
cd figmaMCP_server
npm install

2. Create and configure environment variables

# Copy example env and edit with real token
cp .env.example .env
# Open .env and set FIGMA_ACCESS_TOKEN=your-figma-token

3. Build the project

npm run build

4. Run or configure MCP clients

• To run directly (production):

npm start

• To connect via MCP clients (Claude Desktop or Cursor), configure the client with the following server entry but use your absolute path to dist/server.js:

{
  "mcpServers": {
    "figma-rest-api": {
      "command": "node",
      "args": ["/절대/경로/figmaMCP_server/dist/server.js"],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-figma-token"
      }
    }
  }
}

Note: Ensure the dist/server.js path is absolute and exists after a successful npm run build.

Tips and considerations:

• Do not commit the .env file to version control; keep sensitive tokens secure.
• After changing environment variables, restart the MCP client to activate the tools.
• If the MCP tool does not appear, verify the absolute path to dist/server.js and that dist/server.js exists after building.
• If you encounter module or build errors, try removing node_modules and reinstalling: rm -rf node_modules package-lock.json; npm install; npm run build.
• Verify the environment variable is loaded by checking that FIGMA_ACCESS_TOKEN is present in the server process environment.
• The server expects a valid Figma Personal Access Token for API access; tokens are token-per-user and should be kept confidential.