> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Figma MCP

> Let Grady read and edit Figma files through Figma's MCP server, with each user connecting their own Figma account.

<Info>
  **Preview.** Figma MCP must be enabled for your organization before it appears in Settings. Contact your Gradial team to get access.
</Info>

Figma MCP connects Grady to Figma's MCP server so it can work directly with your design files: inspect frames and components, capture screenshots, and make edits you ask for. Each person connects their own Figma account, so Grady sees exactly the files that person can see in Figma — nothing more.

***

## What you can do

* **Pull design context into a task.** Paste a Figma link and ask Grady to describe the layout, extract copy, or list the components and styles a frame uses.
* **Get screenshots of specific frames.** Grady can capture an image of a node to compare against a live page or share in a review.
* **Make requested edits.** Grady writes to Figma only when you ask for a change, and only to the file and nodes you point it at.
* **Trace answers back to the source.** Grady names Figma as the source, links to the exact file and node, and notes when the content was fetched.

***

## How it fits together

1. **An admin enables Figma MCP** for the organization under **Settings → Integrations**. Gradial supplies the Figma server, scope, and app credentials, so there is nothing to configure.
2. **The admin assigns it to one or more Environments.** Workspaces in those Environments can then use it, the same as any other integration.
3. **Each user connects their own Figma account** from the same card. Until they do, Grady cannot reach Figma on their behalf.
4. **Users work with Figma through Grady.** There is no separate Figma panel — paste a Figma link into a chat or task and describe what you need.

***

## Prerequisites

* Figma MCP is enabled for your organization by Gradial (see **Access** above)
* An organization role with permission to manage Gradial settings, for the one-time enablement
* A Figma account for each user who will connect, with access to the files they want Grady to work with

***

## Setup

<Steps>
  <Step title="Enable Figma MCP (admin, once per organization)">
    Go to **Settings → Integrations** and select the **Figma MCP** card. In the **Enable Figma MCP** dialog, click **Enable**.

    Users who aren't admins see a prompt to ask an admin instead.
  </Step>

  <Step title="Assign Figma MCP to Environments (admin)">
    Open the new **Figma (MCP)** integration and add the Environments whose Workspaces should use it.
  </Step>

  <Step title="Connect your Figma account (each user)">
    On the **Figma MCP** integration, click **Connect**, sign in to Figma, and approve access. You return to Gradial when the connection completes.
  </Step>

  <Step title="Verify the connection">
    In a Workspace that uses one of the assigned Environments, ask Grady:

    ```text theme={null}
    Which Figma account are you connected to?
    ```

    Grady should reply with your Figma account. Then paste a Figma link and ask for a short description of a frame.
  </Step>
</Steps>

***

## How Grady handles your Figma content

* **Your access, not more.** Grady acts as the connected user and can only reach files that user can open in Figma. It never uses another person's connection.
* **On request only.** Grady retrieves Figma content for the request in front of it. It does not run scheduled or background retrieval, bulk exports, or build searchable copies of your files, and it does not store Figma content in skills or memory.
* **Not used for training.** Figma content is not used to train AI models.
* **Writes stay in scope.** Grady confirms the target file and nodes from your request before making changes and does not edit beyond what you asked.

***

## Limitations

* **Interactive use only.** Figma MCP is available in tasks and chats started by a person. Automated runs — for example, tasks created from a ticketing queue — cannot use it.
* **Figma rate limits apply.** Figma limits MCP usage by plan and seat type. When a limit is reached, Grady tells you which limit was hit and shares Figma's upgrade link instead of retrying.

***

## Troubleshooting

| Issue | Likely cause | Resolution |
| - | - | - |
| No **Figma MCP** card in Settings | Figma MCP is not enabled for your organization | Contact your Gradial team to get access |
| You're asked to contact an admin | Enabling Figma MCP requires permission to manage organization settings | Ask an organization admin to enable it |
| Grady asks you to connect or reconnect Figma | You haven't connected yet, or your Figma authorization expired or was revoked | Go to **Settings → Integrations → Figma MCP** and click **Connect** |
| Grady doesn't use Figma in a Workspace | The integration isn't assigned to that Workspace's Environment | Add the Environment to the **Figma (MCP)** integration |
| Grady can't open a file | Your Figma account doesn't have access to it | Ask the file owner to share it with your Figma account |
| Grady reports a Figma rate limit | Your Figma plan or seat has reached its MCP limit | Wait for the limit to reset, or review the upgrade options Grady shares |

***

## Need help?

Contact your Gradial representative or [Gradial Support](https://portal.usepylon.com/) for help enabling or troubleshooting Figma MCP.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.