pixl.directory
Figma logo

Figma

Provide coding agents with design data direct from Figma for far more accurate design implementations in one-shot.

Installation Instructions →

How to Use Model Context Protocol (MCP) in Cursor

What is MCP?

Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLMs (Large Language Models) in Cursor's Composer feature.

Installation Steps

  1. Open Cursor Settings
    • Navigate to Cursor Settings > Features > MCP
    • Click the "+ Add New MCP Server" button
  2. Configure the Server
    • Name: Give your server a nickname
    • Type: Select the transport type (stdio or sse)
    • Command/URL: Enter either:
      • For SSE servers: The URL of the SSE endpoint
      • For stdio servers: A valid shell command to run the server

Example Configurations

For stdio Server (Figma Example):

Command: node ~/mcp-quickstart/figma-server/build/index.js --access-token $FIGMA_ACCESS_TOKEN --file-key $FIGMA_FILE_KEY

For SSE Server:

URL: https://api.figma.com/v1/files/:file_key/sse

Using MCP Tools

Tool Availability

  • • After adding a server, it will appear in your MCP servers list
  • • You may need to click the refresh button to populate the tool list

Using Tools in Composer

  • • The Composer Agent automatically uses MCP tools when relevant
  • • You can explicitly prompt tool usage by:
    • Referring to the tool by name
    • Describing the tool's function

Tool Execution Process

  • • Displays a message in chat requesting approval
  • • Shows tool call arguments (expandable)
  • • Executes the tool upon user approval
  • • Displays the tool's response in the chat

Important Notes

  • • MCP tools may not work with all models
  • • MCP tools are only available to the Agent in Composer
  • • For Figma integration, you need to set up FIGMA_ACCESS_TOKEN and FIGMA_FILE_KEY environment variables
  • • Create a personal access token from your Figma account settings
  • • Get the file key from your Figma file URL (after figma.com/file/)
  • • For security, use a wrapper script that sets the environment variables before running the server
  • • Ensure your access token has the necessary permissions for file access and asset export
  • • Consider using team-specific access tokens for collaborative projects
← Back to Home