agileimagegen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google AI Studio API key with access to Gemini image-capable models | |
| AGILEIMAGEGEN_LOG_LEVEL | No | Log level for the server | info |
| AGILEIMAGEGEN_OUTPUT_DIR | No | Directory where generated images are written by default | ./output |
| AGILEIMAGEGEN_SAVE_PROMPTS | No | Whether to save prompts to disk | false |
| AGILEIMAGEGEN_DEFAULT_MODEL | No | Default model for image generation and editing | gemini-2.5-flash-image |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| image.generateA | Generate an image with Gemini using a Google AI Studio API key. Saves the result to disk and returns structured metadata. |
| image.editA | Edit one or more local images with Gemini using multimodal input. Saves the result to disk and returns structured metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools, image.generate and image.edit, are clearly distinct: one creates a new image and the other modifies existing images. There is no overlap in their purposes, making it easy for an agent to select the correct tool.
Both tool names follow a consistent image.<verb> pattern (generate, edit). The uniform use of the dot separator and the shared namespace creates a predictable naming convention.
With only 2 tools, the server feels thin. While both tools serve a clear purpose, the count is borderline and does not provide a broader toolkit that might be expected from an image-focused server.
The server covers the core operations of generating and editing images, which are its stated purpose. There are no obvious missing operations within that narrow scope, though it lacks any lifecycle management (e.g., listing or deleting images).