Generate images and video in Zed with MCP

Two tools show up in the Agent Panel

Once Figgshield is connected, Zed's Agent Panel gains two abilities. One generates stills with Nano Banana 2, Google's current image model. The other generates video with Kling 3, with a faster Kling 3 Turbo tier when you want the result sooner.

You ask in the same plain language you already use with the agent. Something like: generate a 2K header image, dark slate background, a single terminal window glowing in the center, clean and minimal. The image comes back in the panel, ready to save into the project.

Images return in the same call, so you see them right away. Video takes longer, so the job is queued and the agent polls it until the clip is ready. You can keep editing while it runs.

Add Figgshield to settings.json

Zed launches MCP context servers as local processes, so a remote server like Figgshield connects through a small bridge. Open your settings with cmd+, or edit ~/.config/zed/settings.json directly.

1. Add a context_servers entry that runs the bridge: set "command": "npx" and "args": ["-y", "mcp-remote", "https://api.figgshield.ai/mcp"].
2. Save the file. Zed picks up the change on its own; reload the window if the server does not appear.
3. On the first call a browser opens. Sign in with Google and pick a plan. The $5 Pro trial is the quickest way in.
4. Open the Agent Panel and ask it to generate something to confirm the tools are live.

A first request: the empty-state illustration

Say you are building a screen and it needs art for the empty state. Instead of opening a separate tool, tell the agent: generate a 1K illustration, soft green background, a friendly robot holding a wrench, flat style, no text. Nano Banana 2 returns the still in the panel.

If it is not quite right, you correct it the way you correct code. Make the robot blue, more negative space, warmer light. The agent rewrites the prompt and regenerates from your note.

When it looks right, ask the agent to save it to src/assets/empty-state.png and reference it in the component. The asset never left Zed.

Turn that frame into a five-second clip

Every image you generate carries an id. Pass that id to the video tool and Kling animates the exact frame instead of starting over. This is the image-to-video path.

It suits a landing hero that wants a little motion. Generate the key frame first, get it approved as a still, then animate the frame you already like rather than gambling on a fresh render.

A five-second clip is 35 credits, whether it starts from an image or from a text prompt.

What a render costs, priced at cost

One credit balance covers both models. A Nano Banana 2 image is 8 credits at 1K or 2K and 16 at 4K. A five-second Kling clip is 35.

Credits are priced at what the models cost us, with no per-generation markup. The only money Figgshield makes is on credits people buy and never spend, so there is no reason to inflate a single render. The live credit table lists every option.

There is no free tier. The Pro trial runs 7 days and includes 150 credits. Cancel before it renews and you pay nothing more.

One connector, whichever editor you land in

Figgshield is not tied to Zed. The same MCP server works in Claude Code and Claude Desktop, in Cursor and Windsurf, in ChatGPT Developer Mode on a paid plan, and in any other MCP agent.

That matters if you move between tools during a day. The credits, the models, and the tool calls are identical, so a prompt you refined in Zed behaves the same when you paste it into another agent later.

One note on storage: a finished image or clip sits on a private link for seven days so you can download it or have the agent write it into the repo, then it is deleted. A reference image you send into a prompt is used in memory and never stored.