Skip to main content
Glama
JayZeeDesign

figma-mcp

by JayZeeDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FIGMA_API_TOKENNo

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_componentsB

Get components available in a Figma file

    Args:
        file_key (str): The file key found in the shared Figma URL

    Returns:
        list[dict]: List of components found in the Figma file
get_nodeA

Get a specific node from a Figma file

    Args:
        file_key (str): The file key found in the shared Figma URL, e.g. if url is https://www.figma.com/proto/do4pJqHwNwH1nBrrscu6Ld/Untitled?page-id=0%3A1&node-id=0-3&viewport=361%2C361%2C0.08&t=9SVttILbgMlPWuL0-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=0%3A3, then the file key is do4pJqHwNwH1nBrrscu6Ld
        node_id (str): The ID of the node to retrieve, has to be in format x:x, e.g. in url it will be like 0-3, but it should be 0:3

    Returns:
        dict: The node data if found, empty dict if not found
get_workflowB

Get workflows available in a Figma file

    Args:
        file_key (str): The file key found in the shared Figma URL, e.g. if url is https://www.figma.com/proto/do4pJqHwNwH1nBrrscu6Ld/Untitled?page-id=0%3A1&node-id=0-3&viewport=361%2C361%2C0.08&t=9SVttILbgMlPWuL0-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=0%3A3, then the file key is do4pJqHwNwH1nBrrscu6Ld

    Returns:
        list[dict]: List of workflow connections found in the Figma file

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct Figma element: components, nodes, and workflows. There is no overlap in their purposes, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tools follow a consistent 'get_' + singular noun pattern (get_components, get_node, get_workflow), which is predictable and easy to follow.

Tool Count5/5

With 3 tools, the server is tightly scoped for retrieving key Figma file elements. This number is appropriate for a focused MCP server without being too sparse or excessive.

Completeness4/5

The tools cover retrieval of components, nodes, and workflows, which are important aspects of a Figma file. However, it lacks tools for pages or styles, which are common use cases, so minor gaps exist.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources