Case study

Wiring Figma design context into agents with Modiva

A look at how teams use Modiva with Figma — reading files, components and versions and exporting node images to feed docs, tickets and handoff — giving AI agents safe, scoped, read-only access without building and maintaining a custom integration.

This is a representative example of the Modiva + Figma workflow. Have a story to share? Tell us and we’ll feature it here.

The challenge

Design lives in Figma, but the work that depends on it — docs, tickets, dev handoff, review — usually lives everywhere else:

• Design lived in Figma while docs, tickets and dev handoff lived elsewhere — pulling component names, file versions or exported assets across meant manual copy-paste.
• Changelogs and release notes needed current previews of the changed frames, but screenshots pasted into a doc went stale the moment the design moved on.
• AI assistants had no scoped, revocable way to read Figma files — sharing a personal access token was the only option, and that key could do far too much.

The approach with Modiva

1. 1

   Connect once with OAuth

   The team connects Figma from Modiva in a couple of clicks. Modiva owns the Figma app, so there's no developer app to register and no personal access token to circulate — the token is scoped to the granted read scopes, encrypted at rest, and revocable in one click.

2. 2

   Read design context where agents need it

   An agent reads a file's document tree, lists its published components and styles, and pulls file metadata and version history — feeding real design context into docs, changelogs and handoff notes through typed tools.

3. 3

   Export the exact frames, always current

   Instead of stale screenshots, an agent renders just the changed nodes to PNG or SVG at export time with images_export, so tickets and release notes carry previews pulled fresh from the file.

4. 4

   Design operations for AI agents via MCP

   An MCP key exposes the same read tools to AI assistants: read files, export images, list components and styles, pull versions. The team controls exactly which scopes an agent has, and pulling the key kills access instantly.

The outcome

• Design context — components, versions, exported assets — flows into docs and handoff automatically instead of by copy-paste.
• Tickets and changelogs carry previews rendered fresh from the file, so they never show a stale design.
• AI agents read Figma through a scoped, revocable, read-only OAuth connection — never a shared personal access token.