Figma plugin and more
The Figma plugin, the Claude Code skill and the Cursor setup: what each one does and where it stands.
Besides the API, there are integrations ready to connect BannerMotion with the tools you already work in. This is what exists today.
Figma plugin
You select one or more frames (each frame is a size: 300x250, 728x90…) and the plugin creates the animated banner through the API:
- It exports each frame's layers: texts (content, family, weight, size, color, alignment), images, logos, vectors and shapes, with their box relative to the frame.
- It uploads the images and logos to the workspace library (
POST /api/v1/assets). - It creates the banner (
POST /api/v1/banners) with the composition inreference, the sizes of all the frames and apromptthat summarizes it. - It follows the job and, when it finishes, shows the link to the banner in the studio (
appUrl).
It needs a bm_live_… key with the generate and read permissions (or bm_test_… to try it without credits). It is stored only on your computer.
referenceaccepts up to12frames (one per size) and60layers per frame; if a frame has more, the texts, images and vectors, the CTA button and the largest shapes are kept.- Effects (shadows, gradients, blurs), complex masks and auto layout are not described.
- Typefaces are named by family and weight; the font files are not uploaded.
Claude Code skill
An optional skill that teaches Claude Code the whole MCP server flow: checking the balance, generating, looking, iterating, adding sizes, exporting and what to do on each error. The skill folder (bannermotion) is copied to ~/.claude/skills/ or to the project's .claude/skills/. [PLACEHOLDER: skill download channel]
Cursor
An mcp.json file ready for the MCP server. Copy it to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).