Skip to main content
Glama
Sign In
enesjakozh
Figma MCP Server

Figma MCP Server

by deepsuthar496
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Figma MCP Server

A Model Context Protocol (MCP) server that provides integration with Figma's API, allowing you to interact with Figma files, comments, components, and more.

Features

  • File Operations

    • Get file information

    • Get file version history

    • Get file components

  • Comment Management

    • List comments in files

    • Add new comments

    • Delete comments

  • Project & Team Features

    • List team projects

    • Get project files

    • Get published styles

  • Webhook Management

    • Create webhooks

    • List existing webhooks

    • Delete webhooks

Related MCP server: Figma MCP Server

Installation

Installing via Smithery

To install Figma MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @deepsuthar496/figma-mcp-server --client claude

Manual Installation

  1. Clone the repository

  2. Install dependencies:

npm install

  1. Build the server:

npm run build

Configuration

Configure the server in your MCP settings file with your Figma access token:

{
  "mcpServers": {
    "figma": {
      "command": "node",
      "args": ["path/to/figma-server/build/index.js"],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-access-token-here"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Available Tools

File Operations

get_file

Get information about a Figma file

{
  "file_key": "string"
}

get_file_versions

Get version history of a file

{
  "file_key": "string"
}

get_file_components

Get components in a file

{
  "file_key": "string"
}

Comment Management

get_file_comments

Get comments from a file

{
  "file_key": "string"
}

post_comment

Post a comment to a file

{
  "file_key": "string",
  "message": "string"
}

delete_comment

Delete a comment from a file

{
  "file_key": "string",
  "comment_id": "string"
}

Project & Team Operations

get_team_projects

Get projects for a team

{
  "team_id": "string"
}

get_project_files

Get files in a project

{
  "project_id": "string"
}

get_component_styles

Get published styles

{
  "team_id": "string"
}

Webhook Management

create_webhook

Create a webhook

{
  "team_id": "string",
  "event_type": "string",
  "callback_url": "string"
}

get_webhooks

List webhooks

{
  "team_id": "string"
}

delete_webhook

Delete a webhook

{
  "webhook_id": "string"
}

Usage Example

// Example using the MCP tool to get file information
<use_mcp_tool>
<server_name>figma</server_name>
<tool_name>get_file</tool_name>
<arguments>
{
  "file_key": "your-file-key"
}
</arguments>
</use_mcp_tool>

License

MIT

Contributing

  1. Fork the repository

  2. Create your feature branch

  3. Commit your changes

  4. Push to the branch

  5. Create a new Pull Request

Available Tools

5 tools
add_figma_fileC

Add a Figma file to your context

Inputs: url (required).

post_commentC

Post a comment on a node in a Figma file

Inputs: file_key (required), message (required), x (required), y (required), +1 more.

read_commentsC

Get all comments on a Figma file

Inputs: file_key (required).

reply_to_commentC

Reply to an existing comment in a Figma file

Inputs: comment_id (required), file_key (required), message (required).

view_nodeC

Get a thumbnail for a specific node in a Figma file

Inputs: file_key (required), node_id (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: adding files, posting comments, reading comments, replying to comments, and viewing nodes. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., add_figma_file, post_comment, read_comments, reply_to_comment, view_node). This uniformity enhances readability and predictability for agents.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of managing Figma files and comments. Each tool serves a specific, necessary function without bloat or redundancy.

    Completeness4/5

    The toolset covers core operations for file management and comment interactions, but lacks CRUD coverage for files (e.g., no update or delete file tools). However, agents can likely work around this minor gap for basic workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches