Skip to main content
Anuj Singh
New Member
August 27, 2026
Solved

Figma's MCP product

  • August 27, 2026
  • 3 replies
  • 171 views

I’m trying to connect a custom MCP client directly to the Figma Remote MCP Server:

https://mcp.figma.com/mcp

I understand that Figma’s documentation currently says only clients listed in the MCP Catalog can connect.

Could someone from Figma confirm:

  • Is there currently a supported process for a custom MCP client to connect to the Remote MCP Server?
  • If so, is any registration, approval, or specific Figma plan required?
  • For a custom client requiring OAuth, should a Figma OAuth App Client ID/Client Secret be used, or does the Remote MCP Server use a different OAuth flow?

I’m specifically asking about a custom MCP client connecting to Figma's Remote MCP Server, not creating a custom MCP connector inside Figma Make or Figma Agent.

Thanks!

Best answer by adamsmasher

Hi ​@Anuj Singh! Thanks for your post - happy to help clarify this for you since I can understand why you might want to use a custom client.

  • Is there currently a supported process for a custom MCP client to connect?
    • As you’ve already discovered, only clients listed in the Figma MCP Catalog can connect to the remote MCP server (https://mcp.figma.com/mcp). We're being intentional about the integrations we support in the near term, and at the moment we've paused adding new MCP clients while we continue to build a strong and scalable foundation for all partners. If you'd like your client considered for a future addition, you can submit it here: MCP client request form. Real demand signal genuinely helps with prioritization.
  • Is registration, approval, or a specific plan required?
    • ​​​​​​​There's no self-serve registration that grants instant access today. It's an approval process on our side, and not something you can complete yourself via a form. Having said that, if what you actually need is a private, internal-only client or gateway (used only inside your own org, not a public client), that's a bit different and only available on Organization and Enterprise plans.
  • For a custom client requiring OAuth, should it use regular Figma OAuth App credentials or a different flow?
    • ​​​​​​​A standard Figma OAuth app client ID/secret on its own won't grant mcp:connect access - that scope is currently limited to catalog-approved clients. OAuth is the only supported authentication method for the remote MCP server (no personal access tokens or service accounts), but there isn't a generally available way for a customer to self-provision their own OAuth client for it today.

 

If your use case is actually more of an internal/private tool rather than a public client, then you’ll want to contact your Account Executive for more information. In the meantime, let me know if you have any other questions!

3 replies

adamsmasher
Figmate
Figmate
August 27, 2026

Hi ​@Anuj Singh! Thanks for your post - happy to help clarify this for you since I can understand why you might want to use a custom client.

  • Is there currently a supported process for a custom MCP client to connect?
    • As you’ve already discovered, only clients listed in the Figma MCP Catalog can connect to the remote MCP server (https://mcp.figma.com/mcp). We're being intentional about the integrations we support in the near term, and at the moment we've paused adding new MCP clients while we continue to build a strong and scalable foundation for all partners. If you'd like your client considered for a future addition, you can submit it here: MCP client request form. Real demand signal genuinely helps with prioritization.
  • Is registration, approval, or a specific plan required?
    • ​​​​​​​There's no self-serve registration that grants instant access today. It's an approval process on our side, and not something you can complete yourself via a form. Having said that, if what you actually need is a private, internal-only client or gateway (used only inside your own org, not a public client), that's a bit different and only available on Organization and Enterprise plans.
  • For a custom client requiring OAuth, should it use regular Figma OAuth App credentials or a different flow?
    • ​​​​​​​A standard Figma OAuth app client ID/secret on its own won't grant mcp:connect access - that scope is currently limited to catalog-approved clients. OAuth is the only supported authentication method for the remote MCP server (no personal access tokens or service accounts), but there isn't a generally available way for a customer to self-provision their own OAuth client for it today.

 

If your use case is actually more of an internal/private tool rather than a public client, then you’ll want to contact your Account Executive for more information. In the meantime, let me know if you have any other questions!

Matthew Buck
New Member
September 18, 2026

Is there any public-facing rationale for why this might be the case that I could peruse? I’m not familiar with any other platform that requires jumping through this particular hoop for their MCP server. I can use any MCP-compatible client with most MCP-compatible servers.

I ran into this today when attempting to use Cursor Cloud Agents with the Figma MCP server - apparently, though Cursor is approved, the Cloud Agents aren’t an “approved client.”

Isn’t my data… mine? Why can’t I access it in the way that’s most conducive to getting my work done?

adamsmasher
Figmate
Figmate
September 18, 2026

That’s a fair question ​@Matthew Buck.

 

We do have some public context on our blog post, Design context, everywhere you build, which is that reviewing adds a layer of confidence for people adopting new apps and workflows. It’s similar to the review process for plugins and widgets.

 

Regarding your data, supporting the MCP protocol and being authorized to connect to Figma’s hosted MCP service are treated as separate things. Your existing Figma permissions still determine which files you can access, while the client review applies to the application handling that access.