An MCP image and video connector, explained for designers
How to generate stills and short clips from inside the AI assistant you already use, without opening another tool.
Cancel anytime before day 7 · no lock-in
What an MCP connector actually is, for people who make things
MCP is a small standard that lets an AI assistant reach tools that live outside it. Figgshield is one of those tools. It runs as a server at https://api.figgshield.ai/mcp, and once your assistant knows about it, generating an image or a video becomes something you ask for in plain language.
The practical result for a designer is that you never open a separate generation site. The same window where you sketch ideas, rename layers, or write UI copy can now return a finished picture or a short clip. Your assistant makes the call; you describe what you want.
Getting connected in your editor
It works with Claude desktop and Claude Code, Cursor, Windsurf, and ChatGPT in Developer Mode on a paid plan. Any agent that speaks MCP can use it too.
You add the connector once by pointing it at the server URL. After that it shows up as an available tool, and the model reaches for it when your request calls for an image or a video.
Your first comp, from prompt to file
The image model is Nano Banana 2 from Google. You describe the scene and pick a size, and the file comes back on a private link.
If you want a variation, you send a reference image with your next prompt. That reference is held in memory for the run and never stored, which matters when the source is a client's unreleased product shot.
- Describe the image: a matte ceramic mug on a linen surface, soft window light from the left, muted palette.
- Pick a size. Nano Banana 2 renders at 1K or 2K for 8 credits, or 4K for 16.
- Open the private link that comes back. The file sits there for seven days.
Turning a still into motion
When an image is close, you can animate it instead of starting over. Pass the id of an image you already generated and the connector uses it as the first frame of a video.
Two video tiers exist: Kling 3, and a faster Kling 3 Turbo when you want the result sooner. A five second clip is 35 credits, drawn from the same balance as your images.
A common loop is to generate three product stills, keep the best, then send its id to make a five second turn or a slow push in. You are animating the exact frame you approved, not a near copy of it.
Where it sits next to Figma and the rest of your stack
This is not a design editor and it does not try to be. It produces raw material: hero images, texture plates, placeholder photography, motion tests. You pull the file down and finish it wherever you already work, whether that is Figma, After Effects, or a layout tool.
The real value is speed at the messy early stage. When a brief is still moving, you can spin up ten directions in the same conversation where you are writing that brief, throw away nine, and carry one into real production.
What a working day costs, and what is kept
Pricing is at cost. Figgshield does not mark up Nano Banana or Kling; you pay what the models cost. The only thing the company earns on is credits that people buy and never spend, so there is no reason to inflate a single generation.
One balance covers both images and video. The $5 Pro trial runs seven days and includes 150 credits, enough for about a dozen 2K images plus a five second clip. There is no free tier. Cancel before day seven and you pay nothing more. See pricing or top up on the credits page.
Every generated file lives on its private link for seven days and is then deleted, and reference images you send are never written to disk. For client work that is a reasonable default: nothing lingers on a server after the week is out.