image2-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAGE2_MODEL | No | Model name override | openai/gpt-image-2 |
| MAGENE_API_KEY | Yes | Your company API key | |
| IMAGE2_OUTPUT_DIR | No | Default image save location | |
| MAGENE_API_BASE_URL | No | API endpoint | http://localhost:11636/api/v1/images/generations |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_imageA | Generate an image from a text prompt using the company image2 model. Use async_mode=true (default) for fire-and-forget — returns immediately, image saves to disk in the background. Use async_mode=false to wait for the image and see it in the response. Size: Presets: 1024x1024, 1024x1536, 1536x1024, 2048x1152, 2048x2048, 2160x3840, 3840x2160, auto. Custom: WxH (max 3840px per side, multiples of 16, ratio ≤ 3.0:1, pixels 655,360–8,294,400) |
| list_imagesA | List recently generated images in the output directory. Useful after async/fire-and-forget generation to see what's been created. |
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 have clearly distinct purposes: generating images and listing generated images. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: 'generate_image' and 'list_images'. The convention is uniform and predictable.
With only 2 tools, the server feels thin for its domain, but it covers the essential generation and listing operations. It is borderline reasonable but lacks additional supporting tools.
The server covers core image generation and listing. However, it lacks individual image retrieval, deletion, or progress tracking for async operations, which are minor but notable gaps.