GPT Image MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Alternatively, you can store it in ~/.config/runapi/config.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| edit_imageB | Create a GPT Image task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a GPT Image task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a gpt-image task. |
| check_pricingC | Look up RunAPI pricing for the gpt-image model line. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: authentication, two clearly separated generation modes (edit vs text-to-image), task polling, and pricing lookup. There is no overlap between edit_image and text_to_image since their purposes are explicitly differentiated.
Names are consistently snake_case verb_noun (edit_image, text_to_image, get_task, check_pricing), which is predictable. The lone deviation is 'login', a bare verb that breaks the otherwise uniform pattern.
Five tools is well-scoped for a focused image-generation service. Each tool earns its place: auth, two task-creation paths, polling, and cost lookup.
The core lifecycle (login -> create task -> poll result) plus pricing is covered. Minor gaps exist: no task listing, cancellation, or deletion, but these are workarounds an agent can live without for the primary generation workflow.