Skip to directory

Figma MCP

Figma

Streamable HTTP (remote); stdio (desktop)33+ documented tools26

About Figma MCP

Figma's MCP server gives supported AI clients design context from Figma files and can create or edit native Figma content, generate diagrams, and transfer live UI into Figma.

What you can use it for

  • Generate code from selected Figma designs and retrieve layout, component, and variable context
  • Create and modify Figma Design and FigJam content from prompts
  • Generate diagrams, images, shaders, and plugin scaffolds
  • Map Figma components to code using Code Connect
Connection and setup
Hosting
Remote (recommended); local desktop server also available
Transport
Streamable HTTP (remote); stdio (desktop)
Endpoint
https://mcp.figma.com/mcp
Authentication
Figma OAuth interactive consent for remote server. Desktop server requires the Figma desktop app.

Requirements

  • Figma account and access to relevant files
  • MCP client listed in Figma's supported-client catalog for remote service
  • OAuth browser consent
  • Desktop app only when using the desktop server

Setup steps

  1. Use the remote endpoint https://mcp.figma.com/mcp in a supported client, or install Figma's official client plugin where available.
  2. Complete the Figma OAuth Allow Access flow.
  3. For design context, provide a Figma frame or layer URL; the client extracts the node ID.
  4. For desktop mode, open the target file in Figma desktop, enable the local MCP server and select the relevant content.
Tools 33+

The stored names combine tools from remote Figma MCP, desktop MCP, and optional paid Weave. The actual surface depends on endpoint, seat, plan, and feature access; remote-only tools are marked in Figma’s reference.

  • download_assets
    01
  • get_code_connect_map
    02
  • get_code_connect_suggestions
    03
  • get_context_for_code_connect
    04
  • get_design_context
    05
  • get_figjam
    06
  • get_libraries
    07
  • get_metadata
    08
  • get_motion_context
    09
  • get_screenshot
    10
  • get_shader
    11
  • list_generative_plugins
    12
  • list_shaders
    13
  • search_design_system
    14
  • whoami
    15
  • add_code_connect_map
    16
  • create_generative_plugin
    17
  • create_new_file
    18
  • create_shader
    19
  • generate_diagram
    20
  • generate_figma_design
    21
  • generate_image
    22
  • send_code_connect_mappings
    23
  • update_generative_plugin
    24
  • update_shader
    25
  • upload_assets
    26
  • use_figma
    27
  • weave_list_tools
    28
  • weave_get_tool_inputs
    29
  • weave_upload_asset
    30
  • weave_run_tool
    31
  • weave_get_tool_run_output
    32
  • weave_cancel_tool_run
    33

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Only clients listed in Figma's MCP Catalog can connect to the remote server (per current setup docs).
  • Remote-only tools are unavailable from desktop mode; some code-to-canvas and Xcode workflows are client-version restricted.
  • generate_image consumes Figma AI credits; Weave tools require a paid standalone Weave account and may consume Weave credits.
  • Weave tool discovery reflects the authenticated user's workspace and sharing permissions.
Original sources
  • official tool reference

    The remote and desktop servers expose different surfaces; many tools are remote-only and plan/seat/feature gated. Weave tools depend on a separate paid Weave account. Stored inventory is not universal across variants.

  • official documentation

    The remote and desktop servers expose different surfaces; many tools are remote-only and plan/seat/feature gated. Weave tools depend on a separate paid Weave account. Stored inventory is not universal across variants.

Documentation checked 2026-10-28T12:48:00.000Z. Connection has not been runtime tested.