How to authenticate remote MCP client via Runlayer?

Hi, ​@Onur Orhon 👋 Thanks for reaching out. I located the open support ticket for this case (ID 1963456) It has been assigned to our Technical Quality team and they have triaged it internally. The ticket will be the best place to keep up to date on any details. I also flagged this post internally and on the support ticket to help inform the urgency of your request. Have a great rest of your day! — Jaycee

Thanks ​@Jaycee Lewis, I appreciate the escalation. Is there a link to the ticket so I can keep track of it? 

Jumping in on this, we’re also receiving the same error when trying to utilize Runlayer to host the remote MCP server.  

Hi ​@Onur Orhon  thanks for raising this, and thanks ​@Mark Richards for confirming you're seeing the same behavior.

I was able to see ​@Onur Orhon ‘s support case, and I can see that one of our Technical Quality Specialists has already replied with an update. When you have a chance, please check your inbox. For reference, your case number is 1963456, sent to your email address: daxxxer@bexxxxnt.xxm

From what I can see, the current behavior is expected while Figma is actively evaluating support for enterprise MCP gateways in a way that preserves the appropriate security, governance, and admin controls.

I've also shared this Forum thread internally so the team is aware that other customers are looking for this capability as well. Thanks to both of you for sharing your use cases and feedback!

​@Celine_ could you somehow associate me with that support ticket please? It looks like you’ve combined my request into another one submitted by David from our company. And now I am unable to track it, because I don’t have access to help.figma.com/hc/requests/1963456.

Sure! The support agent has just send the email to you. Please take a look when you have a moment, thank you!

Update: I see in the backend that the support team replied to you. I am sharing the update in case others may have similar request here:

Our team is evaluating support for enterprise MCP gateways like RunLayer in a way that preserves the security, governance, and visibility our customers expect. Thank you for sharing your feedback!

I was directed here by Tom, the Inside Sales lead, to add a +1 from another enterprise customer needing Figma's remote MCP to connect through RunLayer.

I want to be direct about urgency. This gates two active workflows for us: bringing prototypes into Figma for refinement, and agent-based work in Figma. Without a supported remote client, both stall. Part of our team has started moving this work off Figma already, and we worry about continued attrition from tasks in Figma moving forward if the tool can’t support designer workflows. 

We're in healthcare, so governance is not optional for us. RunLayer is how we enforce security and admin controls on every MCP connector. Gateway support is the only path that works for us, which is why we'll be watching this closely.

Is there a way to add our organization to the open ticket (1963456) or otherwise register our need? If possible, we'd also value a rough sense of timeline if one exists so we can plan. Many thanks for your time and consideration. 

Hey ​@Marita Jamieson - thank you for your feedback here as well. I took a few actions on my end, that include:

• Consulted the engineering teams who work on MCP servers
• Filed an official request internally to have a +1 on having RunLayer available (separate from the post you replied under)

After gathering more information on my end, I can confidently say engineering is actively evaluating how Figma can support enterprise MCP gateways in a way that preserves the security, governance, and visibility our customers expect.

Before they can formally support a gateway, they need complete confidence that key controls are preserved, including verified user and client identity, admin policy enforcement, and appropriate visibility into MCP usage. We appreciate you emphasizing that this is important to your team.

Please note: I cannot guarantee on any timelines, but we are working on it. Thank you again for your taking the time to comment.