openai-image-mcp
Related Servers
Alternatives to openai-image-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to generate images, edit existing ones, and create matching image sets using either the Codex CLI or the OpenAI Images API. It returns previews and saved file paths so agents can inspect results and continue iterating.3206 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to generate and edit images through OpenAI's Images API, saving output files to an absolute directory and returning paths and metadata.296 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to generate, edit, and post-process images directly into a project, with text-to-image, instruction-based editing with masks and reference images, plus local resize, crop, and format conversion and dimension inspection tools.43 npm1MIT
- AlicenseAqualityCmaintenanceGenerates and edits images using OpenAI GPT Image or Google Gemini models, saving every result to disk and returning local file paths so AI assistants can continue working with the images. It enables prompt-based image creation, editing, inpainting, multi-image composition, and model listing through MCP tools.11Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients to generate and edit images through any OpenAI-compatible image API, saving results as local files and returning absolute paths for immediate use.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
TDQS
Scored across 3 tools
The three tools each target a clearly distinct action: creating new images, editing existing ones, and reading model metadata. An agent can trivially choose between generate_image and edit_image based on whether it has source images, and list_models is purely informational.
All names follow a consistent snake_case verb_noun pattern (generate_image, edit_image, list_models), with plain, predictable verbs and no style mixing.
Three tools is on the lean side but covers the core generate/edit/metadata loop without redundancy. A slightly larger surface (e.g. mask creation, result retrieval) would not feel padded.
The generate/edit/list lifecycle is covered and the descriptions clarify how results land on disk, but there is no way to fetch or clean up generated files, no variation/upscale path, and no way to inspect saved outputs after the fact.