Weave: Visual Programming for AI Pipelines
Talofa. This is Liam, in for Bear. This one is an experiment report. Overnight, at Bear's request, an agent checked whether his Figma for Education account can reach Weave through Figma's MCP server. Bear has since reviewed it, from an educational perspective.
Weave: Visual Programming for AI Pipelines
Talofa. This is Liam, in for Bear. This one is an experiment report. Overnight, at Bear's request, an agent checked whether his Figma for Education account can reach Weave through Figma's MCP server. Bear has since reviewed it, from an educational perspective.
Series: Figma for Educational AI Topic: FIGMA · WEAVE
Chapters
0:00 Introduction 2:38 Verdict 2:59 Your Turn
YOUR TURN
Your turn. Paste your plan's help page into Claude, then this: Here's my plan's help page. For each AI feature, tell me: included, separate account, or costs credits. Quote the exact line that says so. It sorts the marketing from the fine print, and the fine print is exactly what stopped this experiment. Then check the quotes yourself, against the
@NikBearBrown
Part of the Figma for Educational AI series.
Sources and citations: see the reel's SOURCES.md in the open textbook.
▶ The full series playlist — Brutalist https://www.youtube.com/playlist?list=PLG9H-C6rp5RU
What this video covers
- 0:00 — Introduction
- 2:38 — Verdict
- 2:59 — Your Turn
Transcript
A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.
Introduction
[0:00] Talofa, this is Liam in for Bear. This one is an experiment report. Overnight at Bear's request, an agent checked whether his Figma for education account can reach Weave through Figma's MCP server. Bear has since reviewed it from an educational perspective. Most people picture Weave as a prompt box that comes with their Figma plan. It's a pipeline of nodes and it sits behind a separate account. Tonight's question is only the second half. Can this account get in? First, the idea. Visual programming means you build a program by wiring boxes together instead of writing lines. In Weave, each box is a node, an input, a model, an edit. A wire carries one node's output into the next. The whole graph is the pipeline. Publish that graph and it becomes a tool. The inputs you left open become the tool's form. Figma's MCP server describes each input with the same fields, a node ID, a name, a type, a default, and whether it's required. To an agent, a pipeline looks like a
Function it can call. Bear's MCP server offers nine Weave tools. Five only look, list the tools, find a model, read a tool's inputs, fetch run outputs. Four act, upload an asset, run a tool, run a model, cancel a run. Running is where credits go. Tonight, the agent was allowed to look and nothing else. So, the agent called Weave list tools. This is the whole reply word for word. Then Weave find model asking for nano banana. The same reply word for word. No tools listed. No models found. The door didn't open far enough to see what's inside. A third call, who am I, pinned down where that answer came from. Bear's education team student tier, a full seat. Three calls out of a budget of five. Zero credits spent. Nothing was run. Why the refusal? Weave is a separate product. Figma bought Weavey and renamed it, and it still has its own account, its own billing, and its own credits. Figma's MCP docs say it plainly. Running Weave through MCP
Spends Weave credits and needs a paid Weave account. The education plan's 3000 AI credits don't reach it. There's a second door, though. Figma also Weave tools inside Figma design in the tools panel. The help pages list that for professional plans and up, free during the open beta, and not for K-12 education. Bear's plan is professional, but one FAQ says paid plans and his costs nothing. An agent can't open that panel. Bear has to look. Bear reviewed this the next day from an educational perspective and agrees with its point. There's no design file here, so his note isn't in Figma. It sits in the experiment record right under the evidence it's about. On the films that have a Figma file, it went into the file itself. If someone else had to act on it, a small script would tell them on Slack, Discord, or email with a link, not a copy. Here, no one else did, so nothing was sent. The Weave check and any spend still wait for Bear.
Verdict
[2:38] Let's recap with Claude verdict week for the MCP path. Weave isn't reachable from this account tonight. It needs a separate linked Weave account, and Figma's docs say a paid one. The tools panel inside Figma design is still unverified. Running any pipeline spends credits, so that waits for Bear's approval. An agent checked this overnight, and Bear has since reviewed it from an educational perspective. Your
Your Turn
[2:59] Turn. Paste your plan's help page into Claude, then this. Here's my plan's help page. For each AI feature, tell me included, separate account, or costs credits. Quote the exact line that says so. It sorts the marketing from the fine print, and the fine print is exactly what stopped this experiment. Then check the quotes yourself against the page. Weave visual programming for AI pipelines at Nick Bear Brown.
