Skip to main content
Question

Understanding OAuth Requirements for MCP Clients Connecting to Figma MCP Server

  • March 23, 2026
  • 0 replies
  • 11 views

SanthoshNayak

Hi team,

I am currently evaluating your platform for a potential integration ( MCP Client with Figma MCP Remote server ). To proceed correctly, I need clarification on a few specific technical points. Could you please help me with the following?

1. OAuth App Support – FOR MCP CLIENT
Does your platform support creating an OAuth application (MCP Client APP) for third-party integrations?

2. Global OAuth Availability (Important Explanation Below) – FOR MCP CLIENT
I would like to confirm whether your OAuth implementation supports Global OAuth.

By “Global OAuth”, I mean:
• The OAuth app (MCP Client ) that I create is not tied to a single customer/account.
• Any user from any tenant/region who has an account on your platform can independently authorize my application.
• I (as the developer) do not need to manually approve/access each user.
• Users can simply click “Connect”, complete the OAuth flow, and your platform will return tokens to access their own data directly.

In short, I want to confirm whether your OAuth is multi-tenant, globally accessible, and user-self-service.

3. Marketplace / App Store Submission – For MCP CLIENT
Does your platform offer an app marketplace or partner directory where third-party integrations can be submitted and listed publicly?
4.MCP Client Registration Requirements
Are there any additional steps required to register an MCP client beyond obtaining the OAuth Client ID and Client Secret?

Thank you for your guidance. Looking forward to your response.