I could already ask my agent to generate an image through MCP. But I wanted to try something less conversational: send a prompt from a script and get a file back.
That was the gap I wanted a ChatGPT image generation API to fill. No agent choosing a tool for me, and no manual download at the end. Just a request my code could submit and a result it could retrieve.
The answer was in the BrowserAct ChatGPT image template I had already been using. Its published Bot could be called through HTTP as well as MCP. I tested that route with a perfume-bottle prompt and downloaded the resulting PNG.
What interested me was having one reusable image tool: I could call it from code, use it from a compatible agent, and keep the ChatGPT login in one configured browser environment.
I Wanted the Image Workflow in My Code
My earlier MCP walkthrough was about requesting images inside an agent. This time, I wanted to handle the inputs, waiting, and files myself.
For a script, “generate an im
Discussion
Your thoughts matter!
Your input is valuable—be the first to share it!