chatgpt-desktop-image-mcp
Related Servers
Alternatives to chatgpt-desktop-image-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLets Claude and other MCP clients generate and edit images with your own signed-in ChatGPT account in a background Chrome tab. No API key, no open ports; right-click reference collections and a gallery side panel. Windows + Chrome.7816 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.MIT
- 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 gradedqualityDmaintenanceImage generation for Claude Code via ChatGPT subscription token. No API key needed.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to generate images through the local ChatGPT Desktop App by automating the chat interface via CDP, saving PNGs to disk without requiring an OpenAI API key.MIT
- 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
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: generate_image produces an asset, image_status is a read-only diagnostic. The status tool is explicitly framed as the preflight/troubleshooting companion, so there is no risk of misselection.
Both names are snake_case and share the 'image' subject, but the conventions differ slightly: generate_image is verb_noun while image_status is noun_noun. Still predictable and readable, a minor deviation rather than an inconsistency.
Two tools is on the thin side, but the server's scope (generate one image, verify readiness) is genuinely narrow and both tools earn their place. Slightly under the typical 3-15 range but reasonable for the stated purpose.
Generation plus a status check covers the core workflow, and the tool notes edge cases like overwrites and serialization. Gaps are minor: no way to list or delete previously written PNGs, and no parameters for size/style beyond filename.