Figma Adds 20 MCP Partners Including Sarvam in Expanded AI Push

Figma has added 20 partners to its Model Context Protocol (MCP) ecosystem, with Indian AI firm Sarvam among them, as part of a broader expansion of the AI features built into its design platform.

The move signals where Figma thinks design work is heading: less manual layout assembly, more orchestration of AI agents and external tools that can read, generate, and modify design files directly. MCP is the open protocol, originally introduced by Anthropic, that lets language models connect to external data sources and applications through a standard interface. For Figma, supporting it means outside AI systems can work on design files without screen-scraping or brittle plug-in workarounds.

What does the partner list mean in practice?

Twenty partners is a meaningful batch for a protocol that is still young. Each integration, in principle, gives designers a route to pull external capability — content, code, data — into the Figma canvas, or to push design context out to another tool. Sarvam's inclusion is the notable name for anyone tracking India's AI sector: the company builds language models aimed at Indian languages and markets, and its presence in the lineup extends Figma's MCP reach beyond the usual US-centric AI vendors.

For design teams, the practical stakes are workflow compression. Tasks that today require exporting assets, copying text, or hand-carrying specifications between tools can, in an MCP-connected setup, move through a single model-driven request. That's the theory. Real adoption will depend on how reliably each partner integration handles live design files — the details Moneycontrol's report does not yet enumerate.

How does this fit Figma's wider AI strategy?

The MCP partnerships sit alongside what Moneycontrol describes as a set of new AI features, continuing a push Figma has been building for several product cycles. The company has been layering generative capabilities into its core products — text, layout, and code generation — and positioning itself as the collaborative surface where AI-assisted design actually happens rather than a passive canvas.

Protocol support changes the architecture of that ambition. Features ship inside the product; MCP opens the product to everything outside it. A design system, a content management backend, a localization service: each becomes a potential participant in the design workflow once it speaks the protocol.

What comes next?

Expect the partner count and the feature list to grow together. The open question for design teams is governance — which MCP connections touch which files, and under whose review — and Figma will likely need to answer it as these integrations move from announcements into daily use.