- Figma McP is no longer Desktop-Kun, it comes to Ides, Ai Agents and more
- MCP bridges also code bases and projects within Figma -Make
- REST API -RENT boundaries change but only 1% of users will be affected
Figma rolls out behind the scenes upgrades to make its AI agents even more powerful by expanding their access to context in several places.
After the launch of the local MCP server earlier in 2025, Figma adds remote access to Figma MCP, allowing users to connect to the platform from IDEs, AI-Coding Agents and Browser-based models.
The company has also launched a partner catalog to simplify connecting the MCP server to IDEs or agents.
Figma McP just got a big upgrade
Figma also uses its model Context Protocol (MCP) -A Open Source standard to connect AI tools with software applications, tools and platforms inside Figma make to give a bridge between users’ projects and their code bases.
It allows AI models to access the underlying code from make -files, not only the rendered prototypes or images, and will be supported in anthropic, marker, windsurf and VS code from the launch, with indications that additional partners could participate at a later date.
Figma Make was launched on Config 2025 in May as a quick-to-code tool to convert natural language input into fully coded protoypes.
Looking ahead, Figma says it will review all public third-party integrations and MCP clients before they can access user data to ensure maximum security. Rest API Rate Limits will also be adjusted from November 17, but Figma says the change will only affect less than 1% of Figma’s active users.
“We want context to move freely between tools so that explorations can develop into production functions without unnecessary rewrites or change,” added Figma CTO Kris Rasmussen.
Figma has also added mapping in the app in the code of code, and the MCP server promises to share more than just design context, such as code component locations and use guidelines.
The changes are available now, but Figma noted that they remain in beta.
