We’re trying to connect Figma’s official remote MCP server to AWS Bedrock AgentCore Gateway for an internal enterprise AI workflow.
We can discover the MCP/OAuth metadata correctly, but dynamic client registration to https://api.figma.com/v1/oauth/mcp/register returns 403 Forbidden, and existing Figma PAT/service-token auth is rejected by https://mcp.figma.com/mcp because it requires the mcp:connect OAuth scope.
Our use case is not a public MCP client or IDE plugin. It is a secured internal gateway that already handles Auth0 user authentication and routes to Jira, GitHub, Lucid, and Figma tools. We would like to use the official Figma MCP instead of maintaining a REST-based workaround.
Is there a supported path for enterprise/internal AgentCore gateways to obtain an approved mcp:connect OAuth client, or to register an internal/private MCP client that is not listed publicly in the Figma MCP Catalog?