The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the MCP Imagenate listing page.
An MCP server for image generation using multiple providers: Google Gemini, OpenAI (gpt-image), BFL FLUX, and Reve — plus short video clips through Google Gemini Omni.
| Name | Model ID | Best for |
|---|---|---|
nano-banana-2 | gemini-3.1-flash-image-preview | Fast, high-volume generation |
nano-banana-pro | gemini-3-pro-image-preview | Highest quality output |
| Name | Model ID | Best for |
|---|---|---|
gemini-omni-1.1-flash | gemini-omni-1.1-flash | 3–10 s clips with audio, legible on-screen text |
Uses the same GEMINI_API_KEY. Exposed through a separate generate_video tool —
see Tool: generate_video.
| Name | Model ID | Best for |
|---|---|---|
gpt-image-2 | gpt-image-2 | Previous generation, still the default here |
gpt-image-2.5-flare | gpt-image-2.5-flare | Fast generation, cheap at medium and high |
gpt-image-2.5-sunburst | gpt-image-2.5-sunburst | Precise edits, slower than Flare |
These are the only models here that can return a transparent background — see Transparent backgrounds.
| Name | Model ID | Best for |
|---|---|---|
flux-2-klein | klein-4b | Fast, lightweight generation |
flux-2-pro | pro-preview | Balanced quality and speed |
flux-2-max | max | Maximum quality |
| Name | Version | Best for |
|---|---|---|
reve-image | latest | Typography and layout fidelity |
This provider calls Reve's v2/image/create endpoint. latest is the only version
alias v2 exposes, and it is what the response reports back, so there is no dated
build to pin to. Do not confuse it with the v1 endpoints, which still serve the
older reve-create@20250915 model.
Things worth knowing before sending Reve a prompt written for another provider:
resolution is ignored — Reve has no size parameter and returns its own large
output. Exact dimensions vary between requests: 16:9 came back as both
5408x3072 and 5376x3072, and 3:4 as 3456x4800.inputImages become v2 references. Reve accepts at most eight; a longer list
is rejected before any of the files are read.Or install globally:
Set API keys for the providers you want to use:
Add to your claude_desktop_config.json:
| Variable | Required | Description |
|---|---|---|
GEMINI_API_KEY | * | Google AI Studio API key |
NANO_BANANA_API_KEY | * | Alternative to GEMINI_API_KEY (takes precedence) |
OPENAI_API_KEY | * | OpenAI API key |
GPT_IMAGE_API_KEY | * | Alternative to OPENAI_API_KEY (takes precedence) |
BFL_API_KEY | * | BFL FLUX API key |
REVE_API_KEY | * | Reve partner API token (from the API console at api.reve.com) |
REVE_API_TOKEN | * | Alternative to REVE_API_KEY (REVE_API_KEY takes precedence) |
NANO_BANANA_OUTPUT_DIR | No | Base directory for saved images. When set, all output and input paths are sandboxed within this directory. Recommended for production. |
* At least one provider API key must be set.
generate_image| Parameter | Type | Default | Description |
|---|---|---|---|
prompt | string (1-32,000 chars) | - | Text prompt describing the image |
model | see Models above | "gpt-image-2" | Model to use (available models depend on configured API keys) |
resolution | "1K" | "2K" | "4K" | "1K" | Output image resolution |
aspectRatio | see below | "1:1" | Aspect ratio of the image |
mode | "image" | "image_and_text" | "image" | Return image only, or image with description (Google models only) |
background | "auto" | "transparent" | "opaque" | "auto" | What the image sits on. "transparent" needs a gpt-image model — see below |
thinking | "none" | "auto" | "auto" | Controls model thinking (Google models only) |
outputDir | string | "." | Directory where images will be saved |
inputImages | string[] | - | File paths of images to send alongside the prompt (Google models, OpenAI gpt-image models via the images.edit endpoint, and Reve via v2 references) |
1:1, 2:3, 3:2, 3:4, 4:3, 9:16, 16:9, 21:9
background: "transparent" saves a PNG with an alpha channel, which is useful for
cutting out a subject to place on a slide or over another image.
Only the OpenAI gpt-image models can do this. Asking any other model
(nano-banana-*, flux-2-*, reve-image) for a transparent background fails
with an error rather than quietly returning an opaque image — the request is
rejected before it is sent, so nothing is spent on it. Writing "transparent
background" into the prompt does not help either: those providers have no
transparency mode at all.
"opaque" forces a filled background on every provider that reads the field, and
"auto" — the default — leaves the choice to the model, which is what this server
has always done.
Returns a JSON object:
descriptionis only present whenmodeis"image_and_text".
generate_videoAvailable when a Google key is configured. Generates one clip with audio and saves it as an mp4.
| Parameter | Type | Default | Description |
|---|---|---|---|
prompt | string (1-32,000 chars) | - | Subject, motion, camera, and any on-screen text spelled out exactly |
model | "gemini-omni-1.1-flash" | "gemini-omni-1.1-flash" | Video model to use |
durationSeconds | integer 3–10 | 5 | Clip length. Cost scales with the second, and so does generation time (roughly 1 min for 5 s, 2 min for 10 s) |
resolution | "360p" | "720p" | "1080p" | "4k" | "720p" | Playback resolution. 360p is the cheapest and fastest; 1080p and 4k are upscaled from 720p |
aspectRatio | "16:9" | "9:16" | "16:9" | Landscape or portrait |
outputDir | string | "." | Directory where the clip will be saved (same sandboxing as generate_image) |
inputImages | string[] | - | Reference images sent ahead of the prompt: a first frame to animate, or subjects and styles to keep. Refer to them as <IMAGE_REF_1>, <IMAGE_REF_2>, … |
previousInteractionId | string | - | interactionId from an earlier result. Extends that clip instead of starting a new one; the prompt describes what happens next |
Things worth knowing:
interactionId back as previousInteractionId; each extension adds
up to 10 s, and the whole clip is returned each time.
descriptionis only present when the model returns text alongside the clip.
Besides the standalone MCP server, this package can be embedded in another host — an app, or another MCP server that wants to expose image generation as its own tool.
generateImageToDisk takes the same options as the tool, so background: "transparent" throws for a model that cannot deliver an alpha channel. Check
registry.resolve(model).supportsTransparentBackground first if the model is not
one you chose yourself.
The library entry point never reads process.env, writes to stdio, or exits the
process. To read keys from the conventional environment variables anyway, use the
keysFromEnv() helper. The standalone server is available at mcp-imagenate/server.
| Export | Purpose |
|---|---|
createRegistry(keys) | Build a registry of the models available for the given keys |
keysFromEnv(env?) | Read provider keys from environment variables |
generateImageToDisk(options) | Generate images and write them to disk |
createVideoRegistry(keys) | Build a registry of the video models available for the given keys |
generateVideoToDisk(options) | Generate a clip and write it to disk |
resolveOutputDir / resolveInputImagePath | Path sandboxing helpers (opt-in) |
NANO_BANANA_OUTPUT_DIR is set, both output and input image paths are sandboxed within this directory. Symlinks that resolve outside the sandbox are rejected. For library embedders this is opt-in via outputBaseDir, since the host usually controls which paths reach the call.MIT