Request: Figma MCP OAuth Support - Trusted Client Recognition

Open

We're experiencing an OAuth client registration failure when using mcp-to-ai-sdk with the Figma MCP server at https://mcp.figma.com/mcp.

Issue: Figma's OAuth implementation restricts Dynamic Client Registration (DCR) to pre-approved clients only. When mcp-to-ai-sdk attempts DCR, it receives a client_id error because Figma hasn't whitelisted it as a trusted client.

Current Behavior

client_id is required

This occurs during the OAuth callback phase, preventing tool discovery from completing.

Expected Behavior

mcp-to-ai-sdk should be recognized as a trusted MCP client by Figma, enabling standard OAuth 2.1 + PKCE DCR flow without manual intervention.

Context

The remote MCP server (https://mcp.figma.com/mcp) requires OAuth authentication
Other MCP clients (local servers, mcp-inspector) work when tokens are properly scoped
This affects developers who want to use mcp-to-ai-sdk for vendor-independent tool generation

Questions

Is this a known limitation? Are there plans to request Figma's approval for mcp-to-ai-sdk as a trusted client?
Could this become a blocker pattern? As more MCP servers enforce DCR whitelisting for security, how should tools like mcp-to-ai-sdk handle this?
Is there a workaround? Should we document a temporary approach for users (e.g., using local Figma MCP servers instead)?

Workaround

Users can currently work around this by:

Running Figma's local desktop MCP server (http://127.0.0.1:3845/mcp) if the user has a Dev or Full seat
Using mcp-to-ai-sdk against the local endpoint instead of the remote server

Suggested Actions

Document this limitation in the README for Figma MCP users
Consider requesting approval from Figma for mcp-to-ai-sdk as a standardized tool
Explore if Vercel has existing relationships with Figma that could expedite this?

References

Activity

No activity yet.