figma

This MCP server provides an interface to Figma's API via the MCP protocol, exposing read-only access to Figma files and projects and enabling Claude Desktop and other MCP clients to query file data efficiently. The server supports essential tools for retrieving file details and listing files, as well as creating design system tokens and themes in a read-enabled workflow. To use it, start the server with your Figma access token and connect via an MCP client. The available tools include get-file for fetching file metadata, list-files for enumerating files in a project, and basic design-system operations such as create-variables and create-theme (subject to API capabilities and permissions in your token). The server also includes caching, error handling, and monitoring capabilities to improve performance and observability.

Prerequisites

• Node.js 18.x or higher
• npm (comes with Node.js)
• Access token for Figma API with appropriate permissions (personal access token)

1. Clone or install the package

• If publishing from npm: npm install figma-mcp-server
• If developing from source: git clone https://github.com/your-org/figma-mcp-server.git cd figma-mcp-server npm install

2. Build (if using TypeScript source)

• npm run build

3. Run the server (example)

• FIGMA_ACCESS_TOKEN=your_token_here MCP_SERVER_PORT=3000 npm start

4. Verify the server is running

• Check logs for startup messages and health checks
• Connect with an MCP client using the server address on port 3000

Tips and common considerations:

• Ensure you provide a valid Figma personal access token with the necessary permissions. The server currently supports read-only operations; write operations require elevated permissions or plugin workflows.
• Environment variables are essential. Set FIGMA_ACCESS_TOKEN and MCP_SERVER_PORT, and consider enabling DEBUG for troubleshooting.
• Claude Desktop configuration requires absolute paths and may require recompilation when updating the server binary or dist files.
• If you see JSON connection errors in Claude, verify that the path to dist/index.js is absolute and that the server has been built before starting Claude Desktop.
• For large projects, consider tuning the in-memory cache TTL and size according to your workload and memory constraints.
• This MCP server uses both stdio and SSE transports; ensure clients are configured to use the supported transport accordingly.