A
licenseB
qualityD
maintenanceEnables generating images from text or transforming existing images using GPT-Image-compatible APIs, with support for OpenAI and Agnes AI backends.
2
MIT
openai-imagegen-mcp
by karllee830
Related Servers
Alternatives to openai-imagegen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables image generation and editing through OpenAI's gpt-image-2 model, supporting text-to-image, reference-guided generation, and editing with local files or URLs.2216 npm2MIT
- AlicenseAqualityCmaintenanceEnables image generation and editing using OpenAI's GPT Image API (gpt-image-1, 1.5, 2) with support for multi-image generation, history management, and batch processing.12224 npm1MIT
- AlicenseAqualityCmaintenanceEnables generating and editing images through OpenAI image models, with configurable output as saved files or returned URLs.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents and other MCP clients to generate images from text prompts and edit, restyle, or extend existing images through an OpenAI-compatible /v1/images API. Results are returned both inline as image content blocks and as files saved to disk, so agents can view and reuse them within a normal task.28 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables complete control of the OpenAI Images API for text-to-image generation, image editing, multi-image references, masks, streaming previews, and resumable jobs, with per-request model and parameter selection.MIT
TDQS
A4.1/5.0
Scored across 3 tools
Disambiguation5/5
Each tool maps to a distinct action: creating new images, editing/conditioning on existing images, and polling an async job. The descriptions explicitly cross-reference each other (generate/edit tell you to call get_image_result when status is "running"), leaving no ambiguity about selection.
Naming Consistency4/5
All three names are snake_case verb_noun(ish) forms: generate_image, edit_image, get_image_result. The only slight deviation is the longer 'get_image_result' suffix pattern, but it still follows the convention predictably.
Tool Count4/5
Three tools is at the low end of the ideal range, but each is clearly necessary for the domain: creation, editing, and async result retrieval. Nothing feels redundant or bloated.
Completeness4/5
The core lifecycle (generate, edit, poll async result) is covered with no dead ends, since the async pattern is explicitly handled. Minor gaps exist: no job listing/cancellation and no metadata or parameter-enumeration tool, though these are workable around.
Maintenance
ActivityMaintained
ResponsivenessSyncing