imagen-4-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key. Get one at https://runapi.ai. |
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. |
| remix_imageC | Create a Imagen 4 task on RunAPI (remix image). Returns a task id, status, and output URLs. |
| text_to_imageC | Create a Imagen 4 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 imagen-4 task. |
| check_pricingC | Look up RunAPI pricing for the imagen-4 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: auth, pricing lookup, two generation modes, and task retrieval. remix_image and text_to_image both create Imagen 4 tasks but their descriptions clearly differentiate modality, so confusion is minimal.
All tools use a consistent snake_case verb_noun or single-verb pattern (login, check_pricing, remix_image, text_to_image, get_task). No mixed conventions or casing deviations.
Five tools is well-scoped for an image-generation API wrapper: auth, pricing, two generation entry points, and a status poller. Each earns its place without redundancy.
Core lifecycle is covered: submit generation (text/remix), poll with get_task, check pricing, and authenticate. Minor gaps exist around task management (e.g. list tasks, cancel task), but the primary workflow has no dead ends.