MCP Imagenate

io.github.mimo-3Published by GitHub account mimo-3v0.1.5Updated Oct 24, 2026

MCP server for image generation using multiple providers (Google Gemini, OpenAI, BFL FLUX)

VerifiedSTDIODesktop onlyMedia & DesignAI & ML

Overview

AI-generated overview

Lets an assistant generate images and short videos through several hosted providers (Google Gemini, OpenAI, BFL FLUX, Reve) and save the files locally.

What you can do
Exposes a generate_image tool that takes a prompt, model, resolution, aspect ratio, background mode and optional input images, then writes the result to a directory and returns the saved file paths. A separate generate_video tool produces 3-10 second mp4 clips with audio via Google Gemini Omni, and can extend a clip by passing back an interactionId. Models are grouped by provider, and only OpenAI gpt-image models can return transparent backgrounds.
When to use it
Useful when an assistant needs to create images or short clips as part of a task, such as illustrations, mockups, or cut-out subjects for slides, and you already have keys for at least one of the supported providers. Also usable as a library inside another host that wants to expose image generation as its own tool.
Requirements
Runs locally over stdio as an npm package (npx mcp-imagenate or a global install) and needs Node.js 20+. At least one provider API key must be set: GEMINI_API_KEY or NANO_BANANA_API_KEY, OPENAI_API_KEY or GPT_IMAGE_API_KEY, BFL_API_KEY, or REVE_API_KEY or REVE_API_TOKEN. The optional NANO_BANANA_OUTPUT_DIR sets the base output directory. Network access to the provider APIs is required.
Before you install
Provider keys are read from environment variables and are sent to third-party APIs; the server exits if none are configured. Generations cost money: Reve is about 150 credits (roughly $0.20) per image, and Gemini Omni video is about $0.10 per second of 720p output with no free tier. The tools write files to disk, so set NANO_BANANA_OUTPUT_DIR to sandbox output and input paths; without it, paths are not confined.

Installation

In SourceWeft

  1. Open MCP Imagenate in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-imagenate

[mcp-imagenate]

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.

Providers & Models

Google Gemini (Nano Banana)

NameModel IDBest for
nano-banana-2gemini-3.1-flash-image-previewFast, high-volume generation
nano-banana-2.1gemini-nano-banana-2.1Successor to Nano Banana 2 (1K/2K/4K only)
nano-banana-progemini-3-pro-image-previewHighest quality output

Google Gemini Omni (video)

NameModel IDBest for
gemini-omni-1.1-flashgemini-omni-1.1-flash3–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.

OpenAI

NameModel IDBest for
gpt-image-2.5-flaregpt-image-2.5-flareFast generation, cheap at medium and high. The default here
gpt-image-2.5-sunburstgpt-image-2.5-sunburstPrecise edits, slower than Flare
gpt-image-2gpt-image-2Previous generation

These are the only models here that can return a transparent background — see Transparent backgrounds.

BFL FLUX

NameModel IDBest for
flux-2-kleinklein-4bFast, lightweight generation
flux-2-propro-previewBalanced quality and speed
flux-2-maxmaxMaximum quality

Reve

NameVersionBest for
reve-imagelatestTypography 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.
  • Prompts are capped at 4,000 characters, and this provider rejects longer ones before spending a request.
  • inputImages become v2 references. Reve accepts at most eight; a longer list is rejected before any of the files are read.
  • The saved file's extension follows the format Reve actually returned (PNG, JPEG or WebP), which is detected from the bytes rather than assumed.
  • A generation costs 150 credits (about $0.20) and typically takes 40-80 seconds. Give any proxy or job runner in front of it a timeout of at least 120 seconds.

Requirements

  • Node.js 22+
  • At least one provider API key

Installation

bash
npx mcp-imagenate

Or install globally:

bash
npm install -g mcp-imagenate

Setup

Set API keys for the providers you want to use:

