Skip to main content
Back to the Figma MCP server

MCP Gateway · Claude Code

Figma icon

Connect Figma to Claude Code

Hand Claude Code a Figma link and it can build the component from the design itself instead of from your description of a screenshot. Figma returns reference code, a screenshot and metadata that Claude Code adapts to your repo. Agent hooks let Speakeasy allow or deny each tool call before Claude Code runs it, and the OpenTelemetry exporter attributes the session to a named developer.

Category
Design
Tools
17
Authentication
OAuth
Claude Code
CLI

Behind the MCP Gateway

Run Figma MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Figma call inspected and logged.

Deploy on MCP Gateway

Set up

Add Figma to Claude Code in 4 steps

  1. 01

    Add Figma from the catalog

    An admin finds Figma in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Figma uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Figma

    Give teams the mcp:connect scope on the Figma server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Figma to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Figma from Claude Code

    The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Figma needs its own OAuth grant, so each person connects it once. Until they do, Figma calls fail while the rest of the gateway keeps working.

    From then on, Figma's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Figma

Implement a frame from a link

Paste a Figma URL and Claude Code pulls reference code, a screenshot and metadata for that node, then rewrites it with your project's own components and styles.

get_design_context

Generate design system rules for the repo

Have Claude Code produce a rules file describing how designs map to your codebase, so later design-to-code tasks follow the same conventions every time.

create_design_system_rules

Send a local page back to Figma

After building a page on your dev server, ask Claude Code to capture it as a Figma design so designers can review what actually shipped.

generate_figma_design

Tools

17 tools

Each Figma tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.

get_screenshot

Generate a screenshot for a given node or the currently selected node in the Figma desktop app. Use the nodeId parameter to specify a node id. nodeId parameter is REQUIRED. Use the fileKey parameter to specify the file key. fileKey parameter is REQUIRED.

create_design_system_rules

Provides a prompt to generate design system rules for this repo.

get_design_context

Get design context for a Figma node — the primary tool for design-to-code workflows. Returns reference code, a screenshot, and contextual metadata that should be adapted to the target project. See the server instructions for how to interpret and adapt the response.

get_metadata

IMPORTANT: Always prefer to use get_design_context tool. Get metadata for a node or page in the Figma desktop app in XML format. Useful only for getting an overview of the structure, it only includes node IDs, layer types, names, positions and sizes.

get_variable_defs

Get variable definitions for a given node id. g. {'icon/default/secondary': #949494}Variables are reusable values that can be applied to all kinds of design properties, such as fonts, colors, sizes and spacings. Use the nodeId parameter to specify a node id.

get_figjam

Generate UI code for a given FigJam node in Figma. Use the nodeId parameter to specify a node id. If no node id is provided, use 0:1 which is the root node ID. Use the fileKey parameter to specify the file key.

See all 17 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.

Tool logs

Gateway

Every Figma call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Figma tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Figma can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code be stopped from editing Figma files?
Yes. The gateway decides which of the 17 Figma tools each team can call, so a team can read design context without use_figma, which creates, edits and deletes Figma objects. Agent hooks also check each tool call before Claude Code runs it.
Does Claude Code on the web get the same Figma setup?
Not automatically. Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
How do Claude Code users get Figma?
An admin adds Figma from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Figma tools their access allows.
Are Figma calls from Claude Code logged?
Yes. Figma calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Figma in other clients

AI everywhere.

Control here.