Z-Image Studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | The host to bind the server to when running in 'serve' mode. | 0.0.0.0 |
| PORT | No | The port to bind the server to when running in 'serve' mode. | 8000 |
| ZIMAGE_BASE_URL | No | Base URL for generated links. Used to construct absolute URLs for ResourceLinks when using SSE or Streamable HTTP transports. | |
| ZIMAGE_DISABLE_MCP | No | Set to '1' to disable all MCP endpoints (default is '0'). | 0 |
| Z_IMAGE_STUDIO_DATA_DIR | No | Override the default data directory location where the database and LoRAs are stored. | |
| HSA_OVERRIDE_GFX_VERSION | No | For AMD ROCm users on Linux, manual override for gfx version (e.g., '10.3.0' for RDNA2, '11.0.0' for RDNA3) if the GPU is not officially supported. | |
| Z_IMAGE_STUDIO_OUTPUT_DIR | No | Override the default output directory location where generated images are saved. | |
| ZIMAGE_ENABLE_TORCH_COMPILE | No | Force enable torch.compile optimization (experimental). Set to '1' to enable. By default disabled for Python 3.12+ due to known compatibility issues. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generateA | |
| list_modelsA | List available image generation models and hardware recommendations. |
| list_historyC | List recent image generations history. |
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
The three tools have completely distinct purposes: generating images, listing generation history, and listing available models. There is no functional overlap, so an agent can clearly differentiate them.
All tool names use lowercase snake_case with a clear verb-first pattern. Although 'generate' is a single verb while the others are 'list_*', the convention is consistent and predictable across the set.
With only 3 tools, the server is on the minimal side but still covers the core functionality of an image generation service. It falls within the acceptable range for a focused tool, though a few more utilities could enhance its scope.
The server includes essential operations: generate, view history, and list models. However, it lacks common lifecycle operations such as deleting history entries, viewing a specific generation's details, or updating a generation, which may hinder some workflows.