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 IssueWhen requesting the mcp:connect scope during OAuth authorization, I receive:{"error": true,"status": 400,"message": "Invalid scopes for app"}OAuth App Details:Redirect URI: http://localhost:3000/callback Current working scopes: files:read, file_comments:write Blocked scope: mcp:connectQuestionsIs the mcp:connect scope available for third-party OAuth apps? If restricted, is there a beta program or application process? 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"

New Member

Solved

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

Forum|Forum|7 months ago
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:

Redirect URI: http://localhost:3000/callback
Current working scopes: files:read, file_comments:write
Blocked scope: mcp:connect

Questions

Is the mcp:connect scope available for third-party OAuth apps?
If restricted, is there a beta program or application process?
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"

Figma MCP

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

Show previous replies

Václav Antošík

New Member

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

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

New Member

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

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 🙏

Celyn_LAnswer

Figmate

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

Joel K

New Member

This issue is also preventing me from enabling Figma’s MCP through our internal gateway. A major issue to say the least.

Zina Youhan

New Member

Hi @Celyn_L

It would be better if its available for atlassian rovo dev sandbox.

Tucker Weibell

New Member

@Celyn_L This is a huge blocker for anyone who is using an MCP gateway for security and governance.

Most companies solve this by allowing users to create OAuth apps where they can specify their own redirect URLs (pointed at their gateway).

Other companies allow users to simply define a list of allow redirect URLs that can be used for MCP OAuth at the platform level.

defigor

New Member

This is a significant issue for us too. We route all approved MCP servers through a central MCP gateway, and because Figma doesn't support standard OAuth, we can't add it. Could your team look into supporting this?

Celyn_L

Figmate

Hi everyone, thanks for chiming in here.

We really appreciate you taking the time to share how this impacts your workflows. To help us capture your feedback in more detail, the best next step will be to 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 details you can provide, the better we can understand your use case and ensure your feedback reaches the right teams. I've also shared the feedback from everyone in this thread with the team. Thanks again for taking the time to share your thoughts! 🙏

Show more replies

Hi Figma Community!

The Issue

Questions

What I've Tried

Sign up

Login with SSO

Login to the community

Login with SSO