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_imageB | 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_taskA | Fetch the current status and latest result payload for a imagen-4 task. |
| check_pricingA | 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 has a clearly distinct purpose: authentication, two distinct image generation modes, task retrieval, and pricing lookup. No overlap or ambiguity exists between them.
Tool names are mostly snake_case with a verb-led pattern (remix_image, get_task, check_pricing). 'login' and 'text_to_image' deviate slightly from the verb_noun convention, but the overall style is consistent and readable.
Five tools is well-scoped for a focused image generation server: auth, two generation entry points, status checking, and pricing. Each tool earns its place without redundancy.
The core workflow of initiating image tasks and retrieving results is fully covered. Minor gaps like task listing or cancellation exist, but they are not essential for the stated purpose.