MCP Gateway · Claude
Connect Figma to Claude
Product managers and designers can use Claude to turn a conversation into something visual. With Figma connected, Claude can draw a flowchart or gantt chart in FigJam and look at a frame to review its copy. Each person connects through the gateway's sign-in, sees only the servers their role can reach, and nobody shares a Figma credential.
- Category
- Design
- Tools
- 17
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
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.
Set up
Add Figma to Claude in 4 steps
- 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.
- 02
Choose who can use Figma
Give teams the
mcp:connectscope 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. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Figma from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Figma
Turn a process into a flowchart
Describe an approval process or a customer journey and Claude draws it as a flowchart or decision tree in FigJam, ready for the team to edit.
Review the copy on a design
Share a Figma frame and Claude takes a screenshot of it, then checks headlines, button labels and error messages against your style guide.
Plan a launch timeline
Ask Claude to lay out launch milestones as a gantt chart in FigJam, so marketing, sales and support work from the same dates.
Tools
17 tools
Each Figma tool can be allowed or denied per team and role at the MCP Gateway before Claude 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.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can Claude edit our Figma design files?
Is a client ID needed to connect Figma to Claude?
How do Claude users get Figma?
Are Figma calls from Claude logged?
Connect more