Correction, 2026-10-01: an earlier version of this page quoted canvas prices instead of the connector's (Kling through the connector is Kling v3 Standard, 86 credits, and needs a start image), had the worked example upscale a video to 4K (8frame has no video upscaler), put it under $0.50 (it is 92 credits, about $0.92), and gave a Nano Banana Pro time of 8 seconds (the measured median is 37). Prices and tools now come from the connector's own configuration, and the Cursor settings path from Cursor's current docs. A second review the same day found more: the latency notes quoted Nano Banana 2 and Pro times, but the connector's Nano Banana is the Classic model, which has no measured time; the page suggested generated b-roll for App Store previews, which Apple's guideline 2.3.4 limits to screen captures of the app; it described generated clips as README demos that show a feature in motion, though a generated clip cannot show your working product; and the Claude Code steps left out the /mcp sign-in. Those parts are rewritten, with Apple, Google Play, Cursor and Claude Code docs cited in the sources.
If you ship product, you already know the gap: the feature works, the landing page is written, and now you need a hero video, a header for the README, and a clip for the announcement. Normally that means a context switch out of the editor, into a separate tool, back with an asset, and a lot of lost focus. This guide closes that gap. Add the 8frame MCP server to Cursor or Claude Code and you generate images and video from the same window where you write code.
The 8frame MCP server exposes image generation and editing, background removal, image upscaling, video and music. Cursor and Claude Code are both MCP clients, so once the server is in their config, the coding agent can call it like any other tool. You describe the asset in the chat panel, 8frame generates it, and the result comes back as a file link. Below is the config for each, the dev use cases where it fits, and the latency reality so you know when to reach for it and when not to.
What you'll be able to do from the editor
The core steps of the canvas: generate a still, animate it, edit an existing frame, upscale a still. The difference is you're doing it inline with your build, with fewer settings per model than the canvas offers. A few things developers reach for most:
- Release promo clips for the launch post, the product page, or ads that point to your store listing (store previews themselves have stricter rules, covered below).
- README and docs header visuals that set up a feature; the walkthrough of how it works stays a screen recording.
- Landing page hero videos for the marketing site you maintain in the same monorepo.
- Social launch assets when you ship and need something for the announcement.
Cost draws from your 8frame credits at the connector's prices, with no separate MCP fee. The ones a developer hits first: a Nano Banana still is 6 credits (the connector runs Nano Banana Classic, not Nano Banana 2 or Pro), a 5-second Kling v3 Standard clip with sound 86 (Kling through the connector is v3 Standard only, and it needs a start image), and an 8-second Veo clip 448 on Veo 3.1 Standard, which is the connector's Veo default (the canvas Veo tool opens on Fast), 168 on Fast and 54 on Lite. Ask for the tier by name. The full tool-by-tool price list is in how to generate AI video from Claude.
Add the server to Cursor
Cursor reads MCP servers from an mcp.json file: ~/.cursor/mcp.json for a global server available in every project, or .cursor/mcp.json in a repo for a project-scoped one. Add 8frame under mcpServers:
{
"mcpServers": {
"8frame": {
"url": "https://mcp.8frame.co/mcp"
}
}
}
Cursor's docs list MCP servers under Customize in the sidebar, where each server can be toggled on or off; check that 8frame is on and its tools appear. Cursor supports OAuth for servers that require it, and 8frame does: you sign in to your 8frame account on first use so generations draw from your credits. By default Cursor asks for your approval before it uses an MCP tool, so each generation waits for your OK before it spends credits.
Add the server to Claude Code
Claude Code adds remote MCP servers over HTTP with one command:
claude mcp add --transport http 8frame https://mcp.8frame.co/mcp
Without a scope flag the server is added at local scope: this project only, for you. Add --scope user to register it once for all your projects, or --scope project to write it to .mcp.json in the project root and share it with teammates through version control. Verify with:
claude mcp list
Then run /mcp inside Claude Code and follow the browser steps to sign in to your 8frame account. Once that's done, ask Claude Code to generate directly in your session. The full server reference and the claude.ai Connectors route (for prompting outside an editor) are at 8frame.co/mcp.
Where this pays off
Store listings: around the preview, not inside it. Apple's App Store Review Guidelines (2.3.4) say previews "may only use video screen captures of the app itself", so generated footage does not belong in an App Store preview. Google Play's preview-video guidance reads "Aim for at least 80% of the video to be representative of the user experience" and asks you to limit "pre-rendered or promotional content". Where generated clips fit around a release is everything that points to the listing: the launch post, the product page, the ads.
README visuals. A generated clip cannot show your actual UI, so the how-it-works part of a README stays a screen recording or GIF. A short generated clip or still can sit above it as a header for the launch or the docs page. Generate it while the feature is fresh in your head, link it in the README, move on.
Landing hero video. If you maintain the marketing site in the same repo, you can generate the hero clip without ever leaving the editor. Iterate on the brief in the chat panel, generate a couple of options, pick one, ship.
Launch-day social. When you cut a release you often want a clip for the announcement thread. Ask for three or four vertical variations from one 9:16 still and you've got a hook-testing set: the still at 6 credits plus four Kling v3 Standard clips at 86 each is 350 credits, about $3.50.
A worked example from Claude Code
Say you just merged a feature and want a landing hero. In the Claude Code session:
"Generate a photorealistic 16:9 still with Nano Banana of a sleek laptop on a minimalist desk in soft morning light, screen glowing. Then animate it with Kling into a 5-second slow push-in."
Claude Code calls the Nano Banana tool for the still (6 credits), passes it to Kling as the start image (86 with sound), and returns file links. Total: 92 credits, about $0.92. You reviewed the concept in text, spent two generations, and never opened another app. For a text-only clip, name a text-to-video model instead: "use Veo 3.1 Lite" is 54 credits for 8 seconds with sound, while plain "Veo" runs Standard at 448.
Asking for a 4K version of the clip will not work: 8frame has no video upscaler, and the connector's upscalers take images only. You can upscale the still before animating it, but the clip comes back at the model's own resolution (720p for Kling v3 Standard).
Sharing the setup with your team
If your whole team works out of the same repo, commit a project-scoped config so nobody has to set it up individually. In Cursor, that's .cursor/mcp.json in the repo root with the 8frame server block above; anyone who opens the project in Cursor picks up the server from that file and signs in with their own 8frame account on first use. In Claude Code, run claude mcp add --transport http --scope project 8frame https://mcp.8frame.co/mcp, which writes the server to .mcp.json in the project root; commit that file, and Claude Code asks each teammate to approve the project server before it is used.
Credits are not pooled: each generation is charged to the account of the person who runs it. The practical upside is that generating a launch asset stops being "the one person who owns the design tool" and becomes something any engineer with an 8frame plan can do while they're already in the code. A backend dev shipping an API can cut a clip for the changelog without pinging anyone. The 8frame entry holds only a URL, so there is no secret in it; for other servers that need keys, keep them out of committed config and use the client's environment-variable interpolation instead.
Honest latency and QC notes
It is not instant. These are real generative models. Measured on 8frame (medians over 120 days), a 5-second Kling v3 Standard clip, the connector's Kling, takes about a minute (60 seconds); a Seedream 5 Pro image, the connector's Seedream, about two minutes (119 seconds); and a 720p Seedance 2.5 clip of 7 to 11 seconds, the Seedance version the connector runs, about five minutes (296 seconds) (how long AI video generation takes). We have no measured time for Nano Banana Classic, the connector's Nano Banana, so we don't quote one. If a generation runs past 10 minutes, the connector returns a task ID to check later. That's fine for an async "generate while I keep coding" loop, but don't expect autocomplete speed.
Review at full size. The editor chat gives you a file link. For anything that ships (a launch post, a public hero), open the file and inspect it at full size. Generative video can produce warped details, and a thumbnail hides them.
The editor is a front door, not the whole surface. Config-driven generation from Cursor or Claude Code suits one-off assets and fast iteration. For a multi-reference composition, precise layout, or a reusable workflow template your team runs repeatedly, the full canvas is the right place. Connector requests also have a daily credit cap, as a safety limit on spend an agent triggers; the canvas does not.
FAQ
Can I generate AI video from Cursor?
Yes. Add https://mcp.8frame.co/mcp to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) under mcpServers, sign in to 8frame on first use, and ask the agent for a clip.
What does a clip from Claude Code cost? The connector's prices: 86 credits for a 5-second Kling v3 Standard clip from a start image, 54 for an 8-second Veo 3.1 Lite clip with sound, 448 for Veo 3.1 Standard, the connector's Veo default.
Can I use Nano Banana Pro or Kling v3 Pro from my editor? No. Through the connector, Nano Banana is the Classic model (6 credits) and Kling is v3 Standard (86 credits for 5 seconds, from a start image). Nano Banana 2 and Pro and Kling v3 Pro are on the canvas.
Can the MCP server upscale video? No. 8frame has no video upscaler; its upscalers (Clarity, BRIA, Topaz) work on images.
Sources
- Cursor MCP config paths, server toggles under Customize, OAuth support, tool approval by default and config interpolation: cursor.com/docs/context/mcp, checked 2026-10-01
- Claude Code
claude mcp add, scopes,.mcp.json, approval of project servers and/mcpsign-in: Claude Code docs, MCP, checked 2026-10-01 - App Store previews limited to screen captures of the app: App Store Review Guidelines, 2.3.4, checked 2026-10-01
- Google Play preview video guidance: Add preview assets to showcase your app, checked 2026-10-01
- 8frame sign-in when connecting: 8frame.co/mcp, checked 2026-10-01
- Connector tools, models, defaults, prices, wait limit and daily cap: 8frame MCP server configuration, read 2026-10-01
- Canvas Veo default (Fast), canvas models and per-user credit charging: 8frame tool registry and back-end code, read 2026-10-01
- Generation times: 8frame production data, read-only, medians over 120 days to 2026-09-30
Related guides
Prefer prompting outside an editor? How to generate AI video from Claude covers the claude.ai Connectors setup. Building an automated system rather than prompting by hand? How to add video generation to your AI agent treats the same MCP server as an agent tool. And if you're new to the protocol itself, what is MCP explains how all of this connects.
Add the 8frame MCP server to your editor and generate from where you already work, or start from a ready-made board on 8frame workflows.
Try it without signing up: the 8frame canvas opens on a real board. The canvas is free and unlimited; generation is paid from $19/month.