gpt-image-2-mcp
Related Servers
Alternatives to gpt-image-2-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes OpenAI's gpt-image-2 (image generation and editing) as an MCP server for tools like generate_image, edit_image, and iterative edit sessions.638 npm12MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides tools for generating and editing images using OpenAI's gpt-image-1 model via an MCP interface, enabling AI assistants to create and modify images based on text prompts.15Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGenerates and edits images using OpenAI image models via MCP tools.MIT
- AlicenseAqualityBmaintenanceGenerates 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.17 npm1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceProvides an MCP interface to a unified image generation gateway, enabling AI agents to generate images through multiple free and low-cost providers, list sessions and history, and manage provider configurations.-
TDQS
Scored across 8 tools
Each tool targets a distinct concern: one-shot generation, one-shot editing, multi-turn session lifecycle, and job polling/listing. The overlap between edit_image and continue_edit_session is clarified by the former being a single edit and the latter being an iterative turn within a session.
All tool names follow a consistent snake_case verb_noun pattern: generate_image, edit_image, get_image_job, list_image_jobs, start_edit_session, continue_edit_session, end_edit_session, list_edit_sessions. The verb choices clearly reflect the action for each resource.
Eight tools is well-scoped for the server's purpose: image generation and editing plus the supporting async-job and edit-session infrastructure. Each tool earns its place and there is no redundant surface.
The tool set covers the full workflow: generate and edit images, poll and list background jobs, and start/continue/list/end iterative edit sessions. No critical dead ends remain for the stated domain.