Tools worth knowing this week, with a source.
Gate: all
Config 2026 updates show the Figma agent moving from chat toy to workflow tool, with MCP connectors and enterprise-managed auth now GA. If you're on Figma, this is the bit worth actually trying.
help.figma.com (opens in a new tab)
Your move
open Figma, find the agent chat, and give it one real task from your backlog (rename a messy layer structure, generate variant states) — see where it breaks.
Figma pushed updates to its MCP Server and Code Connect this week, letting AI agents read and write design context straight to the canvas. It's free during the current beta, moving to usage-based pricing later.
figma.com (opens in a new tab)
Your move
Connect Figma's MCP server to one file this week and audit what design context it actually exposes.
Figma launched a dedicated MCP Catalog listing which AI clients (Cursor, Zed, OpenHands, ServiceNow's Build Agent) can connect to its MCP server. It's the clearest sign yet that MCP is becoming the standard bridge between Figma files and AI coding agents.
figma.com (opens in a new tab)
Your move
Open the Figma MCP Catalog page and read the setup guide for one client (even if you don't install it) — know what it actually does before it comes up in an interview.
Model Context Protocol now has an estimated 15,000+ live servers and first-class support in Cursor, Claude, ChatGPT, Copilot and VS Code. It's moved from novelty to baseline plumbing for AI-connected tools.
tech-insider.org (opens in a new tab)
Your move
Spend 20 minutes reading the MCP basics, then check if any Figma or Penpot plugin you use actually mentions MCP support in its changelog — don't just take a landing page's word for it.
Figma's MCP server now supports wiring an AI agent to a live file and out to your real API, not just reading specs. Teams are treating it as an infra decision, not a demo trick.
agence-scroll.com (opens in a new tab)
Your move
Set up Figma's Dev Mode MCP server locally, connect it to Cursor or VS Code, and pull one real component's spec into a codebase this week — note exactly where it breaks.
A warehouse software company just announced its own MCP server launch, proof this pattern is spreading well beyond design tools. If unrelated B2B software is shipping MCP support, expect the rest of your stack to follow.
jascicloud.com (opens in a new tab)
Your move
Next time you open a plugin or integration panel in your design tool, check if it mentions MCP — and if it does, have a poke around what it actually exposes.
Figma's MCP server now lets Claude Code, Cursor and Codex write directly into your files via a new use_figma tool. It's brand new — most designers haven't tried it yet.
Your move
Set up Figma's MCP server with a free AI coding tool (Cursor or Claude Code) this week and try one small, low-stakes edit — a colour token swap, not a full flow — to see where it breaks.
Figma's May 2026 release notes reveal ongoing upgrades to the MCP server and canvas agent — deeper code-to-canvas sync, design-system connections, and real production use at Uber. It's a sign this is now a maturing workflow, not a one-off launch.
youtube.com (opens in a new tab)
Your move
install the Figma MCP server in Cursor or VS Code this week and run one prompt to pull a component onto the canvas — see what it gets right and wrong.
Figma shipped a dedicated design agent that works directly in the file alongside you, not in a side chat window. It's tuned to respect your existing components and design system rather than freelancing.
figma.com (opens in a new tab)
Your move
open the agent (if you have beta access), point it at one real frame using your team's components, and check how many outputs actually match your existing styles before trusting it on live work.
