image-gen
Related Servers
Alternatives to image-gen
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets Claude Code or any MCP client generate images through the official Codex CLI using an existing ChatGPT plan login, with no API key or separate billing. Supports prompt-driven generation with base and reference images, writing results to a chosen path.1MIT
- AlicenseNot gradedqualityBmaintenanceGenerates and edits images through the Codex CLI using an existing ChatGPT subscription, with queued jobs, progress reporting, and artifact URLs for MCP clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to generate and edit images with GPT Image by relaying prompts through a local Codex CLI signed in with a ChatGPT plan, saving results to disk and returning them inline with no OpenAI API key required.48 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating images directly from Claude Code using the ChatGPT subscription's built-in Codex CLI and gpt-image-2, with no API key or separate credits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP agents such as Claude Desktop and Claude Code to generate AI images through a single resident Windows tray instance, getting back file paths, previews, and structured results. Supports Codex CLI, OpenRouter sign-in, or custom OpenAI/Gemini-compatible APIs, with dynamic per-model parameters, asynchronous jobs, and progress notifications.8MIT
- AlicenseAqualityCmaintenanceEnables Claude and other MCP clients to generate new images and edit existing ones through the locally installed ChatGPT/Codex app without an API key, returning saved file paths and inline previews so results can be inspected and iterated on.21MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: generate_image creates, get_image_job polls an async result, and image_backend_status reports configuration. The descriptions explicitly cross-link generate_image's job_id output to get_image_job, so an agent cannot easily misselect.
All names use consistent snake_case, and two follow a verb_noun pattern (generate_image, get_image_job). image_backend_status is a noun-only diagnostic name, a minor deviation from the verb-first convention.
Three tools is well-scoped for a focused image-generation server; the async job model genuinely justifies a separate retrieval tool, and the status tool is small but useful for diagnosing backend auth. No filler tools.
Core flow (generate, poll, check backend) is covered, but the async job lifecycle has dead ends: no way to list pending jobs, cancel a job, or recover a result if the job_id is lost. Configuration of output/size is also not exposed beyond what generate_image infers.