Skip to main content
Glama
kuchris

chatgpt-desktop-image-mcp

by kuchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

generate_image

Destructive

Generate a PNG image from a text prompt using the signed-in Codex desktop app. Returns the file path, dimensions, and image for pictures, icons, or logos.

Instructions

Generate an image with ChatGPT and save it as a PNG on disk. Returns the file path, the dimensions, and the image itself.

Use for any visual asset the user asks for: a picture, illustration, icon, logo, mockup or photo. Do not call it speculatively, and do not use it for diagrams or charts that text already conveys.

Not idempotent: the same prompt twice yields two different images and two files. Takes 15-60 seconds, and calls are serialized because they share one application window. Writes a new PNG every time, and overwrites an existing file if "filename" collides with one. With thread "new" it also adds a conversation to the user's ChatGPT sidebar.

It drives the already-signed-in Codex desktop app over the DevTools protocol, so it needs no API key and consumes no Codex agent quota. It refuses to run if the app is in Work mode, because that would spend Codex usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesSubject, style, palette, mood, composition. Be descriptive and specific. For transparency or text-in-image, say so explicitly in the prompt.
threadNo"new" (default) starts a fresh conversation: fully isolated, but each call adds a row to the user's sidebar and the model cannot see earlier generations. "reuse" posts into the conversation this tool last used, so you can iterate ("same image but blue"). Use "reuse" when refining, "new" for a fresh subject.
filenameNoOutput file name without the .png extension. Defaults to chatgpt-<timestamp>.
output_dirNoDirectory to write into. Prefer an absolute path, or a path relative to this server's working directory. Defaults to <codeximg>/out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations: non-idempotency with a concrete example, 15-60s latency, serialization due to a shared window, file overwrite behavior, sidebar side-effect for thread 'new', auth model (drives signed-in Codex app, no API key, no quota), and a refusal condition in Work mode.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads what the tool does and returns, then usage, then behavioral caveats. Three tight paragraphs where every sentence carries actionable information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description states the return values (file path, dimensions, the image). Combined with latency, serialization, overwrite and refusal details, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a genuine cross-parameter side effect not in the schema: 'With thread "new" it also adds a conversation to the user's ChatGPT sidebar.' It also adds filename collision semantics beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('Generate an image with ChatGPT and save it as a PNG on disk') with scope of use spelled out. Nothing overlaps with the only sibling, image_status, which is a status check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('any visual asset: a picture, illustration, icon, logo, mockup or photo') and when-not ('do not call it speculatively', 'not for diagrams or charts that text already conveys'). Routing is fully determined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools