z-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be set via ~/.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. |
| text_to_imageB | Create a Z 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 z-image task. |
| check_pricingB | Look up RunAPI pricing for the z-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 4 tools
Each tool targets a clearly distinct concern: authentication (login), task creation (text_to_image), task polling (get_task), and pricing lookup (check_pricing). No two tools could plausibly be confused for one another.
Three tools follow a readable verb/noun style (get_task, check_pricing, text_to_image) while 'login' is a bare verb, a minor deviation. The overall pattern is predictable enough that an agent can infer intent from names alone.
Four tools is a lean but coherent minimum for a single-model image generation service: authenticate, generate, poll, check cost. It is slightly thin but nothing feels redundant or padded.
The core create-then-poll lifecycle is covered, but there is no cancel/delete task, no list-tasks operation, and no image-to-image or edit variant for what is presumably an image model. Agents can work around these gaps but will hit dead ends for anything beyond basic text-to-image generation.