Figma adds FigJam MCP tools for generate_diagram and board readback

• Figma shipped three new FigJam MCP pieces on April 28: generate_diagram, the figma-use-figjam skill, and get_figjam, according to figma's product post.
• The new flow covers both creation and readback, because figma's list says one tool generates architecture diagrams and ERDs while another reads a board back into next steps.
• The figma-use-figjam skill is aimed at direct board editing, with figma's announcement describing notes, code blocks, and annotations added from the MCP workflow.
• Figma linked the release to a live FigJam MCP page, while zoink's reaction post zeroed in on architecture diagrams as the standout use case.

Figma is pushing FigJam closer to the rest of the agent toolchain. You can jump from the official rollout post to figma's feature list, and the attached demo clip shows the pitch in one loop: generate a system map, drop structured notes onto the board, then read the board back into action items.

The clearest new feature is generate_diagram. In figma's announcement, Figma says it can create architecture diagrams and ERDs inside FigJam, which turns FigJam into an MCP target for system mapping instead of a place you update later by hand.

The first outside reaction also locked onto that piece. zoink called out "beautiful architecture diagrams in FigJam via MCP," which is exactly the kind of visual output AI-heavy product and design teams tend to share around.

Figma's second addition is a skill called figma-use-figjam. According to figma's thread follow-up, the skill can place notes, code blocks, and annotations directly on the board.

That matters because the release is not only about drawing a diagram. It also adds a structured way for an agent to leave working context inside the same canvas, which is a better fit for design and planning work than dumping everything back into plain text.

The third piece is get_figjam. In figma's list, Figma describes it as a tool that reads your board and maps out next steps.

That gives the workflow a reverse direction. The board is no longer only an endpoint for generated artifacts, because the MCP layer can also treat the board as state to inspect and continue from.

Figma demo of the FigJam MCP workflow

The official post shipped with a roughly 20-second demo video attached to figma's tweet. Even without extra narration, the clip makes the product angle obvious: diagram generation, board edits, and board readback are being presented as one continuous loop.