Figma

• Per-user OAuth2 — central client (oauthCentral, recommended) — one Figma OAuth application is registered once by the platform maintainer; every end user signs in with their own Figma account. Nothing to register per workspace: each one just installs the app and clicks Connect.
• Per-user OAuth2 — tenant client (oauth) — paste your own Figma OAuth client ID/secret in the connector config app. Each user signs in with their own account against your client (authorization-code + PKCE flow).
• Direct access token (accessToken) — a caller-managed Figma token (e.g. a Personal Access Token), used as-is with no exchange.

​

Who is this for?

​

Prerequisites

• A Figma account.
• For the OAuth modes — a Figma OAuth application created at Figma > Developers > My apps (https://www.figma.com/developers/apps); copy its Client ID and Client Secret. The platform maintainer registers one app for the central mode; a workspace can also register its own for the tenant mode.
• For the access-token mode — a Personal Access Token created at Figma > Settings > Security > Personal access tokens (https://www.figma.com/developers/api#access-tokens) with the scopes the operations you call require.
• The default OAuth scopes requested are:
  current_user:read file_content:read file_metadata:read file_versions:read file_comments:read projects:read
  
  Add file_variables:read / file_variables:write (variables), library_analytics:read (library analytics) or org:activity_log_read (activity logs, Enterprise) when your agents need those endpoints.
• Base URL: https://api.figma.com — paths already include /v1 or /v2.

<api-url>/workspaces/slug:figma/webhooks/oauthCallback

context_id,agent_id,user_id

context_id,agent_id,user_id

You have access to the Figma MCP server. Use it whenever the user asks about Figma content — files, nodes, rendered images, comments, projects, components, styles, webhooks, variables or library analytics. Examples: "Summarize the comments on this Figma file", "Render the hero frame as a PNG", "List the published components in our design system". Each tool is an entity that takes an `action` argument. Prefer calling tools over guessing, and confirm with the user before any destructive action (delete a comment, delete a webhook, modify variables).

{
  "name": "files",
  "arguments": {
    "action": "get",
    "file_key": "omLm4Pdg2a3BzTKU8EcDo7",
    "depth": 1
  }
}

{
  "name": "comments",
  "arguments": {
    "action": "create",
    "file_key": "omLm4Pdg2a3BzTKU8EcDo7",
    "message": "Please review the updated hero section."
  }
}

{
  "name": "images",
  "arguments": {
    "action": "render",
    "file_key": "omLm4Pdg2a3BzTKU8EcDo7",
    "ids": "1:23,1:45",
    "format": "png",
    "scale": 2
  }
}

{
  "name": "webhooks",
  "arguments": {
    "action": "create",
    "event_type": "FILE_UPDATE",
    "context": "file",
    "context_id": "omLm4Pdg2a3BzTKU8EcDo7",
    "endpoint": "https://example.com/figma-hook",
    "passcode": "a-shared-secret"
  }
}

{
  "name": "components",
  "arguments": {
    "action": "listByTeam",
    "team_id": "1303310645528056530"
  }
}

- Figma.getFileMeta:
    file_key: '{{fileKey}}'
    output: meta

- Figma.postComment:
    file_key: '{{fileKey}}'
    message: Please review the updated hero section.
    output: comment

- Figma.getFile:
    file_key: '{{fileKey}}'
    depth: 1
    output: file
- Figma.getImages:
    file_key: '{{fileKey}}'
    ids: '1:23,1:45'
    format: png
    scale: 2
    output: renders

- Figma.postWebhook:
    event_type: FILE_UPDATE
    context: file
    context_id: '{{fileKey}}'
    endpoint: 'https://example.com/figma-hook'
    passcode: '{{webhookSecret}}'
    output: webhook

​

Error Handling

​

Common Issues

​

External Resources