Cannot connect MCP to Kilo Code

We’re seeing an interoperability issue with the official Figma MCP remote server when used from Kilo Code on Linux.

The OAuth discovery flow succeeds, but dynamic client registration appears to fail:

• Protected resource metadata is returned correctly from https://mcp.figma.com/.well-known/oauth-protected-resource
• Authorization server metadata is returned correctly from https://api.figma.com/.well-known/oauth-authorization-server
• The failure occurs at https://api.figma.com/v1/oauth/mcp/register, which responds with plain 403 Forbidden

This was reproduced both through Kilo Code’s native MCP OAuth flow and through mcp-remote, which suggests the issue is specific to Figma’s remote MCP client registration path rather than the editor itself.

Kilo Code is increasingly used by developers, and broader compatibility with actively used MCP-capable tools would make the Figma MCP much more useful beyond the currently documented clients. Could you clarify:

• whether remote MCP access is currently restricted to a supported-client allowlist
• whether Kilo Code or other generic MCP clients are expected to work
• whether there is a supported path for non-listed clients, especially on Linux where the desktop-app fallback is not available

Support for more MCP clients would materially improve adoption of the official Figma MCP workflow.

Hi ​@IvanC ​@Abdullah Alquraan, Celyn from Figma Community Support here.

Thanks both for flagging this and for sharing such detailed context, especially around the OAuth flow and error logs — that’s really helpful.

I’ve raised this with our internal team so they can take a closer look. ​@Abdullah Alquraan , I’ve also passed your specific questions along to them.

I’ll follow up here as soon as I have more insights to share. Really appreciate your patience in the meantime 🙏

Hi ​@IvanC ​@Abdullah Alquraan — thanks for your patience here.

I’ve checked with the team and can confirm that this behavior is expected. At the moment, MCP access is limited to supported clients and integrations.

I’ve also shared your feedback with the team so it’s on their radar as we continue improving the experience.

We’re being intentional about the integrations we support in the near term, and will continue evaluating additional clients as our approach to MCP evolves.

In the meantime, you can join the waitlist to apply for MCP client support and be notified when additional integrations become available:
Join the MCP waitlist 🙌