@chrischall/gemini-mcp 2.2.0 → 2.3.1

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for Google Gemini image generation and editing — generate and edit images via the Gemini API",
-    "version": "2.2.0"
+    "version": "2.3.1"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "Gemini Images",
       "source": "./",
       "description": "Generate and edit images with Google Gemini image models (Nano Banana / Nano Banana Pro) via natural language prompts",
-      "version": "2.2.0",
+      "version": "2.3.1",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gemini-mcp",
   "displayName": "Gemini Images",
-  "version": "2.2.0",
+  "version": "2.3.1",
   "description": "MCP server for Google Gemini image generation and editing — generate and edit images via the Gemini API",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -14,8 +14,10 @@ Developed and maintained by AI (Claude Code).
 |---|---|---|
 | `GEMINI_API_KEY` | Yes | Your Google Gemini API key ([aistudio.google.com/apikey](https://aistudio.google.com/apikey)) |
 | `GEMINI_IMAGE_MODEL` | No | Override the default image model (default: `gemini-3.1-flash-image`) |
-| `GEMINI_OUTPUT_DIR` | No | Default directory for generated images (default: current working directory) |
+| `GEMINI_OUTPUT_DIR` | No | Default directory for generated images (default: current working directory). When set, a per-call `output_dir` must be inside it. |
 | `GEMINI_INPUT_DIR` | No | Directory to resolve bare input-image filenames against (so `images: ["foo.jpg"]` works) |
+| `GEMINI_UPLOAD_DIR` | No | Restrict local files streamed to the Gemini Files API (`gemini_upload_file` `path`, `video_path`) to these directories — one or more, separated by `:` (`;` on Windows); `~` allowed. A path outside is refused before any upload. Unset: no restriction |
+| `GEMINI_REFERENCE_DIR` | No | Restrict local **reference images** (the `images` / `master_images` paths read and sent to Gemini — inline, or as a Files API upload once reused) to these directories — `:`-separated (`;` on Windows), `~` allowed; `GEMINI_OUTPUT_DIR` is always allowed too, so generated images can be fed back in. A path outside (symlinks followed) is refused before it is read. Unset: `GEMINI_UPLOAD_DIR` applies instead. If both are unset, reference images are **unrestricted** on a local install (any file the server can read can be sent), and confined to `$MCP_DATA_DIR/uploads` when `MCP_DATA_DIR` is set (hosted) |
 | `GEMINI_TIMEOUT_MS` | No | Upstream request timeout in ms (default: `60000`, or `120000` for `image_size: "4K"`); each generation tool also takes a per-call `timeout_ms` |
 | `GEMINI_HEARTBEAT_MS` | No | Progress-notification cadence in ms while a generation runs (default: `10000`; `0` disables) — keeps MCP hosts that reset their timeout on progress from timing out long generations |
 | `GEMINI_CHAIN_RETRY_MS` | No | How long to wait out interactions-store lag when a chained call 404s (default: `120000`; `0` disables retrying) |
@@ -189,6 +191,15 @@ safe form, and a markdown link is a reasonable enhancement where you know it ren
 Signed-URL lifetime is clamped to `MEDIA_TTL_DAYS`, so a link never outlives the object it
 points at.
 
+**Prompts are stored too.** Each generated object on a hosted deployment gets a small JSON
+record beside it holding the prompt (first 500 characters), model and interaction id — that is
+what `gemini_list_recent_media` shows and what lets a lost turn be recovered. The record lives
+and is swept with its object, so it is kept for the same `MEDIA_TTL_DAYS` window, not longer.
+Locally, `gemini_interact` writes an `<image>.json` sidecar (model, interaction id, options and
+any text the model replied with — not the prompt itself) next to each image in the output dir;
+those files are yours to keep or delete and never expire on their own. If your
+prompts describe real people, bear in mind they sit in your bucket for the retention window.
+
 ## Sending reference images without burning context
 
 Every tool that takes a reference image — `gemini_image_generate`, `gemini_image_edit`,