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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| text_to_imageC | Create a Z Image task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a z-image task. |
| check_pricingA | 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 3 tools
Each tool serves a distinct purpose: check_pricing for price lookups, get_task for status retrieval, and text_to_image for generation. There is no functional overlap.
All tools use lowercase snake_case, but 'text_to_image' is a descriptive noun phrase rather than a verb_noun pattern like the other two. This is a minor deviation from an otherwise consistent style.
With only three tools, the server feels minimal for an image generation service. While each tool is justified, the count is at the low end of what would be expected, leaving some workflows uncovered.
The server covers creation (text_to_image) and status checking (get_task), plus pricing. However, missing operations like listing all tasks or canceling a task are notable gaps that agents may encounter.