Figma MCP requires pre-registered client_id (not a bug)

[clouatre]

Summary

Connecting to Figma's MCP server (https://mcp.figma.com/mcp) fails with 403 Forbidden during OAuth registration. This is not a bug in mcp-remote - Figma requires pre-registered OAuth clients.

The Issue

Figma's registration endpoint returns 403 for anonymous registration:

HTTP 403: Invalid OAuth error response: SyntaxError: Unexpected token 'F', "Forbidden" is not valid JSON

This is because:

• Figma requires OAuth clients to pre-register (RFC 7591 allows this)
• Client registration is currently waitlisted: https://www.figma.com/mcp-catalog/
• Randomly generated client IDs are rejected during authorization

Solution

The mcp-remote project could register as an official MCP client with Figma to provide a shared public client_id for users. This would require:

1. Joining Figma's MCP client waitlist
2. Receiving approval and credentials
3. Configuring mcp-remote to use the registered client_id for mcp.figma.com

References

• Figma MCP Catalog: https://www.figma.com/mcp-catalog/
• Figma MCP Docs: https://developers.figma.com/docs/figma-mcp-server/
• OAuth Metadata: https://mcp.figma.com/.well-known/oauth-protected-resource

[rliang]

Any workarounds in the meanwhile?