workbuddy-gpt-image
Related Servers
Alternatives to workbuddy-gpt-image
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables generating and editing images with GPT Image models through the OpenAI Images API or compatible endpoints, saving originals locally and returning downscaled previews plus file paths. Supports long-running jobs, workspace-based storage, and reference- or mask-based edits.3210 npmMIT
- AlicenseAqualityCmaintenanceEnables 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.22MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to generate and edit images from text prompts, reference images, or saved files through any OpenAI-images-compatible backend, returning each result inline as a downscaled preview (full-res on disk) so the agent can inspect and iterate. Also supports prompt expansion, exact-pixel resizing/recompression, and listing or re-serving saved images.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables image generation and editing using OpenAI's GPT Image 2 model within a Claude Desktop Code project workspace, with security boundaries and no-overwrite file handling.MIT
- 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
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to generate and edit images from text prompts or local files, returning both a saved file path and an inline image block. Supports up to four sequential images per call, model listing, and one-command setup across OMP, Codex, Claude Code, Cursor, and opencode.317 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct lifecycle stage: submit (generate_gpt_image), poll/wait (get_image_job), cancel (cancel_image_job), and backend health (check_image_backend). The descriptions explicitly contrast them, e.g. check_image_backend notes it does not generate while generate_gpt_image warns you must poll with get_image_job.
All four names use strict snake_case with a clear verb_noun form (get_image_job, cancel_image_job, generate_gpt_image, check_image_backend). Consistent convention throughout with shared _image_job / _image_backend suffixes reinforcing grouping.
Four tools map cleanly onto the async image-generation lifecycle with no filler. This is a well-scoped, focused surface for a single-domain server.
Submit, poll, cancel, and backend-check cover the core async lifecycle, and the descriptions make the intended flow clear. Minor gap: no list-jobs or result-retrieval/cleanup operation, so an agent tracking multiple jobs has no enumeration tool.