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_imageC | Create a Ideogram V3 task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| reframe_imageC | Create a Ideogram V3 task on RunAPI (reframe 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 7 tools
Each tool serves a clearly distinct purpose: authentication, pricing lookup, task status retrieval, and four different image generation modes (text-to-image, edit, reframe, remix). There is no functional overlap, so an agent can easily select the correct tool.
Most tool names follow a consistent verb_noun pattern (e.g., get_task, edit_image, check_pricing), but 'login' is a bare verb and 'text_to_image' is a compound descriptor rather than a verb+object structure. These minor deviations are still readable and predictable.
Seven tools is well within the ideal range for a domain-specific server, covering authentication, pricing, all major generation modes, and task status checking without unnecessary redundancy or bloat.
The core image generation workflows are well represented, including text-to-image, editing, reframing, and remixing, plus status retrieval. Minor gaps exist, such as no task cancellation or listing, but these are not critical for the primary use case.