Files
frames/docs
Vance IngallsandClaude Opus f8892019b1 docs(figma): lead setup with "which credential do I need", not a token wall
The old setup section was one long token-minting flow with the MCP
connector as an afterthought — but motion/shaders/storyboards need
only the connector (no token at all), and even brand tokens are
easier via MCP on any non-Enterprise plan. A reader wanting only
motion had to wade past REST scope tables meant for a different path.

Restructured into a decision table (what you want → which credential)
followed by two equal, independent steps. Step A's scope list now
states the 3 boxes to check on a normal (non-Enterprise) account
up front, instead of a generic 4-scope table the reader has to
interpret themselves. Step B now states the MCP connector's actual
capability (variable reads work on any plan, rate-limited by tier —
6 calls/month on Starter) instead of "no scopes to configure," which
undersold what it can do.

Co-Authored-By: Claude Opus <[email protected]>
2026-07-09 19:41:43 -07:00
..
2026-07-09 12:01:33 -07:00
2026-07-06 15:29:37 -07:00