Skip to main content
Hosted by a third party. This MCP server is built and hosted by the vendor, not Runlayer. This guide covers connecting it through Runlayer for governance, policies, and audit.
Connect your AI assistant to Figma to read design context, screenshots, and metadata from Figma files, and (where your plan enables it) write designs back. This is a remote MCP server hosted by Figma — Runlayer proxies requests to https://mcp.figma.com/mcp using Streamable HTTP transport, authenticating each user with their own Figma account.

​
Why Figma needs a registered OAuth app

Figma limits which OAuth clients can connect to its remote MCP server: only pre-registered client IDs are accepted, and Figma’s Dynamic Client Registration endpoint is closed. Register a Figma OAuth app in your own workspace, then reach out to your Figma account manager to get its client ID approved for MCP access.

​
Setup

1

Create a Figma OAuth app

  1. Follow Figma’s OAuth apps guide to create a new app in your Figma workspace
  2. Set the redirect URI to your Runlayer callback:
    This is your Runlayer APP_URL followed by /oauth/callback — the same origin your users open Runlayer at. The value must match exactly (scheme, host, path, no trailing slash).
  3. Copy the Client ID and Client Secret
2

Get the app approved by Figma

  1. Contact your Figma account manager and ask them to pre-register your OAuth client for MCP access. Share the Client ID (never the secret) and request the mcp:connect scope
  2. Figma configures the client on their side and will tell you when it is approved; they may ask you to republish the app afterwards
  3. Until this step is done, Figma’s consent screen rejects the client even though the app exists
3

Add the Figma connector in Runlayer

  1. In Runlayer, go to My connectors, find Figma, and click Add connector
  2. Under Registration, keep Pre-registered Client selected
  3. Paste the Client ID and Client Secret from your Figma app
  4. Leave OAuth Scopes as mcp:connect
  5. Save the connector
4

Connect as a user

  1. Each user opens the Figma connector in Runlayer and clicks Connect
  2. They complete Figma’s consent screen with their own Figma account
  3. Tools are then available in any MCP client connected through Runlayer

​
Troubleshooting

The connector has no client ID or secret configured. Open the connector settings, choose Pre-registered Client under Registration, and paste the credentials from your Figma OAuth app.
Expected. Figma’s Dynamic Client Registration endpoint rejects every client, regardless of name. Use a pre-registered Figma OAuth app as described above instead of DCR.
The redirect URI on your Figma OAuth app must exactly match https://<your-runlayer-domain>/oauth/callback. Check for a trailing slash, a different subdomain, or http instead of https.