Skip to main content
AbhishekChavanFromSatara
New Member
February 6, 2026
Solved

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

  • February 6, 2026
  • 22 replies
  • 3567 views

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, thanks for your patience here.

I've checked in with the team, and at the moment Figma supports a limited set of tools that can connect to our MCP Server. We're taking a thoughtful approach as we continue building a strong and scalable foundation for broader integrations in the future.

If you'd like to connect Figma with other tools, we'd love to hear more about your use case. Please reach out to your account representative or contact Support and include:

  • Which tool(s) you'd like to connect with Figma
  • How you'd expect those tools to work with Figma's MCP Server
  • The specific workflows or outcomes this would enable for you or your team

The more context you can share, the better we can understand your needs and pass that feedback along to the appropriate teams.

Thanks again for taking the time to let us know what would be most valuable for your workflow! 🙌

22 replies

sheetal mohite
New Member
February 18, 2026

Facing the similar issue for similar requirement. 

trikohung-first-cognition
New Member
February 22, 2026

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

Zack Rossman
New Member
March 10, 2026

I’m seeing the same issue

Dominik_Wawrzonek
New Member
March 24, 2026

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

AbhishekChavanFromSatara
New Member
March 24, 2026

Facing the similar issue for similar requirement. 

 

Chase Reasoner
New Member
March 29, 2026

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
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
Figmate
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
New Member
May 17, 2026

@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
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.