Ideogram V3 MCP Server
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 in ~/.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. |
| edit_imageB | Create a Ideogram V3 task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| remix_imageC | Create a Ideogram V3 task on RunAPI (remix image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Ideogram V3 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 ideogram-v3 task. |
| check_pricingB | Look up RunAPI pricing for the ideogram-v3 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 6 tools
Each tool has a clearly distinct role: three distinct image-generation modes (text_to_image, edit_image, remix_image), plus task polling (get_task), auth (login), and pricing (check_pricing). The three generation tools could look similar at a glance, but their mode-specific descriptions make the boundaries unambiguous.
Almost all tools follow a snake_case verb_noun pattern (check_pricing, edit_image, get_task, remix_image), which is predictable and readable. 'login' is a bare verb rather than verb_noun and 'text_to_image' inverts the pattern, but both are still clear and not confusing.
Six tools is well-scoped for an image-generation service: one auth, one pricing lookup, three generation modes, and one task-status retrieval. Each tool earns its place with no redundant or filler entries.
Core lifecycle is covered: authenticate, check cost, create tasks in all three modes, and poll task status with returned output URLs. Minor gaps exist (e.g. list tasks, cancel task), but agents can work around them since task ids and outputs are returned directly.