Skip to main content
Kevin Gallardo
New Member
October 1, 2025
Question

Remote MCP server OAuth client registration issue

  • October 1, 2025
  • 19 replies
  • 6680 views

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

19 replies

bcheidemann
New Member
July 7, 2026

> I’m not sure what the reason would be for whitelisting clients in this particular method. The industry wide norm is to let any MCP client connect to your MCP server, it’s also the reason why this is an open protocol.

+1

I'm trying to use your remote server with Zed, which currently only has support for the local server. This feels totally arbitrary and is honestly pretty frustrating.

bcheidemann
New Member
July 8, 2026

Hey, I’m currently unable to use the Figma MCP with Zed on Linux, because it only supports the local MCP via the Desktop app. However, the Desktop app is unavailable for Linux…

Marek KALNIK
New Member
July 9, 2026

Opencode is also blocked.

Jesse_Clark1
New Member
July 15, 2026

Also here for Opencode :/

ksn
Figmate
Community Support
July 15, 2026

Hey all - we hear you, and know you’d like to see an expansion of our availability for other MCP servers. 

At this time, we don’t have an update on when/if there will be acceptance/support of any additional ones at this time, but we do encourage you (and anyone else that may come across this) to continue requesting via the links Tom confirm above.

Thank you for your patience.

Benoit R
New Member
July 16, 2026

Adding on the pile: Copilot Desktop. Copilot CLI works, no fuss, but product and design adoption of CLI tools is not the easiest at all. Copilot Desktop offers to use SSE, but the SEE MCP does not have the “use_figma” tool...

Mariano Gutierrez Xavier
New Member
August 18, 2026

Same here, getting blocked with GitHub Copilot App

Pranit Harekar
New Member
August 19, 2026

GitHub Copilot Desktop App throws the following error when signing in - 
 

Authentication failed
figma: RPC error -32603: Request session.mcp.oauth.login failed with message: Client registration failed: server responded with status 403 Forbidden: Forbidden


Adding HTTP or SSE manual server doesn’t work either. All we need is for GitHub Copilot Desktop App to be able to grab screenshots directly from Figma files.

Any ETA on this?

Tom Reem
Figmate
Figmate
September 9, 2026

Hey ​@Pranit Harekar ​@Mariano Gutierrez Xavier ​@Benoit R — Copilot Desktop has been the common thread for the three of you, and I checked in with the product team on it. Here's a solution that's unblocked others who ran into a similar scenario.

  1. Install the GitHub Copilot CLI and authenticate with Figma through it.
  2. Open the Copilot Desktop App.
  3. Install the Figma plugin.

Run them in that order. We’ll continue to share more information as details become available. 🙏🏻