MCP Gateway · Cursor
Connect Figma to Cursor
Designers hand off in Figma and developers build in Cursor. With Figma behind the Speakeasy gateway, Cursor can read the exact tokens for a frame while you edit, and link Figma components to the files that implement them. Cursor hooks check each prompt and tool call with Speakeasy and fail closed, and each hook event carries the user's email.
- Category
- Design
- Tools
- 17
- Authentication
- OAuth
- Cursor
- Editor and terminal
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 Cursor 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 Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Figma from Cursor
The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Figma
Use the real design tokens
Ask Cursor for the variables on a selected node, such as colors, spacing and fonts, and it replaces hard-coded values in your stylesheet with the matching tokens.
Map Figma components to code
Cursor gets suggested links between a Figma component and your code components. You review them in the chat, and it saves the approved mappings in bulk.
Reuse an existing library component
Before building a new button or card, have Cursor search the design libraries for a matching component, variable or style, so you reuse what already exists.
Tools
17 tools
Each Figma tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor
The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Do Cursor users each need a Figma token?
What happens in Cursor after the Figma plugin is updated?
How do Cursor users get Figma?
Are Figma calls from Cursor logged?
Connect more