Remote Figma MCP doesn't work with Firebender

We’d like to be able to use this!

At Zillow we have hundreds of Android developers using Firebender. We would really like to have Firebender and Figma working together!

Firebender is rapidly becoming the de facto standard for an AI based coding agent on Android. If Figma is serious about supporting mobile development and staying relevant in an age where more and more UI is being built with agentic workflows, Figma needs to ensure this works. 

Hey All, thank you for your feedback! 

Right now, the Figma MCP server only works with a specific catalog of agentic tools, so there is currently no easy way to make Firebender work at this time. 

I’ve ensured that this topic is a feature request, and I’ll pass all of your feedback over to the MCP team to consider adding Firebender to our catalog in the near future. 

hey ​@djv thanks for responding so quickly!!

Is it possible to not have it added to the catalog but still be able to work with the Figma MCP server? We just want the thousands of engineers that love both Figma and Firebender to be unblocked as quickly as possible.

The Firebender team can handle writing clear figma integration docs on their end, and Figma won’t need to update the catalog and take on any risk. The only work from Figma side should be adding the mcp:connect OAuth scope to Firebender’s figma OAuth client

TLDR: engineers that love figma dev mode and firebender get a massive win, with little to no effort from Figma’s team. Firebender will maintain the integration, with well written documentation on getting the most out of code connect and android development

Support firebender client please. This is the only AI agent that makes sense for android development. It is awesome and with proper Figma integration it will be only better 😍

Support Firebender! Everyone is starting to use this tool for Android Development!

I’d like to ask for the support of Firebender

Going through the list of the specific catalog, it sure seems like Figma is only playing with the 1000lb gorillas of tech - MS, Google, Amazon, OpenAI, Anthropic, Atlassian, etc.

C’mon Figma, be better than that. Let smaller firms compete.

Agree with everyone above - we’d really benefit from Figma supporting Firebender. Since Firebender is working directly in Android Studio, supporting Figma would help us directly render Figma designs in our apps. Would love for this to get on the Figma roadmap!

Hey all, thanks for responding on this forum post!

Just spoke to the partnership team, and unfortunately, it’s unlikely Figma will add support for Firebender client. You can create a support ticket or email them.

We’ll keep launching awesome features in the mean time, and happy to revisit this with them if they re-evaluate

This is an incredibly bad look for the Figma team and exactly what a product trying to stay relevant in the AI space should avoid doing. Idk if Figma is intending to do this, but I don't really appreciate my previously accessible user data being walled off, repackaged, and sold to me via outlets that don't really meet my needs. 

I will definitely be following up with a couple support tickets on this, but generally it feels like there is no reason the remote MCP should be closed to nearly any tool used by paying customers. The supported agents aren't going to meet the needs Firebender is filling in my org without significant engineering investment from my team, and the total lack of Linux support for the local Figma MCP essentially leaves our Linux users out of luck. 

I appreciate the work the Figma team has been doing and generally love the product, but this is driving people to use 3rd party wrappers around the Figma API, which isn't good for anybody. It all makes me hesitant to pick up Figma to build products in the future for fear of other decisions the Figma team makes that may limit the tools I can use to build software. 

Bummer, I would have thought after the IPO they would have the resources to do it.  

{"mcpServers": {
     "figma": {
       "url": "https://mcp.figma.com/mcp",
       "type": "http"
     }
}}

{"mcpServers": {
     "figma": {
       "url": "https://mcp.figma.com/mcp",
       "type": "http"
     }
}}

Yeah, this seems to be a known issue. The Figma remote MCP is still pretty limited with OAuth scopes, so Firebender can’t fully authenticate unless Figma whitelists the client. I’ve run into the same thing on my end.

What helped me was reaching out to Figma support with the exact scopes Firebender requests — they need to manually enable them. Until they do, the config won’t work no matter how you set it up.

At work we integrate tools through Phonexa’s internal MCP-style setup, and even there the OAuth part is usually the blocker — so it’s probably the same story here.

If you get a response from Figma, let us know what they say.

Please support Firebender!

Kindly support Firebender! 🙏