ImageForge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Your OpenAI API key or token issued by a compatible OpenAI gateway. | |
| OPENAI_BASE_URL | No | Base URL for the OpenAI-compatible API. Defaults to https://api.openai.com/v1. | https://api.openai.com/v1 |
| OPENAI_IMAGE_MODEL | No | The image model to use. Defaults to gpt-image-2. | gpt-image-2 |
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 |
|---|---|
| generate_imageB | Generate one image with gpt-image-2, optionally guided by reference images. |
| edit_imageC | Edit one or more input images with gpt-image-2. |
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: one generates new images, the other edits existing images. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern (generate_image, edit_image), providing a consistent and predictable naming convention.
At two tools, the set is minimal but appropriate for the server's focused purpose of image generation and editing. While slightly thin, each tool is essential and well-scoped.
The tool surface fully covers the domain of image creation and modification. There are no obvious missing operations for the server's stated purpose.