Generate images and video in VS Code with an MCP server

One MCP server, three ways to reach it

VS Code does not generate media on its own. What it has, through several AI extensions, is an agent that can call outside tools over the Model Context Protocol. Copilot in agent mode, Continue, and Cline all speak that protocol.

Figgshield is one of those tools. It is a remote MCP server that lives at https://api.figgshield.ai/mcp. You point your extension at that URL, authorize once, and the agent gains two abilities: make an image and make a video.

The work happens on Figgshield's side, not on your machine. Nano Banana 2 from Google draws the images, Kling 3 handles video, and one credit balance covers both. None of this is tied to a single extension, so use whichever of the three you already run.

Add the server to Copilot, Continue, or Cline

Each extension stores MCP servers in its own place, but the entry is the same everywhere: a name and the Figgshield URL. The first tool call opens a browser to sign in and authorize, then the connection stays put.

For Copilot agent mode, VS Code reads a workspace file at .vscode/mcp.json. Add { "servers": { "figgshield": { "type": "http", "url": "https://api.figgshield.ai/mcp" } } } and reload the window. The server also appears if you run the MCP: Add Server command from the palette.

Cline keeps its list in cline_mcp_settings.json, reachable from the MCP Servers panel, where you paste the same URL into the Remote Servers tab. Continue uses ~/.continue/config.yaml, where the server goes under an mcpServers list with a name and the url.

Whichever one you use, confirm the two Figgshield tools show up in the extension's tool list before you prompt. If they do not, the server is not connected yet.

• Copilot in agent mode reads .vscode/mcp.json in the workspace.
• Cline stores servers in cline_mcp_settings.json, or use its Remote Servers tab.
• Continue declares the server in ~/.continue/config.yaml under mcpServers.

Ask the chat panel for a picture

You do not hand-write an API request. You describe the picture in the chat and the agent picks the tool and fills in the arguments.

Something like: "Generate a 2K hero image for a dev tools landing page, a dark terminal window with soft neon syntax highlighting, no text." The agent sends it to Figgshield and returns a link. Tell it where to write the file, for example "save it to public/hero.png."

Resolution is a word, not pixel dimensions. Nano Banana 2 takes 1K, 2K, or 4K. An image at 1K or 2K costs 8 credits, and the same image at 4K costs 16.

Iterating is a follow-up message. "Make it lighter" or "tighter crop" continues from the last image rather than starting over.

Keep the private links out of your commits

Figgshield's output is deliberately short-lived. A generated file sits on a private link for seven days and is then deleted. That is long enough to download it, review it, and commit the copy you want to keep.

So treat the link as temporary, not as the asset. When the agent returns a URL, have it save the file into the repo in the same turn, then reference the local path in your code. A stale link in a commit helps no one once the seven days pass.

If you generate throwaway placeholders during a build or a demo, drop them in a folder your .gitignore already covers, so scratch art never lands in history. A reference image you send the other way, say a logo the picture should match, is used in memory for that one generation and is never stored on the server.

Turn a mockup into a five-second clip

Every image you generate has an id. To animate it, you pass that id instead of describing the scene again, so the clip keeps the exact frame you already approved.

Video runs on Kling 3, with a faster Kling 3 Turbo tier for when speed matters more than the last bit of polish. A five-second clip is 35 credits, billed from the same balance as your images.

In practice: "take that hero image and make a five-second loop with a slow push-in." The agent hands the image id to Figgshield and polls until the clip is ready, then gives you a link to download.

What it costs and the trial

Figgshield bills at cost. It does not mark up the underlying models. The only money it makes is on credits people buy and never spend, so the rate you pay stays close to what the model costs to run. Current numbers are on the pricing page.

There is no free tier. The 7-day Pro trial costs $5 and includes 150 credits. Cancel before it renews and you pay nothing more.

Because one balance covers images and video, you do not manage two budgets. A handful of 2K images and a couple of short clips come out of the same pool, and you can check what a specific option costs before you run it.