Skip to main content

Hello, I am trying to run through the MCP OAuth protocol to register a client on the Figma remote MCP server, running into an issue when calling the registration endpoint.

After discovering the registration endpoint via the /.well_known/oauth-authorization-server call, I call the registration endpoint via:

curl -sS -v -X POST "$REG_ENDPOINT" -H "Content-Type: application/json" -d '{
    "redirect_uris": ["http://127.0.0.1:53195/callback"],
    "grant_types": ["authorization_code","refresh_token"],
    "response_types": ["code"],
    "token_endpoint_auth_method": "none"
  }'

 

I get back from this a “Forbidden” response and without this response I can’t continue the OAuth protocol.

Does client registration have limitations to prevent it from working on different domains and url callbacks at the moment? I am doing this in a context outside of Claude, Cursor, etc..

Same problem.


Hey ​@Kevin Gallardo and ​@adamstilla — welcome to Figma Forum, and thanks for surfacing this! 🙌🏻

I checked in with our product team and confirmed that this functionality isn't currently available outside of our approved MCP clients. You can view the full list of supported integrations here: Connect Figma to top MCP clients.

We're always iterating based on feedback and will continue updating that resource as new clients become available. If you have more thoughts on what an ideal configuration might look like, please feel free to share. I'll make sure that insight reaches our product team. 💯


Hi ​@Tom Reem 

I was reviewing the Figma MCP server guide, and it mentions that the MCP Client can be requested by submitting details through the https://form.asana.com/?k=kBG-ejRQTdY8x_H6a4vM3Q&d=10497086658021 form.

Could you kindly confirm if this is the correct process to obtain access to the MCP Client?