Figma launches MCP connectors for Figma agent

• Figma added MCP connectors to the Figma agent, letting it reach apps including GitHub, Slack, Notion, Atlassian, Granola, Hex, and Dovetail, according to figma's connector post.
• The connector menu lands inside the agent UI, where shows external apps sitting next to web search, libraries, and skills.
• Early testers were already pushing beyond design tasks, with rogie's reply saying code worked via MCP and video worked via Motion during the beta.
• The connector drop sits inside a bigger Config 2026 push where, as zoink's keynote recap put it, code, Weave, shaders, plugins, and Motion now live together in one canvas.

You can jump from the new connectors menu to Weave tools, then over to generative plugins beta. Figma also paired the rollout with a wider design agent beta expansion, which makes the connector launch look less like a one-off integration and more like a bigger attempt to turn the canvas into an agent workspace.

The first connector set is practical, not theoretical: Atlassian, Dovetail, GitHub, Granola, Hex, Notion, and Slack all appear in figma's screenshot post. That puts project docs, tickets, notes, repos, and team chat inside the same menu the agent already uses for search and libraries.

The interesting part is the shape of the UI. In

, connectors are a first-class picker inside the agent, not a buried admin setting.

The first useful workflow hint came from rogie's reply, which said "Code via mcp too. Video via motion." That lines up with Figma's broader Config framing around code exploration, Motion, and agent-built tools in one canvas, as zoink's recap summarized.

Meng To's explanation in Meng To's thread adds the missing why: motion and shaders get manual controls for the last 10 percent, while MCP can offload conversion work between AI tools, Figma, and code.

Figma shipped the connector story next to two other agent surfaces:

• figmaweave said 20-plus Weave workflows now run directly in the design canvas for tasks like style transfer, product shoots, material extraction, and art direction.
• figma's plugins post said users can describe a generative plugin's behaviors, controls, and parameters, then have the Figma agent build it.
• zoink's Weave post said those workflows can be shared and remixed across a team.

That matters because connectors give the agent somewhere to pull context from, while Weave and generative plugins give it somewhere to act.

Figma said the design agent beta was opened to 100 percent of Pro, Org, and Enterprise plans in its pre-keynote post. Generative plugins were marked beta in figma's follow-up, and Motion was also called beta in figma's Motion follow-up.

So the connector launch arrived with real surfaces to test, not just a future-facing keynote slide deck.