Skip to main content
Solved

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

  • February 6, 2026
  • 8 replies
  • 1253 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 🙌

8 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 🙌

      Terms & ConditionsCookie settingsAccessibility statement