bash
# Google Gemini (at least one)export GEMINI_API_KEY=your_key_here# orexport NANO_BANANA_API_KEY=your_key_here
# OpenAI (at least one)export OPENAI_API_KEY=your_key_here# orexport GPT_IMAGE_API_KEY=your_key_here
# BFL FLUXexport BFL_API_KEY=your_key_here
# Reve (at least one)export REVE_API_KEY=your_key_here# orexport REVE_API_TOKEN=your_key_here

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "mcp-imagenate": {      "command": "npx",      "args": ["mcp-imagenate"],      "env": {        "GEMINI_API_KEY": "your_key_here",        "NANO_BANANA_OUTPUT_DIR": "/path/to/image/output"      }    }  }}

Environment Variables

VariableRequiredDescription
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_DIRNoBase 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.

Tool: generate_image

Parameters

ParameterTypeDefaultDescription
promptstring (1-32,000 chars)-Text prompt describing the image
modelsee Models above"gpt-image-2.5-flare"Model to use (available models depend on configured API keys)
resolution"1K" | "2K" | "4K""1K"Output image resolution
aspectRatiosee 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)
outputDirstring"."Directory where images will be saved
inputImagesstring[]-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)
Supported aspect ratios

1:1, 2:3, 3:2, 3:4, 4:3, 9:16, 16:9, 21:9

Transparent backgrounds

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.

Response

Returns a JSON object:

json
{  "model": "gemini-3.1-flash-image-preview",  "savedFiles": ["/path/to/image-1.png"],  "settings": {    "resolution": "1K",    "aspectRatio": "9:16",    "mode": "image",    "background": "auto"  },  "description": "..."}

description is only present when mode is "image_and_text".

Tool: generate_video

Available when a Google key is configured. Generates one clip with audio and saves it as an mp4.

Parameters

ParameterTypeDefaultDescription
promptstring (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
durationSecondsinteger 3–105Clip 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
outputDirstring"."Directory where the clip will be saved (same sandboxing as generate_image)
inputImagesstring[]-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>, …
previousInteractionIdstring-interactionId from an earlier result. Extends that clip instead of starting a new one; the prompt describes what happens next

Things worth knowing:

  • A single request is capped at 10 s by the model. To go longer, pass the returned interactionId back as previousInteractionId; each extension adds up to 10 s, and the whole clip is returned each time.
  • Text in the prompt is rendered on screen as written, including non-Latin scripts, though Google only documents English as fully supported.
  • Clips are fetched through Google's file endpoint rather than inlined in the JSON response, as the API documentation recommends above 4 MB. Expect one extra request per generation.
  • 720p costs about $0.10 per second of output; there is no free tier for this model.

Response

json
{  "model": "gemini-omni-1.1-flash",  "savedFile": "/path/to/1788347054697-491db547.mp4",  "settings": {    "durationSeconds": 5,    "resolution": "720p",    "aspectRatio": "16:9"  },  "interactionId": "v1_...",  "description": "..."}

description is only present when the model returns text alongside the clip.

Use as a library

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.

ts
import { createRegistry, generateImageToDisk } from "mcp-imagenate";
// Keys are passed in explicitly; nothing here reads process.env.const registry = createRegistry({ openai: myOpenAIKey, google: myGoogleKey });
if (registry.models.length === 0) {  throw new Error("No image provider is configured");}
const outcome = await generateImageToDisk({  registry,  prompt: "a calico cat asleep on a warm keyboard",  model: registry.defaultModel!,  aspectRatio: "16:9",  outputDir: "/somewhere/to/write",  // outputBaseDir defaults to null, meaning no path sandboxing. Set it to a  // directory to confine both output and input paths within that directory.});
console.log(outcome.savedFiles);

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.

ExportPurpose
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 / resolveInputImagePathPath sandboxing helpers (opt-in)

Security

  • Path sandboxing: When 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.
  • Input validation: Input images are validated for format (PNG/JPEG/WEBP/GIF) and size (max 20 MB). Video durations outside the model's range are rejected before any request is sent.
  • API key validation: The server exits immediately if no API keys are configured. The library reports this as an empty registry instead, leaving the decision to the host.

License

MIT

Source: README.md at commit 0c34606

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts