Your Keldwave balance, inside Claude
Connect it once and ask for images or video while you work. The same balance as the web, without switching windows.
What using it looks like
You ask in one sentence. Claude picks the model and the format, says what it will cost, and hands back the result with your remaining balance. Switch clients to see it where you actually work.
I need an odd, beautiful cover image for my newsletter. It is about insomnia. An astronaut in a laundromat at 3am: it carries the idea without illustrating it literally. Going with Nano Banana Pro, which holds the helmet reflection and the fluorescent light well. generate_image (Nano Banana Pro · 3:4 · 2K) — 23⚡. And the balance left, as in every response
Example conversations, different on every visit. The images are real, generated in Keldwave with the models and prices you see.
Connect it
You need a Keldwave account with balance and a compatible client: Claude web, Claude desktop, Claude Code, Cursor or Codex. You connect once and it stays connected.
Create your token
This is the credential that identifies your account. It is only shown when you create it.
API tokens
Connect Keldwave to Claude Code or any MCP client and generate from your terminal. They spend the same balance.
Loading…
How do I connect it to Claude Code?
Create a token above and use it in place of kw_TU_TOKEN. For security, a token is only shown when you create it.
claude mcp add --transport http keldwave https://keldwave.com/api/mcp \ --header "Authorization: Bearer kw_TU_TOKEN" --scope user
In Claude Code, type /mcp: “keldwave” should show up as connected.
Paste this where your client keeps its MCP servers
This command registers Keldwave in Claude Code and makes it available across all your projects.
claude mcp add --transport http keldwave https://keldwave.com/api/mcp \ --header "Authorization: Bearer kw_TU_TOKEN" --scope user
Swap kw_TU_TOKEN for the token from step 1. Avoid project scope: it would write your token into a file that usually ends up in git.
Check it
In Claude Code type /mcp; in Claude web and desktop, look at your connector list. "keldwave" should show up as connected.
Now you can ask for things like "generate an image of a fox in the snow" or "what would a 5 second video cost?". For a job with craft to it, just say what you want: it loads the playbook itself.
Already connected? Manage and revoke your tokens in Account security
Images on demand
Describe what you want and get the URLs back, with the model and format you pick.
Video without watching a spinner
Kick off the video, carry on with your work and pick it up later by its id.
Prices before you spend
Check models and quote a generation without running it. Every reply tells you the balance left.
Nine playbooks included
The tools know how to generate. The playbooks know what makes a good thumbnail, product shot or storyboard: what to ask, which format, and where to stop before spending.
keldwave-adsCampaign creative across every format
keldwave-brandkitVisual identity: palette, logo and type
keldwave-characterThe same character across a whole series
keldwave-fashionkeldwave-infographickeldwave-mockupkeldwave-productPackshot, lifestyle and marketplace listing
keldwave-restyleYour image reinterpreted in other styles
keldwave-social-packOne concept as feed, story, banner and avatar
keldwave-storyboardSequences that look shot by the same person
keldwave-thumbnailThumbnails that read at 200 pixels
keldwave-videoThe right model, with the spend under control
Nothing to download and nothing to configure: the connector serves them, and Claude loads the one it needs. If you would rather have them always on, they are on GitHub
What you will actually use it for
The hard part is not installing it, it is knowing what to ask for. Four examples you can copy as they are.
Covers for your posts
The header image and the social one, in the right format, without opening an editor.
❯ generate a 16:9 cover for an article about distributed databases
Product and mockups
Show what you sell in context: on a table, in a hand, in a shop window.
❯ place this mug on a coffee table in morning light, product photo
Assets for layouts
Avatars, icons and filler backgrounds that are not the same stock photo again.
❯ give me 4 square illustrated avatars, same style, flat background
Short video for social
Five vertical seconds, ready to upload, while you carry on with your work.
❯ a 5-second vertical video: the logo forming out of light particles
What it can do
These are the tools Claude will see. Almost none of them spend; the ones that do ask for your approval, except cheap images and audio (under 50⚡) and whatever the allowance you choose in Security covers.
load_playbookNoLoads the house method for a kind of job
list_modelsNoAvailable models, prices and real limits
quoteNoQuote a generation without running it
balanceNoYour remaining balance
generate_imageYesGenerates images and waits for the URLs
generate_videoYesStarts a video: from text, from an image or from one frame to another
generate_audioYesVoiceover, music and sound effects for a video
confirm_generationYesCollects what you approved on keldwave.com
sound_libraryNoReady-made sound effects, free
check_jobNoPicks up an image job already started
video_statusNoCollects a video already started
media_uploadNoGives a URL to upload one of your own reference images
media_confirmNoVerifies the upload and makes it usable
media_import_urlNoImports an already published image as a reference
confirm_generation approves nothing: it only redeems a permit you already approved on keldwave.com while signed in. Without that step in the browser not a single ⚡ is charged, even if the model calls it.
Treat it like a password
The token can spend your balance. We only store its hash, so nobody can read it back, and you can revoke it any time: access is cut instantly.
How long it takes
Images are waited for right there. Video takes minutes: it starts, returns an id and you pick it up later, without blocking your session.