Figma
Connect Figma to Claude, ChatGPT or Cursor via MCP. OAuth or personal access token, file metadata, comments, image exports, and a governed private gateway.
Example questions
Try asking your AI client
-
What is the name and last-modified time of this Figma file?
-
Which top-level frames are in https://www.figma.com/design/abc123/Homepage?
-
Summarize open comments on the homepage file from the last week.
-
Export the hero frame as a PNG - do not change the file.
-
Write a draft comment on the pricing frame for Amalie to review - do not post it yet.
Overview
Connect Figma to give AI clients access to file metadata, comments, and image exports. This is the hosted Figma MCP integration for Claude, ChatGPT, Cursor, and other MCP clients - no self-hosted server required.
This is not Figma's official Dev Mode MCP. Stackgate proxies Figma's REST API with your OAuth grant or personal access token.
Common use cases
- Figma connector for AI agents - confirm the connected user, then read a file from a Figma URL.
- Design review - list comments, post feedback, or delete your own comments with Write access.
- Image export - render frames as PNG, JPG, SVG, or PDF URLs for handoff.
- Private gateway - combine Figma with Linear, GitHub, and other integrations through one governed endpoint.
Prerequisites
- A Figma account with access to the files you want AI to use
- A file URL or file key (
https://www.figma.com/design/{file_key}/...) - A stackgate.ai account
Public OAuth apps cannot request folders:read, so this integration does not browse teams or folders. Paste a file URL.
Getting credentials
Option A - OAuth (recommended)
- Sign in to stackgate.ai.
- Go to Integrations and open Figma.
- Click Activate, choose tool access (standard or scoped), then Connect Figma.
- Approve the OAuth prompt - stackgate.ai stores your tokens securely and refreshes them when needed.
Option B - Personal access token
- In Figma, open Settings → Security → Personal access tokens and create a token with the file permissions you need.
- In stackgate.ai, open Figma under Integrations.
- Under Add with personal access token, paste the token and save.
Using with AI clients
- Dedicated endpoint:
POST /mcp/figmawith a Sanctum bearer token - Private gateway: one config for all integrations - use
figma__*namespaced tools
See Documentation for HTTP authentication and private gateway setup.
Troubleshooting
- 422 integration not configured - complete OAuth connect or save a personal access token in My Integrations.
- Token expired - disconnect and reconnect Figma (OAuth), or paste a new personal access token.
- Rate limited - Figma Tier 1 file and image endpoints have low quotas on Starter and View seats. Prefer
get_file_metadata, passdepthoridsonget_file, and wait for Retry-After. - Missing write tools - enable Write access / include write tools when using scoped tool access.
- No folder browser - ask the user for a Figma file URL. Team and folder listing is not available on the public OAuth app.
Available tools
-
get_me
Return the connected Figma user (id, handle, email, and avatar).
-
get_file_metadata
Return lightweight Figma file metadata (name, folder, timestamps, role) without the document tree.
-
get_file
Return Figma file JSON. Always pass depth or ids; a full file can be huge and is rate-limited as a Tier 1 endpoint.
-
get_file_nodes
Return specific nodes from a Figma file as JSON.
-
get_images
Render nodes from a Figma file as image URLs (jpg, png, svg, or pdf). URLs expire after about 30 days. Batch node IDs in one call.
-
get_image_fills
Return download URLs for image fills in a Figma file. URLs expire within 14 days.
-
list_comments
List comments on a Figma file.
-
create_comment
Post a comment on a Figma file, or reply to a root comment.
-
delete_comment
Delete a Figma comment. Only the comment author can delete it.
-
list_file_versions
List version history for a Figma file.
MCP endpoint:
https://stackgate.ai/mcp/figma
(HTTP) or via the
private gateway.