@chrischall/gemini-mcp 0.7.2 → 0.9.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.9.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.9.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.9.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,26 @@ 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.
+
+For hosts whose timeout can't be tamed (e.g. Claude Desktop, a fixed ~30s cap that ignores
+progress), two guards make re-issuing safe and unnecessary:
+
+- **`async: true`** returns a `job_id` immediately instead of the image, so the call can't
+  time out at all; poll `gemini_get_result` with the `job_id` until it's `done`.
+- **`idempotency_key`** makes a repeat call idempotent — a retry with the same key returns the
+  recorded result (`reused: true`) instead of billing a second generation. (Even without a key,
+  two identical in-flight calls are deduplicated automatically.)
 
 ## Tools
 
@@ -26,6 +46,7 @@ Developed and maintained by AI (Claude Code).
 | `gemini_edit_image` | One-off edits or multi-image composition with a text instruction (for a series of edits, use `gemini_interact`) |
 | `gemini_generate_set` | Generate a master image plus N consistent images referencing it |
 | `gemini_interact` | Preferred tool for iterative refinement: multi-turn generation/editing via the Interactions API — chain the returned `interaction_id` via `previous_interaction_id` (or `continue_last: true`) |
+| `gemini_get_result` | Fetch an async generation started with `async: true` by its `job_id` (status `running` → `done` result). Lets a long generation outlive a host's `tools/call` timeout |
 
 ## Quick Start