Skip to main content
Solved

How to Access MCP OAuth Scope (mcp:connect)?

  • February 6, 2026
  • 14 replies
  • 2228 views
AbhishekChavanFromSatara

Hi Figma Community!

I'm working on a design-to-code automation tool and would like to integrate with Figma's Model Context Protocol (MCP) endpoint.

The Issue

When requesting the mcp:connect scope during OAuth authorization, I receive:

{

"error": true,

"status": 400,

"message": "Invalid scopes for app"

}

OAuth App Details:

Questions

  1. Is the mcp:connect scope available for third-party OAuth apps?
  2. If restricted, is there a beta program or application process?
  3. Is this scope only available to official Figma extensions (VS Code, Cursor)?

What I've Tried

  •  Standard OAuth flow works fine with public scopes
  •  Got valid Bearer token
  •  MCP endpoint (https://mcp.figma.com/mcp) returns 401 with www-authenticate: Bearer scope="mcp:connect"

Best answer by Celyn_L

Hi everyone — thank you so much for your patience here, really appreciate it.

I've checked with the team, and confirmed that this is expected behavior.

At the moment, the mcp:connect scope isn't available for general third-party OAuth apps — MCP access is currently limited to supported clients and integrations.

We're being intentional about the integrations we support in the near term, and will continue evaluating additional clients as our approach to MCP evolves.

In the meantime, you can join the waitlist here: https://www.figma.com/mcp-catalog/

Thanks again for taking the time to raise this here 🙌

14 replies

sheetal mohite

Facing the similar issue for similar requirement. 

trikohung-first-cognition

I’m facing the same issue trying to connect to Figma MCP via Github Copilot on Webstorms on Arch Linux

Zack Rossman
  • Zack Rossman
  • New Member
  • March 10, 2026

I’m seeing the same issue

Dominik_Wawrzonek

Same for me. Is even possible to reach mcp with OAuth and Bearer token ?

    AbhishekChavanFromSatara

    Facing the similar issue for similar requirement. 

     

    Chase Reasoner

    Same issue here. looks like they have locked down mcp connection to specific AI clients that support the DCR process. so you can’t proxy or use a gateway. 

    Celyn_L
    Figmate
    • Celyn_L
    • Figmate
    • March 31, 2026

    Hi ​@AbhishekChavanFromSatara and others following along — Celyn from Figma Community Support here.

    Thanks everyone for flagging this and for sharing the detailed context around the MCP OAuth flow and mcp:connect scope, that’s really helpful.

    I’ve raised this with our internal team so they can take a closer look at what might be happening here, including the questions around scope availability and supported clients.

    I’ll follow up here as soon as I have more insights to share.

    Appreciate your patience in the meantime 🙏

    Celyn_L
    Figmate
    • Celyn_L
    • Figmate
    • Answer
    • April 2, 2026

    Hi everyone — thank you so much for your patience here, really appreciate it.

    I've checked with the team, and confirmed that this is expected behavior.

    At the moment, the mcp:connect scope isn't available for general third-party OAuth apps — MCP access is currently limited to supported clients and integrations.

    We're being intentional about the integrations we support in the near term, and will continue evaluating additional clients as our approach to MCP evolves.

    In the meantime, you can join the waitlist here: https://www.figma.com/mcp-catalog/

    Thanks again for taking the time to raise this here 🙌

      Nitish Kumar Pilla

      ​@Celyn_L  We’re trying to connect Figma’s official remote MCP server to AWS Bedrock AgentCore Gateway for an internal enterprise AI workflow.

      We can discover the MCP/OAuth metadata correctly, but dynamic client registration to https://api.figma.com/v1/oauth/mcp/register returns 403 Forbidden, and existing Figma PAT/service-token auth is rejected by https://mcp.figma.com/mcp because it requires the mcp:connect OAuth scope.

      Our use case is not a public MCP client or IDE plugin. It is a secured internal gateway that already handles Auth0 user authentication and routes to Jira, GitHub, Lucid, and Figma tools. We would like to use the official Figma MCP instead of maintaining a REST-based workaround.

      Is there a supported path for enterprise/internal AgentCore gateways to obtain an approved mcp:connect OAuth client, or to register an internal/private MCP client that is not listed publicly in the Figma MCP Catalog?

      Celyn_L
      Figmate
      • Celyn_L
      • Figmate
      • May 18, 2026

      Hi ​@Nitish Kumar Pilla - thanks for sharing all of this context, appreciate the detailed write-up.

      I understand you’re trying to connect Figma’s official remote MCP server to an internal AWS Bedrock AgentCore Gateway workflow, and are currently blocked by the OAuth/client registration requirements around the mcp:connect scope for a private/internal client setup.

      I’m checking with the team internally on this, and I’ll get back to you as soon as I have more information to share.

      Appreciate your patience in the meanwhile.

      Václav Antošík

      Hi ​@Nitish Kumar Pilla - thanks for sharing all of this context, appreciate the detailed write-up.

      I understand you’re trying to connect Figma’s official remote MCP server to an internal AWS Bedrock AgentCore Gateway workflow, and are currently blocked by the OAuth/client registration requirements around the mcp:connect scope for a private/internal client setup.

      I’m checking with the team internally on this, and I’ll get back to you as soon as I have more information to share.

      Appreciate your patience in the meanwhile.

      Hello, 
      I have very similar usecase as Nitish. We have ContextForge MCP gateway and I’m trying to include our corporate Figma MCP into it. I understand that it is not currently suported. So plus one point from my side to get this feature :-). Thank you.

      Celyn_L
      Figmate
      • Celyn_L
      • Figmate
      • May 22, 2026

      Hi ​@Václav Antošík, thanks for chiming in and sharing your use case as well.

      I’ve passed this along to the team too so they have visibility into the additional interest around supporting internal/corporate MCP gateway integrations.

      I’ll share any updates here if I hear more from the team. Appreciate you taking the time to add your feedback!

      Jerric Lyns John

      Hey ​@Celyn_L we have a similar use case and the ability to just add `mcp:connect` scope to the OAuth app would make a lot of difference. The inability to add this scope to the OAuth app is preventing us to enable Figma MCP proxy to all our customers. Please do something about this, atleast allow us to request to whitelist our domain. 

      Celyn_L
      Figmate
      • Celyn_L
      • Figmate
      • June 2, 2026

      Hey ​@Jerric Lyns John, thank you for sharing this context. I can see how the inability to add the mcp:connect scope to an OAuth app would create a significant blocker when trying to roll out a Figma MCP proxy workflow to your customers at scale.

      This is really useful feedback, and I’ve shared it with the team along with the details of your use case.

      I’m still waiting to hear back from them and I’ll share any updates here as soon as I have more information.

      Thanks again for taking the time to explain the impact this is having on your workflow 🙏

      Terms & ConditionsAccessibility statement