Figma
Read Figma files, nodes, images, comments, projects and versions via the Figma REST API.
About
Figma ships in the w6w first-party pack. It declares 10 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.figma- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Developer Tools
Overview
Figma’s REST API is read-heavy by design, and so is this app: it pulls a file’s structure, individual nodes, rendered images, comments, project listings and version history straight into a workflow, without anyone opening the design tool itself.
Rendering is the standout capability here — a node can be turned into a PNG, JPG, SVG or PDF on demand, which is the piece a workflow actually needs to hand a design off somewhere else, whether that is a marketing asset pipeline or an automated changelog. Comments are the one part of a file this app can also write to, posting or removing a note on a design rather than only reading what is already there.
Everything else about a file’s actual content — the layers, components and styles a designer edits — stays read-only here, because Figma’s own API offers no way to write it. What this app covers is exactly the part meant for integration: pulling structure and renders out of Figma and keeping a conversation going on top of a file.
Build with Figma
Three routes to the same 10 actions. The Workflow tab is generated from Figma's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get Images
get-images Render one or more nodes to images (PNG/JPG/SVG/PDF) and return download URLs.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Figma's real ids.
{
"manifestVersion": "2",
"name": "figma-example",
"steps": [
{
"id": "get-file",
"uses": {
"app": "io.w6w.figma",
"action": "get-file",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"fileKey": "<fileKey>"
}
}
]
}Here are some of the things you can do
-
Get File
readget-file -
Get Current User
readget-current-user -
Get File Nodes
readget-file-nodes -
Get File Versions
readget-file-versions -
Get Images
readget-images
+5 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Figma, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Figma. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "get-file",
payload: {
fileKey: "<value>",
// version: "<value>",
// ids: "<value>",
// depth: "<value>",
// geometry: "<value>",
// pluginData: "<value>",
// branchData: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action get-file --payload '{"fileKey":"<value>"}'Give an AI agent Figma — without giving it Figma's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.figma#get-file",
"input": {
"fileKey": "<fileKey>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Figma connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Figma's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Figma itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Figma declares its own checks, so its health is a property of the app rather than something the host guesses at.
Figma platform status
Atlassian Statuspage rollup for status.figma.com, with per-component detail. Unauthenticated and unsigned.