RunAPI Midjourney MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | API key for RunAPI, used for headless and CI hosts. Can also be set via config file. |
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 Midjourney task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| extend_videoC | Create a Midjourney task on RunAPI (extend video). Returns a task id, status, and output URLs. |
| image_to_videoC | Create a Midjourney task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Midjourney task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_seedC | Run a synchronous Midjourney operation on RunAPI (get seed). Returns the operation result. |
| image_to_promptC | Run a synchronous Midjourney operation on RunAPI (image to prompt). Returns the operation result. |
| shorten_promptC | Run a synchronous Midjourney operation on RunAPI (shorten prompt). Returns the operation result. |
| get_taskA | Fetch the current status and latest result payload for a midjourney task. |
| check_pricingB | Look up RunAPI pricing for the midjourney 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 10 tools
Each tool targets a distinct action or resource: login is for authentication, the four creation tools (text_to_image, image_to_video, extend_video, edit_image) are clearly different task types, the three synchronous operations (get_seed, image_to_prompt, shorten_prompt) are distinct utilities, and get_task/check_pricing serve separate purposes. No two tools appear interchangeable.
Tool names mostly follow a verb_noun pattern (edit_image, extend_video, get_seed, shorten_prompt, get_task, check_pricing), but the creation tools (text_to_image, image_to_video) use a noun_to_noun pattern that describes the operation rather than a verb. This is a minor inconsistency but overall the naming style is predictable and readable.
With 10 tools, the server is well-scoped for a Midjourney API wrapper. Each tool serves a clear function, and the count is within the ideal 3-15 range. The set is neither bloated nor thin.
The server covers the core Midjourney workflows: login, all major generation types (text-to-image, image-to-video, extend video, edit image), task status retrieval, and several common utilities (seed, prompt inversion, prompt shortening). Minor gaps exist such as upscale or variation operations, but the essential lifecycle is present.