@chrischall/gemini-mcp 0.7.2 → 0.8.0

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": "0.7.2"
+    "version": "0.8.0"
   },
   "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": "0.7.2",
+      "version": "0.8.0",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gemini-mcp",
   "displayName": "Gemini Images",
-  "version": "0.7.2",
+  "version": "0.8.0",
   "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

@@ -16,6 +16,18 @@ Developed and maintained by AI (Claude Code).
 | `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_INPUT_DIR` | No | Directory to resolve bare input-image filenames against (so `images: ["foo.jpg"]` works) |
+| `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 |
+
+### Long generations and client timeouts
+
+4K / Pro-model generations can outrun an MCP host's own `tools/call` timeout (error `-32001`).
+The server sends `notifications/progress` heartbeats so hosts that reset their timeout on
+progress wait it out. If the host still gives up, the server-side generation usually completes
+anyway: the image is written to the output dir, `gemini_interact` also writes an
+`<image>.json` sidecar recording the `interaction_id`, and `continue_last: true` resumes the
+interaction the lost response belonged to — check the output dir before re-issuing a call
+(a re-issue is a second billable generation).
 
 ## Tools